On Mon, Dec 05, 2022 at 06:19:53PM +0100, Eric Valette wrote: >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.
There are no dependency issues to worry about here, I'm afraid you simply misunderstood the grub packaging setup. That's reasonable - it's not obvious! Just don't expect the bug to be fixed until the changes have propagated... >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. ACK, I understand your pain there. :-/ -- Steve McIntyre, Cambridge, UK. st...@einval.com "Yes, of course duct tape works in a near-vacuum. Duct tape works anywhere. Duct tape is magic and should be worshipped." -― Andy Weir, "The Martian"
