> 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! -- "do-release-upgrade -d" failed to compute upgrade from kubuntu dapper amd64 to hardy https://bugs.launchpad.net/bugs/221170 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
