No, not that I am aware of. But here is the ouput of markus@bmtMB1:~$ sudo dpkg -l | grep grub ii grub-common 2.02+dfsg1-20+deb10u4 amd64 GRand Unified Bootloader (common files) rc grub-efi-amd64 2.02+dfsg1-20+deb10u3 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin 2.02+dfsg1-20+deb10u4 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 modules) ii grub-efi-amd64-signed 1+2.02+dfsg1+20+deb10u4 amd64 GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) ii grub-firmware-qemu 2.02+dfsg1-20+deb10u4 amd64 GRUB firmware image for QEMU ii grub2-common 2.02+dfsg1-20+deb10u4 amd64 GRand Unified Bootloader (common files for version 2) markus@bmtMB1:~$
Cheers Markus Am 23.06.21 um 16:43 schrieb David Wright:
Please post as text, not *just* html. On Wed 23 Jun 2021 at 15:55:04 (+0200), Markus wrote:<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body> Hi, just before and also after today's "apt full-upgrade" apt tells me that:<br> <br> <pre><code>The following packages were automatically installed and are no longer required</code>: efibootmgr grub-efi-amd64-bin grub-efi-amd64-signed grub2-common libappindicator3-1 libcanberra-gtk3-0 libcanberra-gtk3-module libclutter-gtk-1.0-0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libindicator3-7 libupsclient4 linux-headers-5.10.0-0.bpo.4-amd64 linux-headers-5.10.0-0.bpo.4-common linux-image-5.10.0-0.bpo.4-amd64 linux-kbuild-4.19 linux-kbuild-5.9 mokutil shim-helpers-amd64-signed shim-signed-common shim-unsigned </pre> I don't have a good feeling when I see that it allows me to remove <br> "efibootmgr grub-efi-amd64-bin grub-efi-amd64-signed grub2-common" <br> <br> <br> What is wrong here? I am on Buster and used kernel 5.10.0-0.bpo.5-amd64. With today's <br> full-upgrade 5.10.0-0.bpo.7-amd64 came in.Has grub-efi-amd64 been accidentally removed? AIUI that's the package which depends on having the packages to boot your machine. Cheers, David.
