[SRU exception] backport 5.32 to Jammy and Mantic

[Skia]

[Impact]

This release contains both bug fixes and new features and we would like
to make sure all of our developers have access to these improvements.
It's a version bump from 5.28 to 5.32, so that's a big upstream upgrade with
lots of improvements, but here are the most notable ones for developers:

  * Overall improved riscv64 support
    - QEMU fixes
    - Better timeouts by default
  * Add --cpus to buildvm-ubuntu-cloud tool: this improves speed when building images
  * Bump default QEMU ram size to 2048 (Debian #1059840), making a lot of tests work better by default

See the changelog entry below for a full list of changes and bugs.

[Test Plan]

autopkgtest contains a test suite that is run using the SRU package for each
release. This test suite's results are available here:

Jammy (https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/)
Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240206_130746_30768@/log.gz

As expected, the tests failed, but they've been forever failing on this release (see https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240202_151346_e0140@/log.gz for example).
However, with the current ongoing effort to fix them, we see an improvement with the `schroot` test being now PASS, and only `unshare` being FAIL. Most of the rest is now marked as SKIPPED instead of uncontroled FAIL, which also helps in the road to a green status.

Mantic (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/)
Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240206_155746_00441@/log.gz

Unexpectedly, the tests are green on this release, which is a big improvement compared to the previous version (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240202_225722_a9ed0@/log.gz).
As for Jammy, not everything is PASS, but the failures are under enough control to be marked as SKIP when needed.

Additionally, the following PPAs should be tested manually at least under normal development conditions to ensure users will only be impacted by corner-case issues, should they arise:
https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-mantic/
https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-jammy/

Please take a particular attention to test the cross-arch feature, as there is no automated tests for this.
Here is the documentation on this feature: https://wiki.ubuntu.com/ProposedMigration#How_to_run_cross-architecture_autopkgtest_locally_using_QEMU
Be knowledgeable that the `mawk` is particularly well suited for these kind of tests.

[Where problems could occur]

Given the size of the changelog, there may be corner-cases that aren't
covered by the automated testsuite.
Also, with the differences in Python version, some library interfaces could have changed in untested code, leading to crashes.
Given that this tool is mainly used by developers, users are likely to find workarounds or report bugs when they find them.

[Changelog]

autopkgtest (5.32ubuntu2) noble; urgency=medium

  * Fix traceback in cross-arch testing (LP: #2051593)
  * Update cross-arch patchset from latest snapshot

 -- Paride Legovini <email address hidden> Mon, 29 Jan 2024 22:46:58 +0100

autopkgtest (5.32ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP: #2049737)
    Remaining changes:
    - Add support for cross-architecture testing.

 -- Paride Legovini <email address hidden> Tue, 23 Jan 2024 12:00:37 +0100

autopkgtest (5.32) unstable; urgency=medium

  [ Florent 'Skia' Jacquet ]
  * d/t/schroot: better use of existing variables
  * d/t/schroot: allow running behind a proxy

  [ Simon McVittie ]
  * testarchive: Fix a pycodestyle warning
  * Standards-Version: 4.6.2 (no changes required)
  * qemu: Use 4M OVMF images if available

  [ Stefano Rivera ]
  * Testbed: Kill with SIGKILL if SIGTERM doesn't do the job in 10 seconds
    (Closes: #1059444)

  [ Paul Gevers ]
  * tests: increase sleep in test_timeout() for lxd test (Closes: #1020634)
  * autopkgtest-virt-qemu: raise time for command prompt return
  * virt-qemu: add context to several timeout errors

  [ Michael Biebl ]
  * Bump default ram-size for virt-qemu to 2048 (Closes: #1059840)

  [ Colin Watson ]
  * Add Incus support

  [ Santiago Ruano Rincón ]
  * Make autopkgtest-build-qemu pass mirror info to setup-testbed
    (Closes: #1060426)

  [ Paul Gevers ]
  * tests: increase --timeout-build to accommodate for riscv64
  * tests: mark podman-init autopkgtest flaky for now

 -- Paul Gevers <email address hidden> Thu, 11 Jan 2024 14:06:22 +0100

autopkgtest (5.31.2) unstable; urgency=medium

  [ Florent 'Skia' Jacquet ]
  * d/control: add genisoimage as suggested package.
    It's used in `autopkgtest-buildvm-ubuntu-cloud`.

  [ Paul Gevers ]
  * autopkgtest-build-qemu: drop use of qemu-debootstrap.
    This is not needed in Debian 11 or newer. (Closes: #1038826)

  [ Simon McVittie ]
  * d/rules: Don't fail the build if a lint check fails (Closes: #1058550)
  * qemu, testdesc: Convert "# type:" comments into variable annotations.
    This avoids unused import warnings with current versions of pyflakes.

 -- Simon McVittie <email address hidden> Sun, 24 Dec 2023 16:50:37 +0000

autopkgtest (5.31.1) unstable; urgency=medium

  * runner: fix architecture wildcard support broken in 30d5aa7
  * runner: fail badpkg in case no source was found like before 30d5aa7

 -- Paul Gevers <email address hidden> Sun, 12 Nov 2023 21:35:20 +0100

autopkgtest (5.31) unstable; urgency=medium

  [ Johannes Schauer Marin Rodrigues ]
  * lib/autopkgtest_qemu.py: use -machine type=virt,gic-version=max when
    running natively on arm64 for kvm acceleration

  [ Tim Andersson ]
  * add ssh connect timeout to ssh-setup/nova
  * setup-testbed: Set apt error mode as any

  [ Paul Gevers ]
  * adt_testbed: factor out add-apt-sources
  * adt_testbed: factor out get-default-release
  * adt_testbed: factor out shell code to create sources.lists
  * Rewrite of source version selection in Python
  * create-sources.list-for-pocket: minor logical improvements
  * add-apt-sources: some checks of input arguments

  [ Jochen Sprickerhof ]
  * Update resolv.conf in unshare chroot

  [ Samuel Thibault ]
  * Fix hyphens in manpages

  [ Mateus Rodrigues de Morais ]
  * Add --cpus to buildvm-ubuntu-cloud tool

  [ Christian Kastner ]
  * qemu: Add option to poweroff gracefully

 -- Paul Gevers <email address hidden> Mon, 06 Nov 2023 20:40:32 +0100

autopkgtest (5.30) unstable; urgency=medium

  [ Christian Kastner ]
  * Set umask while initializing DebBinaries, fixing permissions errors
    when running virt-podman with a restrictive umask (Closes: #1032487)

  [ Helmut Grohne ]
  * virt-qemu: Use a lock file to resolve a race condition when allocating
    a port for ssh
  * build-{qemu,lxc}, buildvm-ubuntu-cloud: Explicitly pass RELEASE to
    setup-testbed when known
  * build-qemu: Don't use ext4 features unsupported in the target release

  [ Jochen Sprickerhof ]
  * qemu: Better riscv64 support
    - Use -machine=virt on riscv64
    - Specify a riscv64-compatible network device for all architectures

  [ Stefano Rivera ]
  * build-lxd: Explicitly reuse aliases with lxd >= 5.14, which will no
    longer overwrite an existing alias by default

  [ Simon McVittie ]
  * d/README.source: Add a policy for autopkgtest dependencies:
    - Host system: aiming to support latest Debian stable or Ubuntu LTS,
      and the previous stable/LTS if it's straightforward to do so
    - Testbed: aiming to support Debian 8+ or Ubuntu 14.04+
  * testbed: Use sudo -n true instead of sudo -n -v to detect
    ability to run sudo without password, resulting in it being detected
    successfully in more cases
  * testbed: Move more environmental setup into wrapper.sh
  * testbed: Factor out Perl code to parse dependencies
  * setup-testbed:
    - Remove code that was only needed for Ubuntu 12.04 on armhf
    - Only auto-detect RELEASE, MIRROR when necessary
  * tests:
    - Add a convenience `make check` target
    - Fix a failing qemu test
    - Run more tests in CI and during package build
    - d/tests/lxd: Fix test failure by installing recommended dnsmasq-base
      package
    - d/tests/lxd: Use stable image, fixing testing while
      images.linuxcontainers.org doesn't provide an image for trixie yet
    - Remove stale reference to SchrootClickRunner tests, which were removed
      in mid 2022
    - CI: Use testing instead of unstable, to avoid temporary regressions
      such as #1042498
    - CI: Test the unshare backend on stable instead of unstable
    - CI: Run basic tests on Debian 11
  * Fix some shellcheck warnings

  [ Paride Legovini, Simon McVittie ]
  * testbed: Install satdep using apt-get install /path/to/*.deb if possible
    (apt >= 1.1, available in Debian 9+ or Ubuntu 16.04+), falling back to
    using dpkg --unpack and apt-get -f install as before for Debian 8 and
    Ubuntu 14.04

  [ Gioele Barabucci ]
  * lib/VirtSubproc: Use explicit paths for commands in downtmp,
    fixing testbed failure if the default shell is changed to busybox
    during testing

  [ Antonio Terceiro ]
  * Add --timeout option, which sets a global timeout for all commands
    that are controlled by the source package being tested
    (the build if the needs-build restriction is present, and the tests
    themselves).

  [ Raphaël Hertzog ]
  * debian: Depend on mawk >= 1.3.4 for systime() function, required
    since 5.29

 -- Paul Gevers <email address hidden> Sun, 30 Jul 2023 19:31:21 +0200

autopkgtest (5.29) unstable; urgency=medium

  [ Brian Murray ]
  * Fix a typo

  [ Paride Legovini ]
  * Prevent --apt-pocket from setting the wrong default release
    (Closes: #1032314) (LP: #2009191)

  [ Antonio Terceiro ]
  * autopkgtest-virt-lxc: call timeout sudo instead of sudo timeout

  [ Helmut Grohne ]
  * autopkgtest-build-qemu: add --keyring argument
  * autopkgtest-build-lxc: add --keyring option for consistency with qemu
  * setup-testbed: check the testbed for init-availability
  * setup-testbed: reliably deny starting services

  [ Tim Andersson ]
  * Fix docker build command not returning 1 on failure, causing test to fail
    and not be marked as skippable when run behind a proxy
  * Add timestamps to logfile

 -- Antonio Terceiro <email address hidden> Wed, 14 Jun 2023 20:23:45 -0300

[Skia (hyask)]

Jammy debdiff

[Skia (hyask)]

Mantic debdiff

[Skia (hyask)]

Jammy big debdiff against existing package in `jammy-updates`

[Skia (hyask)]

Mantic big debdiff against existing package in `mantic`

[Skia (hyask)]

https://code.launchpad.net/~hyask/ubuntu/+source/autopkgtest/+git/autopkgtest/+merge/460170

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "jammy.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[Paride Legovini (paride)]

Set the Focal task as Wontfix as discussed.

[Paride Legovini (paride)]

I reuploaded to Jammy and Mantic making sure that the .changes file mentions the right bugs.

[Julian Andres Klode (juliank)]

Unsubscribing ubuntu-sponsors because this has been sponsored.

[Andreas Hasenack (ahasenack)]

12129s autopkgtest SKIP unknown restriction needs-sudo

These skips are annoying. Have you considered adding a delta to run the test as root and switch to a test user in the test itself, like sergio did here[1] for example? Even better, of course, would be to support needs-sudo. Is there a plan for this? Is it a matter of updating the "autopkgtest runners" to use this autopkgtest deb that we are SRUing here?

1. https://salsa.debian.org/sssd-team/sssd/-/merge_requests/30/diffs

[Skia (hyask)]

No, I've not considered anything like this, since I've started to test this new version on the staging infrastructure, and it already fixes the `unknown restriction` issue. See this log for a run with this setup:
https://autopkgtest.staging.ubuntu.com/results/autopkgtest-noble/noble/amd64/a/autopkgtest/20240208_171155_dd558@/log.gz

To add some precision to what is needed on the "autopkgtest runners", this is a branch based on this SRU, with some additional patches required for the infrastructure: https://salsa.debian.org/ubuntu-ci-team/autopkgtest/-/tree/ubuntu/5.32+prod?ref_type=heads
It's not deployed with a deb, but with a `git clone`, that allows a bit more flexibility for the infra. Still, we try to keep the diff as small as possible, but this hasn't been keeping up with upstream for a while, hence this big diff in SRU.
We expect to roll this branch out in production in the not so distant future, when we'll have tested it a bit more on staging, and when the queues will be shorted, and I'll go back to investigate and fix those tests at that moment. We've already some Jira cards opened for that, so we clearly have that in our radar.

[Brian Murray (brian-murray)]

The autopkgtests for autopkgtest are known to fail and have been failing for some time, fixing them is the team's long term plan, but their failure right now will not block the package from migrating from -proposed.

[Timo Aaltonen (tjaalton)]

Hello Skia, or anyone else affected,

Accepted autopkgtest into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/autopkgtest/5.32ubuntu3~23.10.1 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, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

Hello Skia, or anyone else affected,

Accepted autopkgtest into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/autopkgtest/5.32ubuntu3~22.04.1 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, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted autopkgtest (5.32ubuntu3~23.10.1) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

surf/2.1+git20221016-5 (arm64, armhf)

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/mantic/update_excuses.html#autopkgtest

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

Thank you!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted autopkgtest (5.32ubuntu3~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gscan2pdf/2.12.6-1 (armhf)
sbuild/0.81.2ubuntu6 (arm64, ppc64el, s390x)
systemd/249.11-0ubuntu3.12 (amd64, 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/jammy/update_excuses.html#autopkgtest

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

Thank you!

[Skia (hyask)]

Regarding autopkgtest regressions:

On Mantic:
* the surf tests are very flaky[1], and have been so for a while[2]. With some retriggers, arm64 could pass, but with the current load on the infra, I couldn't make armhf to pass. Still the error reported in the log file[3] is `Too few characters detected (0)`, and is thrown by the surf test itself. Nothing in this test makes calls to autopkgtest provided commands, so I don't expect this regression to be actually caused by this current SRU.

On Jammy:
* gscan2pdf and sbuild were transient failures that retries fixed easily.
* systemd, on the other hand, is directly related to this SRU:
  The systemd testsuite, for some reason, tries to patch the `autopkgtest-build-lxd` here[4], but the patch doesn't apply anymore. Given that this file is not present in more recent versions of systemd, I'm not sure if fixing this test is the right way to spend time.
  As for the `networkd-test.py` test, this one has been observed to be flaky in many other runs with different triggers [5]

[1]: https://autopkgtest.ubuntu.com/packages/s/surf/mantic/armhf
[2]: https://autopkgtest.ubuntu.com/packages/surf/jammy/armhf
[3]: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-mantic/mantic/armhf/s/surf/20240227_144458_eb091@/log.gz
[4]: https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/tests/tests-in-lxd?h=ubuntu/jammy-updates#n12
[5]: See https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20240227_140930_112c3@/log.gz and https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20240227_132149_18a85@/log.gz and https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20240227_051630_ed958@/log.gz for examples.

[Skia (hyask)]

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200 here is a bug with a debdiff fixing the systemd tests-in-lxd issue. It will be block-proposed until a more important systemd SRU is done.

[Skia (hyask)]

I've performed some manual verification on local podman containers and encountered no issue. Here are my tests in details, if someone wants to replicate them.

I run the containers with the following command:
```
podman run -it --rm -v /srv/images/:/srv/images -v /dev/kvm:/dev/kvm ubuntu:jammy
```
This allows me both to have hardware acceleration for amd64 VM, and access to my existing VM images in `/srv/images`.

Then in the container, I run this:
```
# Install right package
apt update
apt install -y lsb-release

cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF

cat <<EOF >/etc/apt/preferences.d/proposed-updates
# Configure apt to allow selective installs of packages from proposed
Package: *
Pin: release a=$(lsb_release -cs)-proposed
Pin-Priority: 400
EOF

# Test cross-arch
apt update
DEBIAN_FRONTEND=noninteractive apt install -y autopkgtest/$(lsb_release -cs)-proposed qemu-system-x86 qemu-system-aarch64 qemu-utils
autopkgtest gzip -- qemu --qemu-architecture=aarch64 --timeout-reboot 180 /srv/images/autopkgtest-jammy-arm64.img
autopkgtest mawk -a i386 -U -- qemu /srv/images/autopkgtest-jammy-amd64.img
autopkgtest mawk -a armhf -U -- qemu --qemu-architecture=aarch64 --timeout-reboot 180 /srv/images/autopkgtest-jammy-arm64.img

# Test VM image building
apt install -y genisoimage
autopkgtest-buildvm-ubuntu-cloud -a amd64 -r focal
# Check that it works
autopkgtest gzip -- qemu autopkgtest-focal-amd64.img

# Test null virt-server
cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-sources.list
# Enable Ubuntu source archive
deb-src http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs) restricted main multiverse universe
EOF
apt update
autopkgtest gzip -- null
```

Here are the versions tested:
Mantic:
```
# dpkg-query -W autopkgtest
autopkgtest 5.32ubuntu3~23.10.1
```
Jammy:
```
# dpkg-query -W autopkgtest
autopkgtest 5.32ubuntu3~22.04.1
```

[Andreas Hasenack (ahasenack)]

I'm trying to verify that the systemd dep8 fix is working, but looks like it hasn't run yet in noble. The fix landed in systemd 255.4-1ubuntu1 according to the changelog. Noble now has 255.4-1ubuntu4 (proposed), but I can't find any 255.4-* dep8 run in https://autopkgtest.ubuntu.com/packages/systemd/noble/amd64

[Andreas Hasenack (ahasenack)]

I see new runs of the patched systemd package in noble, and even though tests-in-lxd is still failing, now the reason is not the patch failing to apply, it's something else:

Starting autopkgtest-prepare-Rk7
4650s Created symlink /<email address hidden> → /dev/null.
4656s Container finished booting. Distribution Ubuntu, release noble, architecture amd64
4656s Running setup script /usr/share/autopkgtest/setup-commands/setup-testbed...
4657s sh: Attempting to set up Debian/Ubuntu apt sources automatically
4657s Failed to auto-detect apt mirror; set $MIRROR explicitly
4660s patching file /usr/bin/autopkgtest-build-lxd
4660s Creating autopkgtest-prepare-ilv
4667s
Retrieving image: Unpack: 100% (515.00MB/s)

Retrieving image: Unpack: 100% (515.00MB/s)

Starting autopkgtest-prepare-ilv
4673s Created symlink /<email address hidden> → /dev/null.
4673s Created symlink /etc/systemd/system/snapd.service → /dev/null.
4673s Masking 'snapd.service', but its triggering units are still active:
4673s snapd.socket
4674s Created symlink /etc/systemd/system/snapd.seeded.service → /dev/null.
4680s Container finished booting. Distribution Ubuntu, release noble, architecture amd64
4680s Running setup script /usr/share/autopkgtest/setup-commands/setup-testbed...
4680s sh: Attempting to set up Debian/Ubuntu apt sources automatically
4680s Failed to auto-detect apt mirror; set $MIRROR explicitly
4683s Creating systemd-lxc
4690s
Retrieving image: Unpack: 100% (1.11GB/s)

Retrieving image: Unpack: 100% (1.11GB/s)

Starting systemd-lxc
4750s running
4751s autopkgtest [05:06:03]: test tests-in-lxd: -----------------------]
4751s autopkgtest [05:06:03]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - -
4751s tests-in-lxd FAIL non-zero exit status 1

I agree that updating systemd in jammy just for the sake of this test is not correct. And systemd tests are so flaky, that it's possible a migration-reference/0 run will fail as well, and then mask any subsequent new failures. But I triggered one anyway.

[Andreas Hasenack (ahasenack)]

The remaining dep8 systemd/ppc64el failure on jammy cleared after the migration-reference/0 run also failed, expectedly.

[Launchpad Janitor (janitor)]

This bug was fixed in the package autopkgtest - 5.32ubuntu3~23.10.1

---------------
autopkgtest (5.32ubuntu3~23.10.1) mantic; urgency=medium

  * SRU to mantic (LP: #2051939)

autopkgtest (5.32ubuntu3) noble; urgency=medium

  * Remove .mypy_cache cruft from the previous upload
    Thanks: Alex Murray

autopkgtest (5.32ubuntu2) noble; urgency=medium

  * Fix traceback in cross-arch testing (LP #2051593)
  * Update cross-arch patchset from latest snapshot

autopkgtest (5.32ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP #2049737)
    Remaining changes:
    - Add support for cross-architecture testing.

autopkgtest (5.32) unstable; urgency=medium

  [ Florent 'Skia' Jacquet ]
  * d/t/schroot: better use of existing variables
  * d/t/schroot: allow running behind a proxy

  [ Simon McVittie ]
  * testarchive: Fix a pycodestyle warning
  * Standards-Version: 4.6.2 (no changes required)
  * qemu: Use 4M OVMF images if available

  [ Stefano Rivera ]
  * Testbed: Kill with SIGKILL if SIGTERM doesn't do the job in 10 seconds
    (Closes: #1059444)

  [ Paul Gevers ]
  * tests: increase sleep in test_timeout() for lxd test (Closes: #1020634)
  * autopkgtest-virt-qemu: raise time for command prompt return
  * virt-qemu: add context to several timeout errors

  [ Michael Biebl ]
  * Bump default ram-size for virt-qemu to 2048 (Closes: #1059840)

  [ Colin Watson ]
  * Add Incus support

  [ Santiago Ruano Rincón ]
  * Make autopkgtest-build-qemu pass mirror info to setup-testbed
    (Closes: #1060426)

  [ Paul Gevers ]
  * tests: increase --timeout-build to accommodate for riscv64
  * tests: mark podman-init autopkgtest flaky for now

autopkgtest (5.31.2) unstable; urgency=medium

  [ Florent 'Skia' Jacquet ]
  * d/control: add genisoimage as suggested package.
    It's used in `autopkgtest-buildvm-ubuntu-cloud`.

  [ Paul Gevers ]
  * autopkgtest-build-qemu: drop use of qemu-debootstrap.
    This is not needed in Debian 11 or newer. (Closes: #1038826)

  [ Simon McVittie ]
  * d/rules: Don't fail the build if a lint check fails (Closes: #1058550)
  * qemu, testdesc: Convert "# type:" comments into variable annotations.
    This avoids unused import warnings with current versions of pyflakes.

autopkgtest (5.31.1) unstable; urgency=medium

  * runner: fix architecture wildcard support broken in 30d5aa7
  * runner: fail badpkg in case no source was found like before 30d5aa7

autopkgtest (5.31) unstable; urgency=medium

  [ Johannes Schauer Marin Rodrigues ]
  * lib/autopkgtest_qemu.py: use -machine type=virt,gic-version=max when
    running natively on arm64 for kvm acceleration

  [ Tim Andersson ]
  * add ssh connect timeout to ssh-setup/nova
  * setup-testbed: Set apt error mode as any

  [ Paul Gevers ]
  * adt_testbed: factor out add-apt-sources
  * adt_testbed: factor out get-default-release
  * adt_testbed: factor out shell code to create sources.lists
  * Rewrite of source version selection in Python
  * create-sources.list-for-pocket: minor logical improvements
  * add-apt-sources: some checks of input arguments

  [ Jochen Sprickerhof ]
  * Update resolv.conf in unshare chroot

  [ Samuel Thibault ]
  * Fix hyphens in manp...

[Andreas Hasenack (ahasenack)]

The verification of the Stable Release Update for autopkgtest has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package autopkgtest - 5.32ubuntu3~22.04.1

---------------
autopkgtest (5.32ubuntu3~22.04.1) jammy; urgency=medium

  * SRU to jammy (LP: #2051939)

autopkgtest (5.32ubuntu3) noble; urgency=medium

  * Remove .mypy_cache cruft from the previous upload
    Thanks: Alex Murray

autopkgtest (5.32ubuntu2) noble; urgency=medium

  * Fix traceback in cross-arch testing (LP #2051593)
  * Update cross-arch patchset from latest snapshot

autopkgtest (5.32ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP #2049737)
    Remaining changes:
    - Add support for cross-architecture testing.

autopkgtest (5.32) unstable; urgency=medium

  [ Florent 'Skia' Jacquet ]
  * d/t/schroot: better use of existing variables
  * d/t/schroot: allow running behind a proxy

  [ Simon McVittie ]
  * testarchive: Fix a pycodestyle warning
  * Standards-Version: 4.6.2 (no changes required)
  * qemu: Use 4M OVMF images if available

  [ Stefano Rivera ]
  * Testbed: Kill with SIGKILL if SIGTERM doesn't do the job in 10 seconds
    (Closes: #1059444)

  [ Paul Gevers ]
  * tests: increase sleep in test_timeout() for lxd test (Closes: #1020634)
  * autopkgtest-virt-qemu: raise time for command prompt return
  * virt-qemu: add context to several timeout errors

  [ Michael Biebl ]
  * Bump default ram-size for virt-qemu to 2048 (Closes: #1059840)

  [ Colin Watson ]
  * Add Incus support

  [ Santiago Ruano Rincón ]
  * Make autopkgtest-build-qemu pass mirror info to setup-testbed
    (Closes: #1060426)

  [ Paul Gevers ]
  * tests: increase --timeout-build to accommodate for riscv64
  * tests: mark podman-init autopkgtest flaky for now

autopkgtest (5.31.2) unstable; urgency=medium

  [ Florent 'Skia' Jacquet ]
  * d/control: add genisoimage as suggested package.
    It's used in `autopkgtest-buildvm-ubuntu-cloud`.

  [ Paul Gevers ]
  * autopkgtest-build-qemu: drop use of qemu-debootstrap.
    This is not needed in Debian 11 or newer. (Closes: #1038826)

  [ Simon McVittie ]
  * d/rules: Don't fail the build if a lint check fails (Closes: #1058550)
  * qemu, testdesc: Convert "# type:" comments into variable annotations.
    This avoids unused import warnings with current versions of pyflakes.

autopkgtest (5.31.1) unstable; urgency=medium

  * runner: fix architecture wildcard support broken in 30d5aa7
  * runner: fail badpkg in case no source was found like before 30d5aa7

autopkgtest (5.31) unstable; urgency=medium

  [ Johannes Schauer Marin Rodrigues ]
  * lib/autopkgtest_qemu.py: use -machine type=virt,gic-version=max when
    running natively on arm64 for kvm acceleration

  [ Tim Andersson ]
  * add ssh connect timeout to ssh-setup/nova
  * setup-testbed: Set apt error mode as any

  [ Paul Gevers ]
  * adt_testbed: factor out add-apt-sources
  * adt_testbed: factor out get-default-release
  * adt_testbed: factor out shell code to create sources.lists
  * Rewrite of source version selection in Python
  * create-sources.list-for-pocket: minor logical improvements
  * add-apt-sources: some checks of input arguments

  [ Jochen Sprickerhof ]
  * Update resolv.conf in unshare chroot

  [ Samuel Thibault ]
  * Fix hyphens in manpag...