wireguard-tools: 0.0.20190123 -> 0.0.20190227 #57534
Merged
+5
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@GrahamcOfBorg build wireguard-tools linuxPackages.wireguard |
GrahamcOfBorg
added
the
11.by: package-maintainer
|
@GrahamcOfBorg build wireguard-tools linuxPackages.wireguard |
|
build failures look like a missing dependency |
|
@elseym when bumping I tried to fix the breaking build with the following patch locally: diff --git a/pkgs/os-specific/linux/wireguard/default.nix b/pkgs/os-specific/linux/wireguard/default.nix
index e103de3e1b7..e13828d018a 100644
--- a/pkgs/os-specific/linux/wireguard/default.nix
+++ b/pkgs/os-specific/linux/wireguard/default.nix
@@ -1,4 +1,4 @@
-{ stdenv, kernel, wireguard-tools, perl }:
+{ stdenv, kernel, wireguard-tools, perl, libmnl }:
# module requires Linux >= 3.10 https://www.wireguard.io/install/#kernel-requirements
assert stdenv.lib.versionAtLeast kernel.version "3.10";
@@ -21,6 +21,8 @@ stdenv.mkDerivation rec {
nativeBuildInputs = [ perl ] ++ kernel.moduleBuildDependencies;
+ buildInputs = [ libmnl ];
+
buildPhase = "make module";
meta = with stdenv.lib; {However it breaks with the following error then: This is probaly related to some |
|
thank you, @Ma27 ! 🙇 |
Ensure that only module-related targets from the project's Makefile are built. Co-authored-by: elseym <elseym@me.com> Co-authored-by: Franz Pletz <fpletz@fnordicwalking.de>
|
@GrahamcOfBorg build wireguard-tools linuxPackages.wireguard |
Ma27
approved these changes
Mar 15, 2019
fpletz
approved these changes
Mar 15, 2019
Ma27
added a commit
to Ma27/nixpkgs
that referenced
this pull request
Mar 17, 2019
After working on the last wireguard bump (NixOS#57534), we figured that it's probably a good idea to have a basic test which confirms that a simple VPN with wireguard still works. This test starts two peers with a `wg0` network interface and adds a v4 and a v6 route that goes through `wg0`.
fpletz
pushed a commit
that referenced
this pull request
Apr 2, 2019
After working on the last wireguard bump (#57534), we figured that it's probably a good idea to have a basic test which confirms that a simple VPN with wireguard still works. This test starts two peers with a `wg0` network interface and adds a v4 and a v6 route that goes through `wg0`. (cherry picked from commit 0c4e9e3)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
update wireguard-tools
/cc @kirelagin
Things done
sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"./result/bin/)nix path-info -Sbefore and after)