On Fri, Nov 27, 2009 at 12:25:06PM -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.
unfortunately it appears so, yes. > Since not even unstable has a version of KVM that works with your > package, pushing that conflict down into testing is just inane. i believe it was pushed by the security team because of security issues that hadn't yet migrated to testing. i don't think the correlary issues have yet been fixed in unstable's kvm, so that's still unresolved. > 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. depending on what parts of qemu you need, you might be able to just install qemu-user and/or qemu-system instead of qemu and qemu-utils. alternately, try the new qemu-kvm packages in unstable instead of kvm. taking a brief glance at it, i don't think qemu-kvm conflicts with qemu-utils. it's maintained by the same maintainers as kvm, so is likely to replace kvm entirely. and additionally, i don't think qemu technically conflicts with the version of kvm in testing, so you could rebuild packages yourself with the conflicts removed, as long as you don't install kvm from unstable. the syntax for conflicts is unfortunately not flexible enough to specify a range of conflicting versions. i.e. the current versions of kvm in stable, testing and experimental don't conflict with qemu-utils, but the version in unstable does. if a non-conflicting version of kvm hits unstable before the conflicting version makes it to testing, we could probably remove the conflict entirely, as it was only a limited range of conflicting package versions (kvm 85+dfsg-*) that haven't yet made it to testing. > KVM is tightly coupled to QEMU; it *requires* QEMU to work. You've added a > conflict with a *dependent* package? kvm, as currently packaged in debian, is it's own fork of qemu; it doesn't require the qemu packages. > What the hell are you thinking? i'm thinking comments like that don't improve the situation. please, mistakes happen. > 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. it was probably pushed too early, by people outside of the qemu team. sure, better coordination could happen. apologies. live well, vagrant -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
