Your message dated Wed, 17 Mar 2010 23:43:57 +0100 (CET)
with message-id <[email protected]>
and subject line Re: Bug#574374: qemu-kvm: does not really need to conflict
kvm, just replace it
has caused the Debian Bug report #574374,
regarding qemu-kvm: does not really need to conflict kvm, just replace it
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
574374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574374
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-kvm
Version: 0.11.1+dfsg-1
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.
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.
Related note: I have needed a lot of time today to realize that kvm in
squeeze is now called "qemu-kvm".
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...
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?
Thanks.
--- End Message ---
--- Begin Message ---
On Wed, 17 Mar 2010, Michael Tokarev wrote:
> Santiago Vila wrote:
> > 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).
Oops! Sorry for the noise. You are right. I missed the last release,
in which the upgrade is actually smooth (by way of conflicts and
replaces being versioned). I've just tested it.
Closing then.
Regarding kvm in security/squeeze: I see that qemu-kvm is 6 days old,
so I expect that the real kvm should disappear from security/squeeze
in four days.
If such thing does not happen, I'll report it against ftp.debian.org.
Thanks.
--- End Message ---
