lucid->precise upgrade failure due to gir1.0->gir1.2 conflicts

[Martin Pitt]

The current lucid to precise upgrade fails to compute an upgrade path with universe packages, reproduced by https://jenkins.qa.ubuntu.com/view/Precise/job/precise-upgrade-lucid-universe/.

The apt.log is not that easy to read, but it seems to be due to the dependencies of libseed0 in lucid. Most packages (the OpenCV related ones) fail due to broken libgtk2.0-dev, which fails due to

Investigating (1) libgtk2.0-dev [ i386 ] < 2.20.1-0ubuntu2.1 -> 2.24.10-0ubuntu5 > ( libdevel )
Broken libgtk2.0-dev:i386 Depends on gir1.2-gtk-2.0 [ i386 ] < none -> 2.24.10-0ubuntu5 > ( libs )

which fails due to

Investigating (0) gir1.2-gtk-2.0 [ i386 ] < none -> 2.24.10-0ubuntu5 > ( libs )
Broken gir1.2-gtk-2.0:i386 Conflicts on gir1.0-gtk-2.0 [ i386 ] < 2.20.1-0ubuntu2.1 > ( libs )

which is pulled in by

  Installing gir1.0-gtk-2.0 as Depends of libseed0

Now, libseed0 and gir1.0-* do not even exist any more, so the correct solution would be to remove libseed0 and all gir1.0-* packages.

This might be an apt bug, but we might be able to work around it somehow.

[Rick Spencer (rick-rickspencer3)]

Please note that this bug is blocking upgrade testing.

[Robert Ancell (robert-ancell)]

Can you see what is trying to keep seed?

[Martin Pitt (pitti)]

I don't see that, but perhaps it's time to make libseed-gtk3-0 Breaks: libseed0 to clean it up on upgrades? Michael, could that help?

[Martin Pitt (pitti)]

I discussed that with Michael a bit, and he agrees that cleaning up libseed0 more aggressively might help us here. Either way that at least cannot hurt, so let's see how much further this gets us.

[Launchpad Janitor (janitor)]

This bug was fixed in the package seed - 3.2.0-1ubuntu1

---------------
seed (3.2.0-1ubuntu1) precise; urgency=low

  * debian/control.in: Conflicts/Replaces: the old libseed0, to make it
    slightly easier for apt to untangle the lucid -> precise migration path.
    (LP: #950676)
 -- Martin Pitt <email address hidden> Thu, 22 Mar 2012 12:03:04 +0100

[Martin Pitt (pitti)]

That helped a bit, but wasn't sufficient. Jean-Baptiste filed a new bug now (bug 963069), so using that one now.