** Description changed: + [ 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: 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".
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2124109 Title: DEP8 tests are failing for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2124109/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
