Comment 8 for bug 2008086

> [ Impact ]

> * wireguard package has historic depends on wireguard-modules | wireguard-dkms, which are now useless. Wireguard module has been built-in since forever, and wireguard-dkms has been removed from the archive. Drop these as no longer required.

This doesn't describe how users of stable releases are impacted, which is necessary to consider if an SRU is appropriate. It's a true statement but not really part of any user impact as far as I can tell?

> * This can be safely dropped in jammy sru as well, to allow wireguard-tools userspace package to be installable with hwe kernels from lunar, and inside containers.

How does this impact users, though? What scenarios exist where users are trying to install wireguard-tools inside containers? Why can't you just provide the wireguard-modules Provides in your HWE backports from Lunar?

> 2) On Ubuntu Desktop (as shipped for the xinyi/desktop-fde project) with kernel provided by a snap, there is nothing in deb userspace that allows to install something that provies "wireguard-modules", meaning it is not possible to use wireguard.

Why can that project not provide an equivs-style deb that Provides: wireguard-modules in scenarios where it is ensuring that such a kernel is available? Wouldn't this reduce risk to existing users of Jammy?