[Intrepid] Should tell why it can not calculate a upgrade

Bug #281286 reported by sipickles
4
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Medium
Michael Vogt

Bug Description

Binary package hint: update-manager

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 This can be caused by:
 * Upgrading to a pre-release version of Ubuntu
 * Running the current pre-release version of Ubuntu
 * Unofficial software packages not provided by Ubuntu

If none of this applies, then please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport.

WORKAROUND:
Please use "update-manager --proposed" to get a version of the upgrader that fixes this issue.

Revision history for this message
sipickles (sipickles) wrote :
Revision history for this message
Daniel Hollocher (chogydan) wrote :

do you currently have ubuntu-desktop installed?

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug. Please add which version you were upgrading to which version.

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Daniel Hollocher (chogydan) wrote :

btw, my first question was a silly one. It looks like this might be the rarian-compat / scrollkeeper bug that happened awhile back? No idea if it was fixed.

But, sipickles, you should probably report whether you are still having this problem with the intrepid release candidate.

The problem in general with this kind of bug is that it can pop up, and last only a few hours, or maybe a few days. Then, its gone... So, there ends up not being much to fix.

If the problem is gone, please mark the bug invalid. Thanks.

Revision history for this message
Bart Kroon (bart-kroon) wrote :

On a machine with ubuntustudio hardy the update-manager informs me I can upgrade to 8.10 and then I get this error. Ubuntustudio has a package ubuntustudio-desktop but not ubuntu-desktop.

Revision history for this message
Bart Kroon (bart-kroon) wrote :

Maybe interesting:

Trying to install ubuntu-desktop was (according to synaptic) not possible because ubuntu-sounds could not get installed. Installing ubuntu-sounds however was possible (4 ubuntustudio- packages got removed including ubuntustudio-sounds). Afterwards ubuntu-desktop could be installed.

So it seems that
1) the update-manager tries to install ubuntu-desktop and fails at that,
2) it should not install ubuntu-desktop but upgrade ubuntustudio-desktop.

Revision history for this message
Bart Kroon (bart-kroon) wrote :

Same with ubuntu-desktop installed :S

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in update-manager:
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
Bart Kroon (bart-kroon) wrote :

After reading the tail of main.log, I decided to remove package postgresql-plperl-8.2 and that solved this problem.

I think this bug report should be rephrased as:

"Update manager gives error message (...) instead of informing user of problematic package(s)"

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

@Charlie:
Please use "update-manager --proposed" to get a version of the upgrader that fixes this issue. I agree that update-manger should display a message what package caused the problem (if it can figure that out, not always possible).

Revision history for this message
Michael Vogt (mvo) wrote :

Fixed in my jaunty branch.

Changed in update-manager:
assignee: nobody → mvo
status: Confirmed → Fix Committed
Revision history for this message
Michael Vogt (mvo) wrote :

@Charlie: the postgresql bug in also reported in #293486 (just FYI - there are instructions how to apply the fix there too).

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

@Michael: It would be better to direct these items at the reporter and Bart. All I did is triage on this bug. Thanks.

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.95.1

---------------
update-manager (1:0.95.1) jaunty; urgency=low

  * DistUpgrade/DistUpgrade.glade, DistUpgrade/window_main.ui:
    - show 9.04 upgrade target
  * debian/rules:
    - calculate demotions based on intrepid->jaunty
  * DistUpgrade/DistUpgradeCache.py:
    - when the dist-upgrade calculation fails, show the reason
      why in the error dialog (LP: #281286)
    - when a meta package can not be upgraded, show a proper
      error message with the package in question
  * DistUpgrade/DistUpgradeQuirks.py:
    - abort ugprade from hardy if evms is used in /proc/mounts
      evms got removed from the archive in intrepid (LP: #292179)
    - do not add "relatime" if "noatime" is already given (thanks
      to Ken Geis)
  * DistUpgrade/removal_blacklist.cfg:
    - remove overly broad postgresql regexp
  * DistUpgrade/DistUpgradeCache.py:
    - do not limit the removal blacklist to downloadable packages,
      this limits it too much
  * check-new-release:
    - install check for new releases into update-motd.d/daily

 -- Michael Vogt <email address hidden> Tue, 11 Nov 2008 11:22:41 +0100

Changed in update-manager:
status: Fix Committed → 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.