Bug#1080200: closing 1080200

[Salvatore Bonaccorso <carnil@debian.org>]

Hi Mike,

On Sat, Aug 31, 2024 at 02:16:06PM +0100, Mike Ricketts wrote:
> On 31/08/2024 13:44, Salvatore Bonaccorso wrote:
> > close 1080200
> > thanks
> > 
> > bullseye-backports is discontinued, situation would resolve once the signed
> > packages are around. For bullseye-backports the latest available was:
> > 
> > linux-signed-amd64 | 6.1.90+1~bpo11+1   | bullseye-backports | source
> 
> Whilst bullseye-backports is discontinued, this problem means it is
> impossible to get the system into a clean state in order to upgrade to
> bullseye (which is what I was trying to do when I discovered this).
> 
> linux-signed-amd64 version 6.1.90-1~bpo11+1 seems to be old half available
> in bullseye-backports - the linux-image package is there, but the
> linux-headers is not.
> 
> Will the linux-headers-amd64 package in bullseye-backports ever be fixed, or
> do we have to upgrade to bullseye from a system with broken packages and
> just hope it all goes ok?

The package would not be fixed anymore, see

https://lists.debian.org/debian-backports/2024/08/msg00008.html

this was the missing bit needed to get the signed packages in.

That said you have several options:

- Update the system to bookworm (preferred)
- if you have to stick with bullseye, which is now maintained by the
  Debian LTS team, a linux-6.1 source package will be provided which
  continues to provide 6.1.y series for bullseye (via
  bullseye-security, but not anymore through bullseye-backports).

Ben might give some details when such packages are to be expected.

Does this help?

Regards,
Salvatore