I just realized that we have a better DEP8 test already running, but in another source package: src:wireguard-linux-compat, which produces bin:wireguard-dkms. With wireguard now being in the kernel, I wonder if we still need the dkms one. Maybe for cases where someone wants to try a newer version before the kernel is updated? Not sure.
In any case, we have good DEP8 coverage already, but split among different source packages: - src:wireguard-linux-compat: sets up a wireguard vpn using network namespaces, and uses ping to test it, similar to what I have done above - src:wireguard: just generates keys, and that test is marked correctly as superficial - src:netplan.io: also sets up a wireguard vpn, and exercises it These are all run together when a new wireguard upload happens. In that sense, we have good coverage, even if we decide to drop the dkms package. The netplan test would still exercise wireguard, but I think it does not use the wg or wg-quick tools to set it up, so we would still benefit from having another end-to-end test using those tools. So I can still add my test to src:wireguard, or copy over the one from src:wireguard-linux-compat. -- 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
