[Pkg-xen-devel] Bug#606590: Bug#606590: Upgrading from Lenny leaves xen-hypervisor-3.2-1-amd64 in and doesn't install 4.0

[Thomas Goirand]

On 12/10/2010 04:48 PM, Bastian Blank wrote:
> severity 606590 important
> thanks
> 
> On Fri, Dec 10, 2010 at 03:55:09PM +0800, Thomas Goirand wrote:
>> Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64
>> installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually
>> to have it installed after a dist-upgrade. This for sure, isn't the expected
>> behavior.
> 
> Yes it is. As with every versioned binary package.
> 
> Bastian

Hi Bastian,

Thanks for being prompt to reply.

Please confirm: is the expected behavior is to not upgrade Xen to 4.0,
and leave the old version of Lenny installed, which cannot start the
Squeeze kernel? If so, why did you do such a choice? I don't get it...
Maybe your answer with what's bellow will explain it.

Is there a binary package that I didn't install, that is not versioned,
that should have pull the updated library? If it doesn't exist,
shouldn't we create one, so that upgrades are smooth in the future? I
mean, there's a linux-2.6 package, that makes the upgrade to
linux-2.6.32-5 automatic. Should we have a "xen-system" package or
something like that, that pulls the upgrades too?

As an advanced user, system administrator, and contributor to Debian, of
course, it was easy for me to understand fix. I'm sure it wont for
others! Even so, for people like me that do understand, it's not
convenient at all, as this require yet another manual apt-get of both
xen-utils-4.0 and the hypervisor. Can't we find a solution somehow?

Please let me know if I'm missing something here.

Thomas Goirand (zigo)