Bug#1021012: marked as done (linux-image-amd64 depends on linux-image-4.19.0-22-amd64, but this package is not available)

2022-10-01 Thread Bastian Blank
On Sat, Oct 01, 2022 at 09:29:10PM +0200, Ben Hutchings wrote: > In buster, the metapackages are still built from linux-latest. This > has a fake build-dependency on linux-headers--all to ensure it > waits for linux to be built, but it doesn't have any such relation to > linux-signed-*. Ah,

Bug#1021012: marked as done (linux-image-amd64 depends on linux-image-4.19.0-22-amd64, but this package is not available)

2022-10-01 Thread Ben Hutchings
On Sat, 2022-10-01 at 12:23 +0200, Bastian Blank wrote: > On Sat, Oct 01, 2022 at 06:45:03AM +, 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

Bug#1021012: marked as done (linux-image-amd64 depends on linux-image-4.19.0-22-amd64, but this package is not available)

2022-10-01 Thread Bastian Blank
On Sat, Oct 01, 2022 at 06:45:03AM +, 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