Skip to content
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

Jump to bottom

linuxPackages.wireguard: 0.0.20200128 -> 0.0.20200205 #79288

Closed
wants to merge 1 commit into from
Closed

linuxPackages.wireguard: 0.0.20200128 -> 0.0.20200205 #79288

wants to merge 1 commit into from

Conversation

d-xo
Copy link
Contributor

@d-xo d-xo commented Feb 5, 2020

Motivation for this change

https://lists.zx2c4.com/pipermail/wireguard/2020-February/004962.html

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@d-xo d-xo requested a review from Ma27 February 5, 2020 18:06
@Ma27
Copy link
Member

Ma27 commented Feb 5, 2020

Duplicate to f8a0576.

@Ma27 Ma27 closed this Feb 5, 2020
@d-xo
Copy link
Contributor Author

d-xo commented Feb 5, 2020

haha, too fast for me 😉 🙂

@d-xo d-xo deleted the wireguard-compat-0.0.20200205 branch February 5, 2020 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Ma27 Ma27 Awaiting requested review from Ma27

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@d-xo @Ma27