[Bug 1884148] Autopkgtest regression report (ubuntu-release-upgrader/1:20.04.20)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-release-upgrader (1:20.04.20) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

update-manager/1:20.04.10.1 (armhf)
update-motd/3.6-0ubuntu6 (armhf, s390x, amd64, arm64, 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/focal/update_excuses.html#ubuntu-release-upgrader

[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 ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1884148

Title:
  dist upgrade process passes a number along with package to apport

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

Bug description:
  [Impact]
  The distribution upgrade process is passing to apport packages with numbers prepended to them, this then causes apport to crash and bugs about package installation failures not to be reported.

  [Test Case]
  1) Install the package pure-ftpd on an 18.04 LTS system
  2) Run 'do-release-upgrade -d' to upgrade to 20.04 LTS

  With the version of the dist-upgrader in the release pocket you'll
  receive the Traceback in comment #2.

  To test the dist-upgrader from -proposed you'll actually have to
  download and use the dist-upgrader tarball from
  http://archive.ubuntu.com/ubuntu/dists/focal-proposed/main/dist-
  upgrader-all/current/focal.tar.gz. When running that version of the
  dist-upgrader you should not receive a Traceback and have a pure-ftpd-
  common crash file in /var/crash/.

  This is actually also recreatable when upgrading from 19.10 to 20.04
  and that would be easier as you can use 'do-release-upgrader -p' to
  test the new version of the dist-upgrader.

  [Regression Potential]
  The code change is a just a simple check to see if the package name starts with a number which then removes the number. So the only chance of regression is the additional python code being bad which it isn't.

  Original Description
  --------------------
  The Ubuntu Error Tracker has been receiving reports about a problem regarding apport.  This problem was most recently seen with package version 2.20.11-0ubuntu40, the problem page at https://errors.ubuntu.com/problem/976abccbca7b548c9ccf155c80c8eb6f36efa7de 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/1884148/+subscriptions