On Sun, Apr 05, 2026 at 09:47:45PM +0100, Steve McIntyre wrote:
> Again, following up on both bugs for a different reason.
>
> I've ended up uploading versions of shim for bookworm and trixie with
> slightly different versions to match up with the latest version I've
> uploaded in unstable.
>
> I'm not seeing any sign of builds happening in either case, so I guess
> I need to ask for an update to allow that? Pretty please! :-)
>
> I now have:
>
> shim/16.1-2~deb13u1 in trixie (#1131861)
> shim/16.1-2~deb12u1 in bookworm (#1131862)
Builds won't start until the sources are accepted, after which they will be
automatically added to {,oldstable-}proposed-updates and roll out to users
of those suites.
If I understand right, that will break secure boot for grub for those users
because of the change of sbat level? Therefore should we get grub2
accepted and built first? Where will updating shim leave users while we
await shim-signed?
--
Jonathan Wiltshire [email protected]
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
