Public bug reported: 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". ** Affects: docker.io-app (Ubuntu) Importance: Undecided Status: Invalid ** Affects: docker.io-app (Ubuntu Jammy) Importance: Undecided Assignee: Athos Ribeiro (athos-ribeiro) Status: Triaged ** Tags: server-todo ** Also affects: docker.io-app (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: docker.io-app (Ubuntu) Status: New => Invalid ** Changed in: docker.io-app (Ubuntu Jammy) Status: New => Triaged ** Changed in: docker.io-app (Ubuntu Jammy) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) ** Tags added: server-todo -- 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
