Comment 10 for bug 990740

Is anyone here seeing this bug when running do-release-upgrade / update-manager *before* trying to dist-upgrade by hand?
If so, can you please give me some more information that I can use to reproduce this? A list of packages you have installed would be helpful. And APT logs. https://wiki.ubuntu.com/DebuggingUpdateManager

> As has been reported in this bug a number of times, do-release-upgrade
> doesn't work either.

The reports mentioning that looked like they'd tried to dist-upgrade first.

> But to that point, I would call it a failing that a process needs to be
> wrapped around "apt-get dist-upgrade" to handle, uhm,
> *dist*tribution*-upgrade*s.

Regardless of your opinion of that, having a tool that handles all the details of a distribution upgrade (which is more complex than just an apt dist-upgrade) makes peoples lives a lot easier. It means you don't have to read long release notes mentioning every possible pitfall we know about, that you may run into. update-manager can just know how to avoid them, itself.

apt's dist-upgrade is just an apt upgrade that allows package removal. It's not an all-in-one distribution upgrade tool.

> Well, that didn't work here either. I upgraded apt and dpkg and still
> needed to override the apt configuration variable to finally get it to
> install.

Which is the kind of thing you need to do when upgrading by hand, rather than using upgrade-manager. It's perfectly doable, just not that quick and easy.

I'd like to help, but I haven't got much concrete data to work on here.