Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
On 05/12/2022 18:33, Steve McIntyre wrote: 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... I beg to disagree on this one. On my laptop, I updated grub-efi-amd64-signed to the 1+2.06+6 version but, as installation does not trigger grub reinstall, my laptop is still broken. If you do not want to put dependency on component, each component that contains things that should be moved to EFI directory should trigger a grub update. And at first you should not update the EFI directory until all needed binaries are updated. ( ls /var/lib/dpkg/info/grub-efi-amd64-signed.* /var/lib/dpkg/info/grub-efi-amd64-signed.list /var/lib/dpkg/info/grub-efi-amd64-signed.md5sums ) The good point, is that, on my Desktop that was broken due to previous install, and on which I downgraded and pinned, because I installed a coherent set all at once, it worked. But dependencies should enforce you always have a coherent set when ruing grub update. So I have to boot windows, suspend bit locker, trigger the reinstall of grub, verify it works by rebooting and then again reenable bitlocker. Groumph. -- eric
Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
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"
Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
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
Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
On Mon, Dec 05, 2022 at 05:55:13PM +0100, Eric Valette wrote: >I had the previous version 2.06-5 on a laptop, and it was not affected by the >bug, Only my very old Desktop was. > >As the bug was closed, I did install 2.06-6 on my laptop (or at least the >composant actually upgraded) and now it also fails on my laptop with same >error than on my desktop. > >I now have apparently several grub version flavors and several shim version >flavor: > >15.4 for shim-signed:amd64 and shim-signed-common and 15.6 for >shim-helpers-amd64-signed and shim-unsigned > >And for grub, I have 2.06-6 except for the important part : >grub-efi-amd64-signed that is still at 2.06-5. The shim versions don't matter here, the issues are all in grub. >root@:~# dpkg -l grub* >Desired=Unknown/Install/Remove/Purge/Hold >| >Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend >|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) >||/ Name Version Architecture Description >+++-=---= ... >hi grub-efi-amd64-signed 1+2.06+5 amd64GRand Unified Bootloader, >version 2 (amd64 UEFI signed by Debian) 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. -- Steve McIntyre, Cambridge, UK.st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
I had the previous version 2.06-5 on a laptop, and it was not affected by the bug, Only my very old Desktop was. As the bug was closed, I did install 2.06-6 on my laptop (or at least the composant actually upgraded) and now it also fails on my laptop with same error than on my desktop. I now have apparently several grub version flavors and several shim version flavor: 15.4 for shim-signed:amd64 and shim-signed-common and 15.6 for shim-helpers-amd64-signed and shim-unsigned And for grub, I have 2.06-6 except for the important part : grub-efi-amd64-signed that is still at 2.06-5. dpkg -l shim* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=--- un shim(no description available) hi shim-helpers-amd64-signed 1+15.6+1 amd64boot loader to chain-load signed boot loaders (signed by Debian) hi shim-signed:amd64 1.38+15.4-7 amd64Secure Boot chain-loading bootloader (Microsoft-signed binary) hi shim-signed-common1.38+15.4-7 all Secure Boot chain-loading bootloader (common helper scripts) hi shim-unsigned 15.6-1 amd64boot loader to chain-load signed boot loaders under Secure Boot root@:~# dpkg -l grub* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=---= un grub(no description available) un grub-cloud-amd64(no description available) hi grub-common 2.06-6 amd64GRand Unified Bootloader (common files) un grub-coreboot (no description available) un grub-doc(no description available) hi grub-efi 2.06-6 amd64GRand Unified Bootloader, version 2 (dummy package) hi grub-efi-amd642.06-6 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version) hi grub-efi-amd64-bin2.06-6 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 modules) hi grub-efi-amd64-signed 1+2.06+5 amd64GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) un grub-efi-arm(no description available) un grub-efi-arm64 (no description available) un grub-efi-ia32 (no description available) un grub-efi-ia64 (no description available) un grub-emu(no description available) un grub-ieee1275 (no description available) un grub-legacy (no description available) un grub-legacy-doc (no description available) un grub-linuxbios (no description available) un grub-pc (no description available) hi grub-pc-bin 2.06-6 amd64GRand Unified Bootloader, version 2 (PC/BIOS modules) un grub-uboot (no description available) un grub-xen(no description available) un grub-yeeloong (no description available) un grub2 (no description available) hi grub2-common 2.06-6 amd64GRand Unified Bootloader (common files for version 2) root@:~# -- eric
