On Wed, May 05, 2021 at 12:53:53AM +0200, Michael Rasmussen wrote: >On Tue, 4 May 2021 23:47:30 +0100 >Steve McIntyre <st...@einval.com> wrote: > >> >> Wow, OK. That *is* surprising! Oh well, thanks for the information >> anyway. It seems that *something* has caused your system to install >> shim-signed, but I've no clue what! :-) >> > >I have been trying to recapture my memory and I think it was installed >at the time where EFI boot first was introduced into Unstable - can't >remember exactly when ;-)
Ah, OK. :-) That would have been during the Jessie release cycle, so quite a few years back. Don't worry about it too much... >> Anyway, the bug should be fixed now with tonight's upload. >> >Yes, but you need to reinstall the new package to be able to remove it: >Preparing to unpack .../shim-signed_1.35+15.4-4_amd64.deb ... >Unpacking shim-signed:amd64 (1.35+15.4-4) over (1.34+15.4-2) ... >cat: /sys/firmware/efi/fw_platform_size: No such file or directory >dpkg: warning: old shim-signed:amd64 package post-removal script >subprocess returned error exit status 1 >dpkg: trying script from the new package instead ... >dpkg: ... it looks like that went OK Cool, that's what I expected to see. -- Steve McIntyre, Cambridge, UK. st...@einval.com "The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." -- Bertrand Russell
