Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version

Eric Valette eric.valette at free.fr
Mon Dec 5 17:19:53 GMT 2022


On 05/12/2022 18:07, Steve McIntyre wrote:

> You're using the Secure Boot path (shim -> grub-efi-amd64-signed), so
> the version of grub that matters for you is the signed version:
> 1+2.06+5. That is (so far) still based on grub2 source version 2.06-5.
> It takes a short while for the builds to propagate through the signing
> machinery in Debian.
> 
> Please be patient, the fix is on the way to you. If you can check
> again when 1+2.06+6 is available, that will be more helpful.

Fair enough but for me this should be handled as a dependency so that 
you cannot upgrade only part of grub components. A meta package that 
makes sure all the dependencies are ok before starting the upgrade.

And as explained I must play with windows bitlocker to suspend it before 
being able to install so I would prefer doing it all at once.


-- eric



More information about the Pkg-grub-devel mailing list