[Bug 1787649] Re: ubuntu-release-upgrader crashed with SystemError: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

[Łukasz Zemczak]

Hello errors.ubuntu.com, or anyone else affected,

Accepted ubuntu-release-upgrader into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:18.04.26 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1787649

Title:
  ubuntu-release-upgrader crashed with SystemError: E:Error,
  pkgProblemResolver::Resolve generated breaks, this may be caused by
  held packages.

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  As documented in bug 1766890 some system were having failing to upgrade due to trigger issues with gnome-menus and ubuntu-release-upgrader was modified to upgrade libc6 first because that would fix that. However, in some rare cases this causes an issue for apt's problem resolver and the upgrade can't be calculated. Instead of leaving people on an unsupported we should try and upgrade them the way we used to - by not upgrading libc6 first.

  [Test Case]
  We actually haven't found a situation where upgrading libc6 first will create a issue for apt's problem resolver, but testing upgrades to ensure there are no regressions should be sufficient. Additionally, we can watch the bucket in the Ubuntu Error Tracker (referenced below) to ensure that the new version of ubuntu-release-upgrader doesn't appear there.

  [Regression Potential]
  A typo in the new code could cause a different Traceback, but it all looks good to me.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-release-upgrader.  This problem was most recently seen with package version 1:18.04.24, the problem page at https://errors.ubuntu.com/problem/2295855a1a01cc3182184b45e474b7af0ea7f46b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1787649/+subscriptions