I had a chat with apw in #ubuntu-devel[1], and it looks like keeping the current order of dkms first, then modules, is correct.
This is the reason, in summary: "so that if you install this with a personal kernel, or a kernel without support you get the dkms not another kernel." The scenario could be you have no kernel which provides wireguard- modules. Then you apt install wireguard. If wireguard-modules comes first, apt will select some binary kernel package that has the modules, and install it. But you are still without the modules, because you have to boot the kernel. With dkms first, you at least get the chance to build the modules via dkms, and start using wireguard right away. If you have a kernel which provides wireguard-modules, then the "dkms- wireguard | wireguard-modules" will be satisfied, and dkms won't be installed. That all of course ignores the fact that installed kernel doesn't necessarily mean running kernel, but that's another issue. My seed change is then for bin:wireguard-tools. not bin:wireguard, because I don't want wireguard-dkms to appear in component mismatches. But maybe this is a tooling issue? Archive Admins, given the above, what do you prefer? 1. https://irclogs.ubuntu.com/2022/02/23/%23ubuntu-devel.html (not a super direct link because the log hasn't updated yet, but the conversation should be near the top) -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
