Glad to hear the result. Thanks for working through this and hearing me
out on IRC as well.

With regards to the TODO:

> I suggest the server team to reach out to @unit193 as the MOTU who
maintained

Unit193 is really top-notch and knows the project well, is an active
participant with upstream, and generally is pretty on top of things. I
don't know whether MIRing this means some sort of hand off involved, but
I'd say that to the extent you can keep him in the fold, it's some nice
expertise to keep around.

> - does NOT have a test suite that runs at build time, we should add at least
>  the trivial autopkgtest generating and checking keys, as suggested
> - does NOT have a non-trivial test suite that runs as autopkgtest, we should
>  integrate more testing (LP: #1952102) as suggested by adding the new "vpn"
>  test and/or copying the non-trivial autopkgtest from wireguard-linux-compat

Let me know if you guys need help scripting these up. Indeed taking the
wireguard-linux-compat case is probably a good place to start. But if
you want something more elaborate and need a hand, just poke me on IRC.

>  + wireguard-dkms: recommended by wireguard-tools, it's part of the same 
> source
>    package, but we probably want to drop that, as we have the WireGuard 
> modules
>    in the kernel. Or at least we'd want to change Recommends: wireguard-dkms 
> to
>    Suggests: wireguard-dkms (LP: #1873288)

I'd suggest you sync up with @apw about this. He was involved in some of
the earlier discussions about this. And @unit193 too. Details are a bit
fuzzy to me, but I think there's something interesting happening with
the `wireguard` metapackage pulling in `wireguard-tools` and a
`wireguard-modules` virtual package. That `wireguard-modules` virtual
package is then satisfied by wireguard-dkms, wireguard-linux-compat, and
the various Canonical kernel packages. Or something like that. I don't
see a need for this to change. But...

> recommended by wireguard-tools, it's part of the same source package

This part confused me. Many many eons ago, WireGuard was one repo, with
src/* having dkms kernel sources and src/tools/* containing the tools
package. For a long long time now, this has been split up. But I wonder
if the wireguard-tools package still has something left over from the
days when dkms was mixed with it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950317

Title:
  [MIR] Wireguard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to