emerge -c wants to remove sys-boot/grub after upgrading to ego 2.6.0

Question

Now after running "ego sync" and "emerge -auND @world" when I run "emerge -cp" I get the following output:

>sudo emerge -cp
Password:
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence of this, it often becomes necessary to run
* `emerge --update --newuse --deep @world` prior to depclean.
Calculating dependencies... done!
>>> Calculating removal order...
>>> These are the packages that would be unmerged:
sys-boot/grub
selected: 2.02-r1
protected: none
omitted: none
sys-boot/efibootmgr
selected: 15
protected: none
omitted: none
media-libs/freetype
selected: 2.8
protected: none
omitted: none
sys-libs/efivar
selected: 35
protected: none
omitted: none
All selected packages: =sys-boot/efibootmgr-15 =sys-boot/grub-2.02-r1 =sys-libs/efivar-35 =media-libs/freetype-2.8
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
Packages installed: 434
Packages in world: 22
Packages in system: 81
Required packages: 430
Number to remove: 4

I have not removed any of the packages listed in the output and wanted to ask if this is expected and intended behavior. Pulling out grub seems a little bit reckless. If I remember correctly, following the Funtoo Install Guide caused grub to be pulled in as a dependency of boot-update. Perhaps the upgrade instructions for ego 2.6.0 should be expanded to cover this.

Share this post

Link to post

Share on other sites

On my system 'emerge -cp' does not want to remove grub, although grub does not seem to be a dependency for anything:

Quote

farout ~$ emerge -cp
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*~
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence of this, it often becomes necessary to run~
* `emerge --update --newuse --deep @world` prior to depclean.
Calculating dependencies ..^H^H... done!
>>> Calculating removal order...
>>> These are the packages that would be unmerged:
sys-kernel/gentoo-sources
selected: 4.18.11~
protected: none~
omitted: 4.18.12~
All selected packages: =sys-kernel/gentoo-sources-4.18.11
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
Packages installed: 1127
Packages in world: 936
Packages in system: 84
Required packages: 1126
Number to remove: 1