Re: [DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system
Hi, fsmithred via Dng writes: > On 8/6/21 5:57 PM, Adrian Zaugg wrote: >> In der Nachricht vom Friday, 6 August 2021 03:25:58 CEST steht: >>> Which Beowulf iso did you use? I think we fixed this in the 3.1.1 >>> point-release isos, but you still may hit it on an upgrade. >> >> It happened on upgraded systems. >> >> Thanx for fixing the ISO. >> >> Don't you see a way to prevent the issue happening on upgraded systems, e.g. >> blacklisting grub-efi-amd64-signed or using another mechanism? >> >> Regards, Adrian. >> >> BTW: I uninstalled grub-efi-amd64-signed without concern because of Debian >> bug >> #906124 [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906124] > > If grub-efi-amd64-signed is getting installed on upgrade from ascii to > beowulf, one way I can think of preventing it is to pin that package > before doing the upgrade. For example: > > in /etc/apt/preferences.d/no-signed > > Package: grub-efi-amd64-signed > Pin: release n=beowulf > Pin-Priority: -1 > > Aha! I see that grub-efi-amd64-bin Recommends grub-efi-amd64-signed, so > another way to block it is to block Recommends. > > in /etc/apt/apt.conf.d/00norecommends > > APT::Install-Recommends "no"; > > or else add '--no-install-recommends' to a command-line install. While I personally have that set in my apt.conf.d somewhere, it may be a bit drastic for the average user. > I can't think of any clean ways for us to do this for the end user. Maybe > someone else has a better idea. I don't know if it's better but perhaps doing the upgrade of grub as a separate first step, like so apt-get install grub-efi-amd64-bin grub-efi-amd64-signed- Note the trailing `-` which instructs apt-get to remove the package. You may need to add an explicit version to grub-efi-amd64-bin for it to actually upgrade. Something like apt-get install grub-efi-amd64-bin=2.02+dfsg1-20+deb10u4 \ grub-efi-amd64-signed- This is completely untested, so if apt-get starts barfing all kinds of conflicts then I recommend *not* going ahead with this. If all apt-get wants to do is upgrade and/or add a few packages to make it work, that should be okay. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system
On 8/6/21 5:57 PM, Adrian Zaugg wrote: > In der Nachricht vom Friday, 6 August 2021 03:25:58 CEST steht: >> Which Beowulf iso did you use? I think we fixed this in the 3.1.1 >> point-release isos, but you still may hit it on an upgrade. > > It happened on upgraded systems. > > Thanx for fixing the ISO. > > Don't you see a way to prevent the issue happening on upgraded systems, e.g. > blacklisting grub-efi-amd64-signed or using another mechanism? > > Regards, Adrian. > > BTW: I uninstalled grub-efi-amd64-signed without concern because of Debian > bug > #906124 [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906124] > > If grub-efi-amd64-signed is getting installed on upgrade from ascii to beowulf, one way I can think of preventing it is to pin that package before doing the upgrade. For example: in /etc/apt/preferences.d/no-signed Package: grub-efi-amd64-signed Pin: release n=beowulf Pin-Priority: -1 Aha! I see that grub-efi-amd64-bin Recommends grub-efi-amd64-signed, so another way to block it is to block Recommends. in /etc/apt/apt.conf.d/00norecommends APT::Install-Recommends "no"; or else add '--no-install-recommends' to a command-line install. I can't think of any clean ways for us to do this for the end user. Maybe someone else has a better idea. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system
In der Nachricht vom Friday, 6 August 2021 03:25:58 CEST steht: > Which Beowulf iso did you use? I think we fixed this in the 3.1.1 > point-release isos, but you still may hit it on an upgrade. It happened on upgraded systems. Thanx for fixing the ISO. Don't you see a way to prevent the issue happening on upgraded systems, e.g. blacklisting grub-efi-amd64-signed or using another mechanism? Regards, Adrian. BTW: I uninstalled grub-efi-amd64-signed without concern because of Debian bug #906124 [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906124] signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system
On 8/4/21 7:17 AM, Adrian Zaugg wrote: > Dear list > > Beowulf is hit hard by a problem with hardcoded path in grub-efi-amd64-signed > leading to an unbootable system as reported on this list and on dev1galaxy > (manual intervention in certain configurations needed to boot). This problem > also exists on fresh installs of beowulf, as it seems. Is there some effort > under way to fix the problem? > > Best regards, Adrian. > > > Work-around (thanks to fsmithred): > > # apt purge grub-efi-amd64-signed > ... > # apt install --reinstall grub-efi-amd64 > ... > Which Beowulf iso did you use? I think we fixed this in the 3.1.1 point-release isos, but you still may hit it on an upgrade. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system
Dear list Beowulf is hit hard by a problem with hardcoded path in grub-efi-amd64-signed leading to an unbootable system as reported on this list and on dev1galaxy (manual intervention in certain configurations needed to boot). This problem also exists on fresh installs of beowulf, as it seems. Is there some effort under way to fix the problem? Best regards, Adrian. Work-around (thanks to fsmithred): # apt purge grub-efi-amd64-signed ... # apt install --reinstall grub-efi-amd64 ... References: On this list: "Strange behaviour with last version of grub" by viverna (04/03/2021 17:22) --> https://lists.dyne.org/lurker/message/20210304.162242.f881d3b8.en.html In the Dev1 Galaxy Forum: "Strange behaviour with last version of grub" by viverna (2021-03-04) --> https://dev1galaxy.org/viewtopic.php?pid=27939 "Issues with booting a fresh Beowulf install" by chomwitt (2021-07-10) -->https://dev1galaxy.org/viewtopic.php?pid=30972#p30972 ...and the mentioned underlaying Debian Bug report: "Wrong prefix directory hardcoded in signed GRUB image" by Pascal Hambourg (2021-03-22) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925309 signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
