By adding your conflict with KVM, you're now breaking systems, if the
administrators aren't paying attention. People running KVM, if they
want to KEEP running KVM, can't update QEMU. There is no
non-conflicting version of KVM available anywhere in testing or unstable.
Since not even unstable has a version of KVM that works with your
package, pushing that conflict down into testing is just inane. We're
broken and we can't fix it without going into experimental, and even at
that, a simple apt-get update/install won't work. It looks like we'll
have to manually go get the package and install it. KVM is tightly
coupled to QEMU; it *requires* QEMU to work. You've added a conflict
with a *dependent* package? What the hell are you thinking?
If you want to rearchitect your software and add conflicts, *coordinate
it with the people you're conflicting with*, especially when they're
married to your project at the freaking hip. You need to release at the
same time, or people end up stuck.
Grrrr.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
