Santiago Vila wrote: > Package: qemu-kvm > Version: 0.11.1+dfsg-1 Note that current version is 0.12.3+dfsg-4. JFYI.
> I see that qemu-kvm uses these fields: > > Package: qemu-kvm > Replaces: kvm > Conflicts: kvm > > The "Conflicts: kvm" is not really necessary. It forces kvm to be > removed before qemu-kvm may be installed. However, just using a > Replaces will make both packages to be installed, then deborphan will > mark kvm as suitable to be uninstalled. > > The reason I consider this as a bug is that people will have to think > twice before telling apt that it's ok to remove the currently installed kvm. > > On the other hand, if the upgrade is set up so that kvm is upgraded > and qemu-kvm installed as a new package, the user will not have to > think so much and the upgrade will be smoother. I've read this, and re-read this, and re-read this again, but I still don't see your point. As in: not at all. Note that in the new version I changed Conflicts/Replaces to be versioned, because we've now a transitional dummy package, just like you did with diff=>diffutils rename. > To see what I mean: This is what happens with diff/diffutils from > lenny to squeeze while doing "apt-get dist-upgrade": > > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following NEW packages will be installed: > diffutils > The following packages will be upgraded: > diff > 1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. This is exactly what will happen with 0.12.3+dfsg-4 as currently in unstable. But I've left all the Conflicts/Replaces in place (albiet versioned). As far as I can see, Conflicts is to prevent installing "real" old kvm while qemu-kvm is installed. I might be wrong. > Related note: I have needed a lot of time today to realize that kvm in > squeeze is now called "qemu-kvm". There was a bug asking for smooth upgrade path, -- that's why I created the dummy transitional package. > The fact that there is still a *real* kvm package in the squeeze branch > of security.debian.org probably has something to do with this... Oh, in *squeeze* ?? I'll take a look. It should not be there. > Question: Could you please ask for it to be removed? Or maybe it will > be done automatically once the qemu-kvm package currently in unstable > enters testing? Dunno. But we've asked for kvm to be removed from testing already -- the old one (kvm-85). It was before we created the dummy transitional package... I'll ask around, thanks for the heads-up! Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
