Unresolvable problem message does not help users and results in less useful bug reports

[Brian Murray]

In UpdateManager/UpdateManager.py the following code exists:

    except SystemError, e:
        msg = ("<big><b>%s</b></big>\n\n%s\n'%s'" %
               (_("Could not calculate the upgrade"),
                _("An unresolvable problem occurred while "
                  "calculating the upgrade.\n\n"
                  "Please report this bug against the 'update-manager' "
                  "package and include the following error message:"),
                e)
               )

The upgrade may not be calculated for a couple of reasons. As an example we have:

E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

 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

update-manager knows, or should know, if you are upgrading to a pre-release or running one and should notify the user to try again as this may be due to archive inconsistencies rather than having them file a bug right away.

[Paolo Rotolo (paolorotolo)]

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!

[RedSingularity (redsingularity)]

Hey Brian, are you going to take care of this one or should I assign it to Michael?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Brian Murray (brian-murray)]

I plan on working on this real soon now.

[Robert Roth (evfool)]

@Brian Murray: what's the status? DId you manage to find out anything on this?

[Brian Murray (brian-murray)]

The same message is produced by ubuntu-release-upgrader's DistUpgrade/DistUpgradeCache.py. These issues should be resolved in tandem.

[Brian Murray (brian-murray)]

Users who have a package in the removal blacklist:

LP: #1245037/VarLogDistupgradeMainlog.txt:2013-10-26 13:40:53,234 ERROR Dist-upgrade failed: 'The package 'postgresql-8.4' is marked for removal buLP: #1245037/VarLogDistupgradeMainlog.txt:2013-10-26 13:40:53,234 ERROR Dist-upgrade failed: 'The package 'postgresql-8.4' is marked for removal but it is in the removal blacklist.'

Will also see this same error message which actually doesn't fall into any of the conditions listed.

[Cylgalad (cylgalad)]

I can't upgrade to saucy (from raring) because of this "bug", which looks very much Microsoftian to me btw.
Is there anything to do to know what's offending the upgrader so I can upgrade to saucy before the next upgrade?

[Brian Murray (brian-murray)]

Log files for the distribution upgrade are kept in /var/log/dist-upgrade. You'll want to start by looking at main.log.

[Cylgalad (cylgalad)]

Thanks but main.log is not very informative.
At first I thought it was lack of lubuntu-desktop (and the crap it installs like OBSOLETE xscreensaver) that was the problem, but I did apt-get install lubuntu-desktop and after that the upgrade still failed.

I must say that ubuntu's upgrade process is a real PIA, but generally the problems happen *after* the upgrade not *before* !
I may want to go back to a distro that is always up-to-date.

[Christian Dywan (kalikiana)]

> grep ERROR /var/log/dist-upgrade/main.log
2014-11-21 13:32:56,186 ERROR Dist-upgrade failed: 'Das Paket »ubuntu-desktop-next« ist zum Löschen vorgesehen, wurde aber durch das System gesperrt.'

For me the log did contain the offending failure. Question is, why doesn't the UI handle this. Showing the very same error message, which is even localized, would help a lot, even if it means manually taking care of it.

[DLMiller (dlm-miller)]

So what is the resolution to problem seems it was reported in 2012. All I want to do is upgrade to Ubuntu 15.04