Package: wireguard-linux-compat / 1.0.20210219-1

Metadata

Package Version Patches format
wireguard-linux-compat 1.0.20210219-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
0001 Makefile do not use git to get version number.patch | (download)

src/Makefile | 8 3 + 5 - 0 !
1 file changed, 3 insertions(+), 5 deletions(-)

 [patch] makefile: do not use git to get version number

Debian prefers to stick with the one in the source code.

Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

0002 Avoid trying to compile on debian 5.5 kernels Closes.patch | (download)

src/dkms.conf | 10 8 + 2 - 0 !
1 file changed, 8 insertions(+), 2 deletions(-)

 avoid trying to compile on debian 5.5 kernels (closes: #956241)

zx2c4 and Unit193 and i discussed this at length in IRC and couldn't
find a better way to express to DKMS that building the kernel is not
needed for debian's 5.5.0 kernel, since it has wireguard backported.

Note that the detection trick that we're using (looking for
wireguard.h in /lib/modules/5.5*) is still fairly crude.

We want to ensure that people running other distributed kernels
(e.g. raspberry pi? liquorix?) can still use debian's wireguard-dkms
to install wireguard.ko on their particular flavor of 5.5.  But if
they are building for the debian 5.5.0-1-* kernels, they won't need
it.

This is a bit sloppy because it means if you have both 5.5 from some
non-stock line *and* the headers for debian's stock 5.5.0-1-amd64 (for
example) installed, it will probably cause dkms to avoid building
wireguard.ko on the custom kernel.  But we decided that corner case is
too obscure to make it worth making the test logic here more complex
and fiddly.

Suggestions welcome for making this tweak more accurate as long as it
doesn't become more fragile.