[Pkg-xen-devel] Bug#681376: Bug#681376: Xen hypervisor package not upgraded on dist-upgrade Squeeze to Wheezy

[Ian Campbell]

On Sat, 2012-07-14 at 19:59 +0200, Bastian Blank wrote:
> On Thu, Jul 12, 2012 at 12:37:52PM -0600, Ian Campbell wrote:
> > I recently upgrade from Squeeze to Wheezy on a system which had the
> > xen-linux-system-686-pae metapackage (one of two which Provides:
> > xen-linux-system). After dist-upgrade I had the new xen-utils-common and
> > xenstore-utils (and a few others) but not the xen-utils-4.1 or
> > xen-hypervisor-4.1-i386 or xen-hypervisor-amd64 package. (dpkg -l
> > "*xen*" output is below).
> > 
> > I have marked this bug important since I think failure to upgrade is "a
> > major effect on the usability of a package".
> 
> Please show the actual error. The old versions should still work without
> problems. While this is no ideal state, it is not broken by itself.

The error is that after upgrade the system has only the Squeeze version
of Xen and not the new Wheezy version unless the administrator takes
manual steps. They should not have to do this.

> Wheezy will be the first release where there will be some sort of cross
> compatibility. So an automatic upgrade can work.
> 
> > I think this is because the dependency chain is:
> > xen-linux-system-686-pae
> >  -> xen-linux-system-3.2.0-3-686-pae
> >    -> xen-hypervisor-amd64 | xen-hypervisor-i386
> 
> There is no dependency for the utils package.

If the upgrade works correctly for xen-hypervisor-FOO then the matching
utils will get installed due to the recommends from
xen-hypervisor-4.1-FOO

> > At the very least this issue needs to be added to the release notes
> > since the is currently an extra manual step required during upgrade.
> 
> There is no change from earlier releases, so it does not really need it.

Well even better is if there is no manual step needed at all, which
would be my preference.

Ian.