New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
procps-ng: updated project location #37731
Conversation
owner ="procps-ng"; | ||
repo = "procps"; | ||
# should be tag v3.3.12, but the sha is immutable of course, which is desirable | ||
rev = "e0784ddaed30d095bb1d9a8ad6b5a23d10a212c4"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd still use
rev = "v${version}";
Git tags are meant not to be moved; we check the hash of the output anyway. It will also be less error-prone on updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, will add that
Otherwise I like the changes. EDIT: but it will need to target the staging branch instead, due to rebuilding thousands of packages. |
Should I take maintainership of procps-ng, too? |
- use the real project location and not some sf.net mirror - the meta attribute shouldn't point users to a website cluttered with ads (sf.net) where they probably just follow the link to the real project location - adapted the build to the new archive
@typetetris: yes. The main implications are getting e-mails from hydra.nixos.org when build status changes and being a point of contact about the package. |
I guessed that much and am willing to do that. Should I add the commits to this pr too? |
Yes, let's merge that together. |
Motivation for this change
with ads (sf.net) where they probably just follow the link
to the real project location
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
My box didn't have nix 2 and with some
nix-shell -p nixUnstable
tried to build all derivations, whichseemed unlikely to be caused by this.
./result/bin/
)I also offer to take maintainership of procps-ng, if so desired.