DEP8 tests are failing for jammy

[Athos Ribeiro]

[ Impact ]

he basic-smoke DEP8 test in docker.io-app generates a chroot with debootstrap targeting Debian "stable".
The debian-archive-keyring package in jammy does not have the keys for the current "stable" suite, resulting in the following error:

107s I: Retrieving InRelease
107s I: Checking Release signature
107s E: Release signed by unknown key (key id 762F67A0B2C39DE4)
107s The specified keyring /usr/share/keyrings/debian-archive-keyring.gpg may be incorrect or out of date.
107s You can find the latest Debian release key at https://ftp-master.debian.org/keys.html

[ Test Plan ]

Run autopkgtest for docker.io-app. The tests will fail with the error described in the "Impact" section if the package is affected. When fixed, the tests should pass.

* This test plan does not apply to riscv64. See the "Other Info" section for further details.

[ Where problems could occur ]

If we decide to start running autopkgtest for riscv64 in jammy, those tests will fail. This will not introduce a regression since the first tests will be failing already. See the "Other Info" section for further details.

Moreover, there is a possibility that, in a future docker.io release during jammy's support period, bullseye becomes "too old" for the newest upstream docker.io, and then we may start having issues wither importing the image into docker or running it. If that happens, we may need to re-visit the idea of updating the debian-archive-keyring package or find another workaround for the issue.

[ Other Info ]

Note that this is not fixing the tests for riscv64 since there are no builds for that architecture for bullseye in archive.debian.org. This will not introduce a regression since we have no benchmarks for riscv64 tests in jammy ATM.

[ Original message ]

The basic-smoke DEP8 test in docker.io-app generates a chroot with debootstrap targeting Debian "stable".
The debian-archive-keyring package in jammy does not have the keys for the current "stable" suite, resulting in the following error:

107s I: Retrieving InRelease
107s I: Checking Release signature
107s E: Release signed by unknown key (key id 762F67A0B2C39DE4)
107s The specified keyring /usr/share/keyrings/debian-archive-keyring.gpg may be incorrect or out of date.
107s You can find the latest Debian release key at https://ftp-master.debian.org/keys.html

While we may discuss (and possibly consider) updating the keyring packages in our supported releases, a quick workaround for the failing test in jammy would be to change the targeted suite to the codename of the Debian "stable" suite known by that package version back when it was released, i.e., "bullseye".

[Athos Ribeiro (athos)]

This is being fixed through https://github.com/canonical/docker.io-app/pull/19

[Andreas Hasenack (ahasenack)]

Hello Athos, or anyone else affected,

Accepted docker.io-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io-app/28.2.2-0ubuntu1~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.

[Athos Ribeiro (athos)]

autopackage tests are now passing, as observed in the autopkgtest infrastructure. https://autopkgtest.ubuntu.com/packages/d/docker.io-app

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io-app - 28.2.2-0ubuntu1~22.04.1

---------------
docker.io-app (28.2.2-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport from questing to jammy (LP: #2112523)
  * d/control: b-d on golang-1.23-go instead of golang-1.24-go
  * d/rules: add Go 1.23 to $PATH
  * d/t/basic-smoke:
    - Target bullseye for debootstrap image generation (LP: #2124109)
    - Change the MIRROR URL to use archive.d.o since oldoldstable is not
      available for ppc64el and s390x through ftp.d.o

docker.io-app (28.2.2-0ubuntu1) questing; urgency=medium

  * New upstream version 28.2.2
  * d/h/build-manpages.sh: adjust manpage build script to upstream changes
  * d/manpages/*: update manpages for version 28.2.2
  * d/docker.io.docs: update NOTICE files
  * d/copyright: update copyright data

docker.io-app (27.5.1-0ubuntu4) questing; urgency=medium

  * d/control: conflicts/replaces podman-docker (LP: #2037905)

 -- Athos Ribeiro <email address hidden> Wed, 10 Sep 2025 11:50:16 -0300

[Julian Andres Klode (juliank)]

The verification of the Stable Release Update for docker.io-app 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.