On Fri, 2009-11-27 at 12:25 -0500, Ron Watkins wrote: > 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.
For unstable you could try the qemu-kvm package, which also has newer code than the kvm package. > 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? Neither qemu-kvm or kvm need the qemu package, the modified qemu source is 'self-contained' in qemu-kvm or kvm. > 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. As soon as qemu-kvm has had some more testers, it will replace the old kvm package in unstable (and then testing). -- Jan Lübbe <jlue...@lasnet.de> http://sicherheitsschwankung.de gpg-key 1024D/D8480F2E 2002-03-20 fingerprint 1B25 F91F 9E7B 5D4F 1282 02D6 8A83 8BE4 D848 0F2E -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
