Unable to upgrade from 13.10 to 14.04 - tk8.5-lib fails to upgrade to libtk8.5

Bug #1280782 reported by Bruno Thomsen
206
This bug affects 39 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Fix Released
High
Brian Murray

Bug Description

It fails with a generic error about using 3rd party packages, but who doesn't install extra packages?

TEST CASE:
On a minimal installation of Saucy
1. Install erlang-gs or gitk or any reverse dependency of tk (apt-cache rdepends tk)
  $ sudo apt-get install --no-install-recommends erlang-gs
2. Upgrade
  $ do-release-upgrade -d

EXPECTED RESULT
The upgrader calculates a successful upgrade path

ACTUAL RESULT
This bug

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205.4
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CrashDB: ubuntu
Date: Sun Feb 16 14:13:18 2014
InstallationDate: Installed on 2012-12-13 (429 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to saucy on 2014-02-16 (0 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Bruno Thomsen (bruno-thomsen) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

From VarLogDistupgradeAptlog.txt:

Investigating (8) tk [ amd64 ] < 8.5.0-2ubuntu5 -> 8.6.0+6ubuntu1 > ( libs )
Broken tk:amd64 Breaks on tk8.5 [ amd64 ] < 8.5.11-2ubuntu4 -> 8.5.15-2ubuntu2 > ( libs ) (< 8.5.14-3)
  Considering tk8.5:amd64 0 as a solution to tk:amd64 4
  Upgrading tk8.5:amd64 due to Breaks field in tk:amd64
Investigating (8) tk8.5 [ amd64 ] < 8.5.11-2ubuntu4 -> 8.5.15-2ubuntu2 > ( libs )
Broken tk8.5:amd64 Depends on libtk8.5 [ amd64 ] < none -> 8.5.15-2ubuntu2 > ( libs ) (= 8.5.15-2ubuntu2)
  Considering libtk8.5:amd64 0 as a solution to tk8.5:amd64 0
  Holding Back tk8.5:amd64 rather than change libtk8.5:amd64
Investigating (9) tk [ amd64 ] < 8.5.0-2ubuntu5 -> 8.6.0+6ubuntu1 > ( libs )
Broken tk:amd64 Breaks on tk8.5 [ amd64 ] < 8.5.11-2ubuntu4 -> 8.5.15-2ubuntu2 > ( libs ) (< 8.5.14-3)
  Considering tk8.5:amd64 0 as a solution to tk:amd64 4
  Upgrading tk8.5:amd64 due to Breaks field in tk:amd64
Investigating (9) tk8.5 [ amd64 ] < 8.5.11-2ubuntu4 -> 8.5.15-2ubuntu2 > ( libs )
Broken tk8.5:amd64 Depends on libtk8.5 [ amd64 ] < none -> 8.5.15-2ubuntu2 > ( libs ) (= 8.5.15-2ubuntu2)
  Considering libtk8.5:amd64 0 as a solution to tk8.5:amd64 0
  Holding Back tk8.5:amd64 rather than change libtk8.5:amd64

Revision history for this message
Brian Murray (brian-murray) wrote :

Ah, some more details:

Broken libtk8.5:amd64 Conflicts on tk8.5-lib [ amd64 ] < 8.5.11-2ubuntu4 > ( libs ) (< 8.5.14-3)
  Considering tk8.5-lib:amd64 0 as a solution to libtk8.5:amd64 0
  Holding Back libtk8.5:amd64 rather than change tk8.5-lib:amd64

However, earlier we see:

  Installing libtk8.5 as Depends of tk8.5
    Installing libtcl8.5 as Depends of libtk8.5
       Removing: tcl8.5-lib
     Removing: tk8.5-lib

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → High
summary: - Unable to upgrade from 13.10 to 14.04
+ Unable to upgrade from 13.10 to 14.04 - tk8.5-lib fails to upgrade to
+ libtk8.5
tags: added: saucy2trrusty
tags: added: saucy2trusty
removed: saucy2trrusty
Revision history for this message
Christopher (soft-kristal) wrote :

I uninstalled a number of third party applications: Steam. Splashtop and the like but it didn't help. There are still some bits and pieces left from Medibuntu, if that makes a difference.

Revision history for this message
Steve Langasek (vorlon) wrote :

The conflicts/replaces from libtk8.5 to tk8.5-lib and libtcl8.5 to tcl8.5-lib are versioned, and they shouldn't be since these packages are obsolete. It's possible that making these unversioned conflicts will be enough to let apt choose the right upgrade path.

description: updated
Revision history for this message
Christopher (soft-kristal) wrote :

For what it's worth, my laptop is also an AMD64 while my desktop running Intel has no issues with the upgrade.

Changed in ubuntu-release-upgrader (Ubuntu):
assignee: nobody → Brian Murray (brian-murray)
status: Triaged → In Progress
Revision history for this message
Brian Murray (brian-murray) wrote :

This package change seems to have resolved it.

tcltk-defaults (8.6.0+6ubuntu2) trusty; urgency=medium

  * Add conflicts on tk-lib and tk8.5-lib to facilitate apt choosing the
    correct upgrade path (LP: #1280782)
 -- Brian Murray <email address hidden> Mon, 03 Mar 2014 13:29:52 -0800

Revision history for this message
Brian Murray (brian-murray) wrote :

There haven't been any new reports of this since March 2nd, so I'm going to close this as Fix Released.

Changed in ubuntu-release-upgrader (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Christopher (soft-kristal) wrote :

It's still a bug on my AMD64 laptop as of this morning. There must be something specific installed, as I upgraded one of my testing (unstable) partitions on the same machine back in December.

Revision history for this message
Christopher (soft-kristal) wrote :

I quit both classicmenu-indicator and Gnome Encfs Manager and am upgrading as I write. The only recent update was to ca-certificates.

Revision history for this message
Brian Murray (brian-murray) wrote :

The update necessary to fix this bug was an update to a package in Trusty, so you wouldn't actually notice an update to a package. Well unless you were running trusty in which case you wouldn't experience the bug.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'm reopening this report. According to bug 1288625 it is still an issue with tk 8.6.0+6ubuntu2.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Brian Murray (brian-murray) wrote :

Ah we also need conflicts for tcl-lib and tcl8.5-lib. I've added those and uploaded a new tcltk-defaults package. Thanks for reopening this.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Christopher (soft-kristal) wrote :

I'm going to add my two cents in case other people have the same issues. The upgrade proceeded after closing classicmenu-indicator. Also, there were installation bugs during the upgrade process which continued to clog the system until I removed all traces of what Medibutu had installed. apt-get autoclean removed what Synaptic didn't.

Since then, my system is running optimally.

Revision history for this message
Volkan Gezer (volkangezer) wrote :

If this will affect Trusty, how will be able to upgrade into it using this manager?

Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 1280782] Re: Unable to upgrade from 13.10 to 14.04 - tk8.5-lib fails to upgrade to libtk8.5

On Thu, Mar 06, 2014 at 05:54:32PM -0000, Volkan Gezer wrote:
> If this will affect Trusty, how will be able to upgrade into it using
> this manager?

The release upgrader downloads information about packages from the
release you are upgrading to, Trusty in this case, and then tries to
calculate the upgrade. The upgrade calculation has been failing due to
package transitions. However, with the changes I've made the release
upgrader will now be able to calculate the upgrade correctly.

--
Brian Murray

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

tcltk-defaults (8.6.0+6ubuntu3) trusty; urgency=medium

  * Add conflicts on tcl-lib and tcl8.5-lib to facilitate apt choosing the
    correct upgrade path (LP: #1280782)

Changed in ubuntu-release-upgrader (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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