xen-meta only depends on Xen 3.2 packages

Bug #323546 reported by Evan Broder on 2009-01-31
Affects Status Importance Assigned to Milestone
Hardy Backports

Bug Description

hardy-backports provides Xen 3.3, but the xen-meta packages explicitly depend on the 3.2 versions of the various Xen packages.

Ideally, I think this would be solved by creating 4 packages: ubuntu-xen-{server,desktop}-3.{2,3}, and having ubuntu-xen-server depend ubuntu-xen-server-3.2 | ubuntu-xen-server-3.3, but I'm not entirely convinced I know how to do that transition cleanly.

So instead, I'll attach a slightly less ideal fix that should more or less get the job done.

Evan Broder (broder) wrote :

This fix has the unfortunate property that the dependencies could be satisfied by a mixture of 3.2 and 3.3 packages, but it's more straightforward to convince yourself that it should work.

Evan Broder (broder) wrote :

Oh wait - let me set the target release correctly. Let's try this patch instead...

Evan Broder (broder) wrote :

As per discussion on IRC, I've updated my patch to explicitly depend on the Xen 3.3 versions of all packages, instead of creating the possibility of mixing and matching.

John Dong (jdong) wrote :

ACK'ed and uploaded last debdiff. For the record, the IRC discussion was that

(1) Alternate dependencies on 3.2/3.3 are just more confusing for the user and doesn't really offer anything additional -- you can't mix 3.2 and 3.3 and expect things to work, though these dependencies would allow it.

(2) Creating new -3.2/-3.3 metapackages will pose headaches for upgrades.

(2) Instead, we will offer pure-3.3 dependencies in hardy-backports such that it will take a dist-upgrade / explicit upgrade to install the backport, and it forces all the 3.3 packages to be installed.

Scott Kitterman (kitterman) wrote :


Changed in hardy-backports:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers