On Sat, 2022-10-01 at 12:23 +0200, Bastian Blank wrote: > On Sat, Oct 01, 2022 at 06:45:03AM +0000, Debian Bug Tracking System wrote: > > This will resolve itself automatically once the signed packages are > > available as well (they are in progress of beeing dealt with but needs > > a manual interaction of ftp-masters). > > Looks like we need to backport the changes that moved the meta package > into linux-signed-*. This now also affects the build of the cloud > images and breaks them.
In buster, the metapackages are still built from linux-latest. This has a fake build-dependency on linux-headers-<version>-all to ensure it waits for linux to be built, but it doesn't have any such relation to linux-signed-*. I don't think I should try to move binary packages around post-release, so probably the best approach is to wait to upload linux-latest in future. (This wasn't a problem with stretch LTS because we didn't do code signing, and it wasn't a problem with buster prior to LTS because security updates and point releases would release all related packages at once.) Ben -- Ben Hutchings Editing code like this is akin to sticking plasters on the bleeding stump of a severed limb. - me, 29 June 1999
signature.asc
Description: This is a digitally signed message part
