[Bug 1913476] Autopkgtest regression report (update-manager/1:20.10.3)

Ubuntu SRU Bot 1913476 at bugs.launchpad.net
Fri Jan 29 01:44:40 UTC 2021


All autopkgtests for the newly accepted update-manager (1:20.10.3) for groovy have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:20.10.14 (ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#update-manager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  /usr/bin/update-manager:TypeError:/usr/bin/update-
  manager at 118:start_update:start_available:refresh_cache:update:_make_groups:__contains__

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Focal:
  In Progress
Status in update-manager source package in Groovy:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager.  This problem was most recently seen with package version 1:20.04.10.3, the problem page at https://errors.ubuntu.com/problem/b4e18d21aa7526e3a98130b1556e4d38ffaff9e0 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/.

  [Impact]

   * With update-manager versions 1:20.04.10.3 or 1:20.10.2,
     update-manager would crash while processing the apt
     cache.

  [Test Case]

   * Look at the Error Tracker issues and make sure the 
     versions 1:20.04.11 and 1:20.10.3 do not cause this
     same error.

  [Where problems could occur]

   * If apt is ever processing a package without the name
     field, it couldcause a crash. This scenario would likely
     cause a crash in many other parts of the code other than
     what is being changed here

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+subscriptions



More information about the foundations-bugs mailing list