On Mon, Apr 06, 2026 at 04:00:23PM +0100, Jonathan Wiltshire wrote:
>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?
The change of SBAT will not take effect until we have those signed
shims for people to install, in fact. So we'll need to make sure that
the new shim-signed and signed grub packages hit bookworm together,
that's all. Trixie already contains updated grub packages so it will
be ok.
But before we get there, I need to get build logs and binaries for
these unsigned shims - we need that for the review process. So if you
could accept these sources that would be appreciated. :-)
--
Steve McIntyre, Cambridge, UK. [email protected]
Is there anybody out there?
