Ubuntu
gtk+2.0 package

Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks - does not replace gir1.0-gtk-2.0 with gir1.2-gtk-2.0

Bug #963069 reported by Jean-Baptiste Lallement
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gtk+2.0 (Ubuntu)
Fix Released
High
Martin Pitt
Precise
Fix Released
High
Martin Pitt

Bug Description

Lucid to Precise Universe Upgrade:

Failed to calculate the upgrade
https://jenkins.qa.ubuntu.com/job/precise-upgrade-lucid-universe/ARCH=amd64,LTS=lts,PROFILE=universe,label=upgrade-test/60/

TEST CASE:
1. On lucid up to date install libhigui-dev
2. run from a terminal, the following command:
  $ do-release-upgrade -d

See original description
Jean-Baptiste Lallement (jibel)
tags: added: precise rls-mgr-p-tracking
tags: added: dist-upgrade lucid2precise qa-daily-testing
Jean-Baptiste Lallement (jibel)
summary: Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks
+ with digikam and kipi-plugins installed
description: updated
Changed in update-manager (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in digikam (Ubuntu):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Martin Pitt (pitti) wrote : Re: Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks with digikam and kipi-plugins installed

It's still similar to bug 950676, but let's use this new one now that we have it. The libseed conflict helped a bit, though.

Jean-Baptiste Lallement (jibel)
Changed in update-manager (Ubuntu):
status: Triaged → New
Changed in digikam (Ubuntu):
status: Triaged → Invalid
summary: Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks
- with digikam and kipi-plugins installed
description: updated
affects: digikam (Ubuntu) → opencv (Ubuntu)
Jean-Baptiste Lallement (jibel)
summary: Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks
+ - libhighgui-dev
Jean-Baptiste Lallement (jibel)
Changed in opencv (Ubuntu):
status: Invalid → Confirmed
description: updated
Martin Pitt (pitti)
summary: Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks
- - libhighgui-dev
+ - libgtk2.0-dev
Revision history for this message
Martin Pitt (pitti) wrote : Re: Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks - libgtk2.0-dev

It seems it still cannot install libgtk2.0-dev:

Broken libgtk2.0-dev:amd64 Depends on gir1.2-gtk-2.0 [ amd64 ] < none -> 2.24.10-0ubuntu5 > ( libs )
  Considering gir1.2-gtk-2.0:amd64 3 as a solution to libgtk2.0-dev:amd64 5
  Removing libgtk2.0-dev:amd64 rather than change gir1.2-gtk-2.0:amd64

which is due to

Investigating (0) gir1.2-gtk-2.0 [ amd64 ] < none -> 2.24.10-0ubuntu5 > ( libs )
Broken gir1.2-gtk-2.0:amd64 Conflicts on gir1.0-gtk-2.0 [ amd64 ] < 2.20.1-0ubuntu2.1 > ( libs )
  Considering gir1.0-gtk-2.0:amd64 3 as a solution to gir1.2-gtk-2.0:amd64 3
  Holding Back gir1.2-gtk-2.0:amd64 rather than change gir1.0-gtk-2.0:amd64

So gir1.0-gtk-2.0 has the same score (3) than gir1.2-gtk-2.0, and apt refuses to replace it. As gir1.0-* were removed long ago, we need to find a way to increase the score of gir1.2-gtk-2.0.

summary: Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks
- - libgtk2.0-dev
+ - does not replace gir1.0-gtk-2.0 with gir1.2-gtk-2.0
affects: opencv (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in gtk+2.0 (Ubuntu):
status: Confirmed → New
no longer affects: update-manager (Ubuntu)
no longer affects: update-manager (Ubuntu Precise)
tags: added: rls-p-tracking
removed: rls-mgr-p-tracking
Changed in gtk+2.0 (Ubuntu Precise):
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Martin Pitt (pitti) wrote :

I tried:

 - Boot current lucid live system
 - Enable universe
 - sudo apt-get install --no-install-recommends libgtk2.0-dev gnome-shell
 - switch apt sources to precise
 - sudo apt-get update
 - sudo apt-get dist-upgrade

But that works, gir1.0-gtk-2.0 gets a score of 8, while gir1.2-gtk-2.0 gets a score of 365, so a clear winner.

Revision history for this message
Martin Pitt (pitti) wrote :

I can reproduce this when I try dist-upgrading in the QA VM for this.

 - Conflicts -> Breaks does not help
 - Versioned conflicts/breaks does not help
 - Adding Provides: gir1.0-gtk-2.0 does help, but is technically wrong
 - Dropping the conflicts/breaks works, but would not properly clean up
 - Adding an extra "Breaks: gir1.0-gtk-2.0" to libgtk2.0-dev helps. This seems like the best option to me right now.

Martin Pitt (pitti)
Changed in gtk+2.0 (Ubuntu Precise):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+2.0 - 2.24.10-0ubuntu6

---------------
gtk+2.0 (2.24.10-0ubuntu6) precise-proposed; urgency=low

  * debian/control.in: Add an extra Breaks: gir1.0-gtk-2.0, to nudge apt to
    remove this instead of keeping that obsolete and non-existing package
    during upgrades. (LP: #963069)
 -- Martin Pitt <email address hidden> Mon, 26 Mar 2012 13:25:39 +0200

Changed in gtk+2.0 (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.