"do-release-upgrade -d" failed to compute upgrade from kubuntu dapper amd64 to hardy

Bug #221170 reported by to be removed on 2008-04-23
4
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

I was testing upgrades of Kubuntu on amd64 from dapper to hardy. I ran:

do-release-upgrade -d

The result: "Could not calculate the upgrade

A unresolvable problem occurred while calculating the upgrade."

(Manual copy-paste, sorry for any errors.) As per instructions I am reporting this as a bug.

I note that the similar upgrade worked for i386.

to be removed (liw) wrote :
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please try again with the instructions from the kubuntu upgrade web page? The do-release-upgrade command is aimed toward server use and behaves a bit differently from the desktop upgrade. You can switch that with do-release-upgrade -m desktop.

This whole update-manager/do-release-upgrade stuff is a bit awkward and we need to make that server/desktop mode stuff clearer (or unify it).

Changed in update-manager:
status: New → Incomplete
MarcRandolph (mrand) wrote :

> The do-release-upgrade command is aimed toward server use and behaves a bit differently from the desktop upgrade.

In what way? (that's mostly a retorical question - I'm taking your response that I should use the desktop upgrade, which I'm starting right now)
I can find no documentation or indication of different behavior. I have a mostly-headless machine that I treat as mostly a server. I'd rather do the upgrade via command line, and my assumption was that I could use "do-release-upgrade". Thankfully (and luckly), I did the following just for fun:

$ sudo update-manager -h

which produced:

/var/lib/python-support/python2.5/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
Usage: update-manager [options]

When I started searching on the GtkWarning, one thing lead to another and I eventually I stumbled upon this ticket.

> This whole update-manager/do-release-upgrade stuff is a bit awkward and we need to make that server/desktop mode stuff clearer (or unify it).

Yes please. One tool would eliminate confusion (and no telling how much wasted time, like the multiple hours I just did trying to read up on it, only to finally give up). Even the --help output for it is surprisingly unhelpful.

Thanks for all the hard work on Ubuntu!

Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers