Thanks Julian for the explanation, on what the affected path needs to have to trigger this. That might indeed reduce the set quite a bit.
You outlined the chain in this case in comment #9 already. The good thing here is that this is "inside" the domain of virt packages as it is in src libvirt. No need to change many other sources out there for this one. Let us have a look how far this would reach ... ./checkrdepends --no-ports --include-provides --suite resolute --archive-base 'http://archive.ubuntu.com/ubuntu' -b qemu-kvm [I'm reducing duplicates] This is the list of things that depend on qemu-kvm: - libvirt-daemon-driver-qemu[-hwe] -> qemu-kvm|qemu-system - nova-compute-kvm -> qemu-kvm|qemu-system - aqemu -> qemu-kvm|qemu-system-x86|qemu-system-arm|qemu-system-mips|qemu-system-ppc|qemu-system-sparc|qemu-system-misc - debvm -> qemu-system-native|qemu-kvm|qemu-system-any - ganeti -> qemu-kvm|xen-system-amd64 - ikvswitch -> qemu-kvm|qemu-system-any - uvtool-libvirt -> qemu-kvm That is quite bunch and many of them usually not having delta. These are all bare unversioned. If I understand this right, the situation always occurs when any of that is now pulled in via a recommends. libvirt-daemon-driver-qemu: Reverse-Recommends ================== * libvirt-daemon * libvirt-daemon-hwe debvm: Reverse-Recommends ================== * debusine-worker uvtool-libvirt: Reverse-Recommends ================== * uvtool Which translates in those paths to exist today: - debusine-worker -R-> debvm -D-> qemu-system-native|qemu-kvm|qemu-system-any - uvtool -R-> uvtool-libvirt -D-> qemu-kvm - libvirt-daemon -R-> libvirt-daemon-driver-qemu -D-> qemu-kvm|qemu-system - libvirt-daemon-hwe -R-> libvirt-daemon-driver-qemu-hwe -D-> qemu-kvm|qemu-system That is two more paths than the one we knew. But there is no protection that no others would be added some day or even outside our control (PPAs or any such). And while uvtool is rarely touched these days and Ubuntu only (no problem with the change to be added), debusine is without delta, changing frequently and the whole complexity here is Ubuntu only :-/ Given that we found there are other "prio: extra" in the archive, I'm tempted to want to evaluate how they got that state and if we could go for the same. Before we then consider changing all those packages as fallback solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2148469 Title: `libvirt-daemon-driver-qemu` prefers `qemu-system-x86-hwe` to satisfy `qemu-kvm | qemu-system` dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2148469/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
