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

[Ian Campbell]

On Sat, 2012-07-14 at 20:03 +0200, Bastian Blank wrote:
> On Sat, Jul 14, 2012 at 11:39:01AM -0600, Ian Campbell wrote:
> > On Thu, 2012-07-12 at 12:37 -0600, Ian Campbell wrote:
> > > One possible solution would be to turn those virtual packages into real
> > > ones, at which point I expect the versioning would cause the expected
> > > upgrade.
> > Perhaps inevitably this wasn't quite sufficient. The problem is that
> > even if xen-hypervisor-amd64 becomes a real package on upgrade the
> > dependency is already satisfied by xen-hypervisor-4.0-amd64 so apt
> > doesn't do the upgrade.
> 
> This can be fixed by adding a version, like "(>> 0)"

I'll try this. I'd worry about it causing the 4.0 version to be
uninstalled too which would not be preferable, but we'll see.

> > I can't really think of a solution for this in Wheezy. However what we
> > can, and I think should, do for Wheezy is to add an explicit real
> > package "xen-hypervisor-latest-ARCH". It will still require manual
> > action on upgrade to Wheezy but things should then Just Work for Wheezy
> > +1.
> 
> No hacks.

I don't agree that this is a hack, having a metapackage as a real
package is a very normal way to do things. The linux-latest meta
packages are pretty much the same. I'd even argue that it less of a hack
than adding a spurious version to the depends.

Ian.