I've let people know in #ubuntu-kernel, so hopefully Canonical will take a look. To recap for whoever inherits this bug, the following things need to be done:
1. Add back the "Provides: wireguard-modules" in linux-image-generic. This is really important. It used to be there but has strangely been dropped, which is why this bug report was filed by a user.
I've let people know in #ubuntu-kernel, so hopefully Canonical will take a look. To recap for whoever inherits this bug, the following things need to be done:
1. Add back the "Provides: wireguard-modules" in linux-image- generic. This is really important. It used to be there but has strangely been dropped, which is why this bug report was filed by a user.
2.. Reverse the order of wireguard-modules and wireguard-dkms in both the Depends: and Recommends:. Importing the latest Debian package will do this: /salsa. debian. org/debian/ wireguard/ -/commit/ 2d36365079f4668 660963c5c819db3 b544c5d56f /salsa. debian. org/debian/ wireguard/ -/commit/ b536ea7e12ee259 e5d16e7e66a7b92 1837223023
https:/
https:/
3. Optional: tweak Debian's semantics for wireguard-dkms to handle the changed build exclusion based on Ubuntu's particulars. That involves modifying: /salsa. debian. org/debian/ wireguard- linux-compat/ -/blob/ debian/ master/ debian/ patches/ 0002-Avoid- trying- to-compile- on-debian- 5.5-kernels- Closes. patch
https:/