Jump to content
funtoo forums
  • 0
Sign in to follow this  
lazlo.vii

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

Question

I followed the instructions in this thread:

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.

In the meantime I'll just add sys-boot/grub to my world file.

Edited by lazlo.vii
Punctuation

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

Verify you have installed ego-2.6.0-r2

On my system ego-2.6.0-r2 depends on grub due to boot-update integration.

funtoo /home/rj # equery d grub
 * These packages depend on grub:
app-admin/ego-2.6.0-r2 (sys-boot/grub)
funtoo /home/rj # ego query v ego
 app-admin/ego| slot|               repo
--------------+-----+-------------------
         2.4.2|    0| core-kit/1.2-prime
       2.5.0.2|     | core-kit/1.2-prime
       2.5.0.4|     | core-kit/1.2-prime
    * 2.6.0-r2|     | core-kit/1.2-prime
          9999|     | core-kit/1.2-prime

 

 

Share this post


Link to post
Share on other sites
  • 0

@cardinal

>ego query v ego
 app-admin/ego| slot|               repo
--------------+-----+-------------------
         2.4.2|    0| core-kit/1.2-prime
       2.5.0.2|     | core-kit/1.2-prime
       2.5.0.4|     | core-kit/1.2-prime
    * 2.6.0-r2|     | core-kit/1.2-prime
          9999|     | core-kit/1.2-prime

 

>equery d grub
 * These packages depend on grub:

On my server Portage thinks that nothing depends on grub. 



@Oleg Vinichenko

2 hours ago, Oleg Vinichenko said:

This is link to the new Funtoo Installation Guide.   "This page was last edited on October 5, 2018, at 22:02."

Share this post


Link to post
Share on other sites
  • 0

May I add to the confusion?

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
Quote

farout ~$ ego query v ego

 app-admin/ego| slot|               repo
--------------+-----+-------------------
         2.4.2|    0| core-kit/1.2-prime
       2.5.0.2|     | core-kit/1.2-prime
       2.5.0.4|     | core-kit/1.2-prime
    * 2.6.0-r2|     | core-kit/1.2-prime
          9999|     | core-kit/1.2-prime
Quote

farout ~$ equery d grub
 * These packages depend on grub:

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...