Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61978 - [wireguard-lts] Depend on explicit kernel version

Attached to Project: Community Packages
Opened by Richard Neumann (rne) - Monday, 11 March 2019, 13:17 GMT
Last edited by Christian Hesse (eworm) - Monday, 11 March 2019, 13:21 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Feature request to add dependecy on specific kernel version.

Additional info:
* wireguard-lts 0.0.20190227-2
* linux-lts 4.19.28-1

Steps to reproduce:
The two up-to-date packages listed above do not work together:

$ modprobe wireguard
modprobe: ERROR: could not insert 'wireguard': Invalid argument

However they also do not cause any conflict on the package manager's level.
Hence, if the kernel module packages is updated later than the kernel package, which is currently the case, all WireGuard interfaces will be broken, causing the system to possibly be no longer reachable.
To resolve this issue, one can migrate to wireguard-dkms as I did for a quick fix, but I think, if the precompiled packages are provided, they should work with any current kernel version.

tl;dr:
I recomment adding a specific dependency on the respective kernel's version to the dependencies of wireguard-lts.
Possibly this also applies to the package "wireguard", for the mainline kernel.
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 11 March 2019, 13:21 GMT
Reason for closing:  Fixed
Additional comments about closing:  wireguard-lts-0.0.20190227-3

Loading...