Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #236373 > unrolled thread

Re: apt tells me that grub-efi, grub2-common are no longer needed

Started byDavid Wright <deblis@lionunicorn.co.uk>
First post2021-06-23 16:50 +0200
Last post2021-06-24 17:00 +0200
Articles 3 on this page of 23 — 7 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: apt tells me that grub-efi, grub2-common are no longer needed David Wright <deblis@lionunicorn.co.uk> - 2021-06-23 16:50 +0200
    Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-06-23 17:10 +0200
      Re: apt tells me that grub-efi, grub2-common are no longer needed David Wright <deblis@lionunicorn.co.uk> - 2021-06-23 18:10 +0200
        Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-06-24 08:50 +0200
          Re: apt tells me that grub-efi, grub2-common are no longer needed Greg Wooledge <greg@wooledge.org> - 2021-06-24 13:20 +0200
            Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-06-24 17:10 +0200
              Re: apt tells me that grub-efi, grub2-common are no longer needed Greg Wooledge <greg@wooledge.org> - 2021-06-24 17:20 +0200
                Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-06-24 18:50 +0200
                  Re: apt tells me that grub-efi, grub2-common are no longer needed Greg Wooledge <greg@wooledge.org> - 2021-06-24 19:00 +0200
                    Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-07-07 08:30 +0200
                      Re: apt tells me that grub-efi, grub2-common are no longer needed Andrei POPESCU <andreimpopescu@gmail.com> - 2021-07-07 09:30 +0200
                        Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-07-07 12:30 +0200
                          Re: apt tells me that grub-efi, grub2-common are no longer needed Anssi Saari <as@sci.fi> - 2021-07-07 14:30 +0200
                            Re: apt tells me that grub-efi, grub2-common are no longer needed The Wanderer <wanderer@fastmail.fm> - 2021-07-07 14:40 +0200
                              Re: apt tells me that grub-efi, grub2-common are no longer needed Anssi Saari <as@sci.fi> - 2021-07-07 21:30 +0200
                          Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-07-08 10:30 +0200
                            Re: apt tells me that grub-efi, grub2-common are no longer needed Anssi Saari <as@sci.fi> - 2021-07-08 12:00 +0200
                            Re: apt tells me that grub-efi, grub2-common are no longer needed The Wanderer <wanderer@fastmail.fm> - 2021-07-08 12:20 +0200
                      Re: apt tells me that grub-efi, grub2-common are no longer needed Greg Wooledge <greg@wooledge.org> - 2021-07-07 13:30 +0200
              Re: apt tells me that grub-efi, grub2-common are no longer needed David Wright <deblis@lionunicorn.co.uk> - 2021-07-08 16:50 +0200
          Re: apt tells me that grub-efi, grub2-common are no longer needed David Wright <deblis@lionunicorn.co.uk> - 2021-06-24 16:10 +0200
            Re: apt tells me that grub-efi, grub2-common are no longer needed Nicolas George <george@nsup.org> - 2021-06-24 16:10 +0200
            Re: apt tells me that grub-efi, grub2-common are no longer needed Markus <debianer@gmx.de> - 2021-06-24 17:00 +0200

Page 2 of 2 — ← Prev page 1 [2]

#236414

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2021-06-24 16:10 +0200
Message-ID<Ctydj-42p-5@gated-at.bofh.it>
In reply to#236396
On Thu 24 Jun 2021 at 08:49:40 (+0200), Markus wrote:
> Am 23.06.21 um 18:08 schrieb David Wright:
> > On Wed 23 Jun 2021 at 17:01:07 (+0200), Markus wrote:

> > > rc  grub-efi-amd64 2.02+dfsg1-20+deb10u3
> >    ↑↑ There's your problem. It's been removed (but not purged).

> Ok so...hmmm...I did not remove it myself. I mean why would I want to do
> that?!?! Nevertheless this is an issue now.

Take a look at /var/log/apt/history.log* to see the reason
and/or the occasion (but not necessarily the intent).¹

As an example of how things can happen unintentionally, this
post from Tuesday illustrates where a broken package's bug
report seems to have led to a different package being removed:
https://lists.debian.org/debian-user/2021/06/msg00581.html

> Interestingly when booting my computer this morning grub was there and
> booted into Buster. Shouldn't it be gone if it got removed (even though
> it not got purged)? Hmmm...!?!?

Only if you'd gone ahead and removed all those other packages.
There's actually nothing substantial inside grub-efi-amd64:

$ dpkg -L grub-efi-amd64
/.
/usr
/usr/share
/usr/share/bug
/usr/share/bug/grub-efi-amd64
/usr/share/bug/grub-efi-amd64/presubj
/usr/share/bug/grub-efi-amd64/script
/usr/share/doc
/usr/share/doc/grub-efi-amd64
$ 

> How to fix that? Is there actually something wrong (this morning grub
> was there!!!) that needs to be fixed?
> Is it sa[f]e to just reinstall grub-efi-amd64?

Yes. The package exists for its dependencies. Just reinstall it.
You can then try autoremove again, and its list should now only
include the (presumably third) versions of the kernel packages
that you wanted to remove as a matter of routine, like mine in ¹.

¹ entries in /var/log/apt/history.log look like:

Start-Date: 2021-06-19  17:45:10
Commandline: apt-get --purge autoremove
Purge: linux-headers-4.19.0-14-amd64:amd64 (4.19.171-2), linux-headers-4.19.0-14-common:amd64 (4.19.171-2), linux-image-4.19.0-14-amd64:amd64 (4.19.171-2)
End-Date: 2021-06-19  17:45:33

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#236415

FromNicolas George <george@nsup.org>
Date2021-06-24 16:10 +0200
Message-ID<Ctydk-42p-11@gated-at.bofh.it>
In reply to#236414
David Wright (12021-06-24):
> Only if you'd gone ahead and removed all those other packages.

Not even then. The GRUB packages are useful for installing the GRUB
bootloader. Once it's installed, the computer will boot, and the package
are not necessary, although they might be useful to automatically update
the configuration after upgrades.

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

#236420

FromMarkus <debianer@gmx.de>
Date2021-06-24 17:00 +0200
Message-ID<CtyZI-4iq-3@gated-at.bofh.it>
In reply to#236414
Thank you, David, for the very useful hint.

I found this in apt history:

Start-Date: 2021-03-06  21:08:42
Commandline: apt full-upgrade
Requested-By: markus (1000)
Upgrade: grub-common:amd64 (2.02+dfsg1-20+deb10u3,
2.02+dfsg1-20+deb10u4), grub2-common:amd64 (2.02+dfsg1-20+deb10u3,
2.02+dfsg1-20+deb10u4), grub-efi-amd64-bin:amd64 (2.02+dfsg1-20+deb10u3,
2.02+dfsg1-20+deb10u4), grub-efi-amd64-signed:amd64
(1+2.02+dfsg1+20+deb10u3, 1+2.02+dfsg1+20+deb10u4)
Remove: grub-efi-amd64:amd64 (2.02+dfsg1-20+deb10u3)
End-Date: 2021-03-06  21:08:45


Do you guys maybe find similar entries in apt history?

So why did apt remove it while upgrading other grub corresponding
packages? And then afterwards apt is complaining and wants to remove
grub, efibootmgr and other stuff.

The following packages were automatically installed and are no longer
required:
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

Is it somehow linked to that shim-* packages that got also updated.
Wasn't there a bug report recently about this package when updating to
Buster 10.10?

Maybe it was like this:
1. On 2021-03-06 grub-efi-amd64 got removed because the other updated
grub packages somehow took over its tasks

2. shim got updated just recently and took over the tasks of
efibootmgr
grub-efi-amd64-bin
grub-efi-amd64-signed
grub2-common

3. only grub-common gets not removed because it is still required and in
conjunction with shim it is enough and all fine.

Because if you subtract the "no longer required" grub packages from

markus@bmtMB1:/var/log/apt$ sudo dpkg -l | grep grub
ii  grub-common   					2.02+dfsg1-20+deb10u4
rc  grub-efi-amd64                                	2.02+dfsg1-20+deb10u3
ii  grub-efi-amd64-bin                           	2.02+dfsg1-20+deb10u4
ii  grub-efi-amd64-signed                       1+2.02+dfsg1+20+deb10u4
ii  grub-firmware-qemu                          2.02+dfsg1-20+deb10u4
ii  grub2-common                                  	2.02+dfsg1-20+deb10u4

you end up with grub-common and grub-firmware-qemu.

 From here you can read that shim is also some kind of bootloader:
https://packages.debian.org/en/buster/shim-signed

But obviously shim depends on grub2-common and grub-efi-amd64-bin.
Hmmm...this makes no sense...

Cheers



Am 24.06.21 um 16:00 schrieb David Wright:
> On Thu 24 Jun 2021 at 08:49:40 (+0200), Markus wrote:
>> Am 23.06.21 um 18:08 schrieb David Wright:
>>> On Wed 23 Jun 2021 at 17:01:07 (+0200), Markus wrote:
>
>>>> rc  grub-efi-amd64 2.02+dfsg1-20+deb10u3
>>>     ↑↑ There's your problem. It's been removed (but not purged).
>
>> Ok so...hmmm...I did not remove it myself. I mean why would I want to do
>> that?!?! Nevertheless this is an issue now.
>
> Take a look at /var/log/apt/history.log* to see the reason
> and/or the occasion (but not necessarily the intent).¹
>
> As an example of how things can happen unintentionally, this
> post from Tuesday illustrates where a broken package's bug
> report seems to have led to a different package being removed:
> https://lists.debian.org/debian-user/2021/06/msg00581.html
>
>> Interestingly when booting my computer this morning grub was there and
>> booted into Buster. Shouldn't it be gone if it got removed (even though
>> it not got purged)? Hmmm...!?!?
>
> Only if you'd gone ahead and removed all those other packages.
> There's actually nothing substantial inside grub-efi-amd64:
>
> $ dpkg -L grub-efi-amd64
> /.
> /usr
> /usr/share
> /usr/share/bug
> /usr/share/bug/grub-efi-amd64
> /usr/share/bug/grub-efi-amd64/presubj
> /usr/share/bug/grub-efi-amd64/script
> /usr/share/doc
> /usr/share/doc/grub-efi-amd64
> $
>
>> How to fix that? Is there actually something wrong (this morning grub
>> was there!!!) that needs to be fixed?
>> Is it sa[f]e to just reinstall grub-efi-amd64?
>
> Yes. The package exists for its dependencies. Just reinstall it.
> You can then try autoremove again, and its list should now only
> include the (presumably third) versions of the kernel packages
> that you wanted to remove as a matter of routine, like mine in ¹.
>
> ¹ entries in /var/log/apt/history.log look like:
>
> Start-Date: 2021-06-19  17:45:10
> Commandline: apt-get --purge autoremove
> Purge: linux-headers-4.19.0-14-amd64:amd64 (4.19.171-2), linux-headers-4.19.0-14-common:amd64 (4.19.171-2), linux-image-4.19.0-14-amd64:amd64 (4.19.171-2)
> End-Date: 2021-06-19  17:45:33
>
> Cheers,
> David.
>

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web