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
linuxPackages.wireguard: 0.0.20200121 -> 0.0.20200128 #78726
Conversation
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.
lgtm 🐱 ✨
@Ma27 From your lnk to the mailing list, this is just a compat update for kernels >= 5.5, so I don't think this requires a backport to stable. |
Uhm, it's actually a compat-update for the kernels |
Yes, but the update |
Ah I guess I misunderstood you. The thing is, we usually backport wireguard versions and I'm not a big fan of skipping versions in that case in general as this means that whoever needs to backport the next version, gets to resolve a merge-conflict. |
Valid argument. So +1 for a backport from me as I don't expect the update to break anything on stable. |
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.
LGTM.
Backported as b1a1ada. |
linuxPackages.wireguard: 0.0.20200121 -> 0.0.20200128
Motivation for this change
https://lists.zx2c4.com/pipermail/wireguard/2020-January/004905.html
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)