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
gnupg22: 2.2.10 -> 2.2.11 #49831
gnupg22: 2.2.10 -> 2.2.11 #49831
Conversation
See http://lists.gnu.org/archive/html/info-gnu/2018-11/msg00003.html for release information
Success on x86_64-linux (full log) Attempted: gnupg22 Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: gnupg22 Partial log (click to expand)
|
cherry-picked to staging-18.09: cff4cb6 |
I actually did push it to 18.09 along side with other cherry-picks this morning… (76a06b0) Should I revert this backport to release-18.09 and wait for |
oh, whoops. Given the amount of rebuilds I think this should only go to staging? I'm not sure though. |
Yes, I guess I should have gone for that approach, but hydra seems to have done a good job at the moment: https://hydra.nixos.org/eval/1489936 (less than 200 jobs to go at the moment). And I actually said in the PR message that I would backport those to But since it is done, and hydra already did most of the job, I think we should leave it there. |
Yeah, fair enough. It should merge fine. Comments mentioning your backport, or a reference in the backport commit to the PR, would be helpful to make it visible that you've backported it :) |
Motivation for this change
See http://lists.gnu.org/archive/html/info-gnu/2018-11/msg00003.html for
release information
Once merged, I’ll backport this to
staging-18.09
andstaging-18.03
since this is a maintenance release.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)