<delroth>
does anyone happen to have a good way of getting eelco's attention? :) https://github.com/NixOS/nixpkgs/pull/100024 we've missed something like 5 months of "sudo" stable releases because the PRs aren't getting reviewed, and so far this one seems to be going the same way
<{^_^}>
#100024 (by delroth, 1 day ago, open): sudo: 1.8.31p1 -> 1.9.3p1 + adding myself as maintainer
<samueldr>
niksnut on IRC is eelco, delroth
<samueldr>
though already mentioning it here helps
<delroth>
ahh, I looked for the usual usernames :)
<delroth>
thanks
<samueldr>
I would suggest adding `closes #whatever` to the PR body in this instance, since it obsoletes other PRs
<samueldr>
hopefully all committers check those are true when working on a contributor's PR :)
<delroth>
done
<samueldr>
delroth: do you know if there is a reason the change should be backported to stable?
<samueldr>
something like fixing security issues mainly
<delroth>
not that I know of
<samueldr>
good, I looked at the changelog quickly and saw nothing of the sort either
<aanderse>
> anonymous function at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/packet-spot-eval-3/pkgs/servers/http/couchdb/default.nix:1:1 called with unexpected argument 'spidermonkey', at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/packet-spot-eval-3/lib/customisation.nix:69:16
<samueldr>
aanderse: which PR?
<{^_^}>
error: syntax error, unexpected ':', expecting ')', at (string):325:149
<eyJhb>
I might not know exactly how Hydra works, but e.g. why was it cancelled?
<samueldr>
right, there's no reason to give when you cancel a job
<eyJhb>
Is there any way to deduct it?
<samueldr>
IIRC aborted are for when hydra canceled, and canceled for when a user canceled
<samueldr>
though I'm not 100% sure
<samueldr>
>> Status: Cancelled by user
<samueldr>
right
<samueldr>
it's written right here
<samueldr>
so _any_ user that can cancel jobs in Hydra could have canceled it
<eyJhb>
Yeah, but it is just.. It moved to a new version of nixpkgs, which might have worked, but not sure, and no reason, and stuff
<eyJhb>
Would be nice to have a comment field for stuff like that...
<eyJhb>
(I just want unstable to run again, but there is SO LONG between builds, but it does not eval that often)
<samueldr>
I do agree it would be nice to have a (required) field with a reason
<eyJhb>
Can we make it run the latest version ?
<samueldr>
I think the most likely reason it was cancelled was the use of the option to cancel all the queued builds "not current"
<eyJhb>
:((((
<samueldr>
though that's totally a guess
<eyJhb>
It is better than anything I have
<samueldr>
what do you mean "run the latest version"?
<eyJhb>
Evaluate the latest master nixpkgs, so that we can maybe bump the unstable branch
<eyJhb>
If that makes sense?
<samueldr>
an evaluation could be queued, but without knowing why the builds were cancelled, I don't know if there's value over leaving it eval whenever
<samueldr>
it could be staging-next is being prioritized so that it can be merged
<samueldr>
which is why a cancel reason would really be helpful at the people-scale we present
<samueldr>
maybe there's not that many users on Hydra with rights, but they're... uh... definitely not in proximity, either communication, geographical or timezone-wise