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

[20.03] backport protonvpn cli ng 2.2.0 -> 2.2.2 #82896

Merged

Conversation

JeffLabonte
Copy link
Contributor

@JeffLabonte JeffLabonte commented Mar 19, 2020

Motivation for this change

Keep security tool up-to-date

Things done

Backport PR #81735

  • 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.

Simply keep up to date the cli since it is used to connect to a VPN.

(cherry picked from commit eb96574e9df3aba387c4abe902b154398271becf)
Reason: A tool to communicate with a VPN provider should be kept
up-to-date
@JeffLabonte JeffLabonte changed the base branch from master to release-20.03 March 19, 2020 00:18
@JeffLabonte JeffLabonte changed the title 20 03 backport protonvpn cli ng [20.03] backport protonvpn cli ng Mar 19, 2020
@JeffLabonte JeffLabonte changed the title [20.03] backport protonvpn cli ng [20.03] backport protonvpn cli ng 2.2.0 -> 2.2.2 Mar 19, 2020
@Mic92 Mic92 merged commit 82ab717 into NixOS:release-20.03 Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants