| View previous topic :: View next topic |
| Author |
Message |
Jach
n00b
Joined: 08 Jun 2007
Posts: 5
|
 Posted: Sun Jan 30, 2011 10:06 am Post subject: emerge world -- skipping over dependencies in package.mask |
 |
|
Hello, I have a package.mask file which contains "gnome-extra/gnome-screensaver" because I don't want it on my system. However, when I run | Code: | | emerge -avuD --keep-going world |
it ends with | Code: | !!! All ebuilds that could satisfy ">=gnome-extra/gnome-screensaver-2.30.2" have been masked.
!!! One of the following masked packages is required to complete your request:
- gnome-extra/gnome-screensaver-2.30.2 (masked by: package.mask) |
So far I've had two solutions to the problem: editing the ebuild and redigesting it (but this is undone when I sync), and second, mysteriously it will print that error but still continue to do the emerge if I add the -N option to my emerge command.
Is there a way to shut it up over that or make it not fail even without the -N option? |
|
| Back to top |
|
 |
Hu
Watchman
Joined: 06 Mar 2007
Posts: 7678
|
| Posted: Sun Jan 30, 2011 4:56 pm Post subject: |
|
|
| It appears that the only package which has this dependency is gnome-base/gnome, a meta package intended to install large parts of GNOME. If you do not want the GNOME screensaver, why not remove the meta package and instead emerge only those GNOME components you actually want? |
|
| Back to top |
|
|
steveL
Veteran
Joined: 13 Sep 2006
Posts: 1706
Location: The Peanut Gallery
|
| Posted: Sun Jan 30, 2011 4:57 pm Post subject: Re: emerge world -- skipping over dependencies in package.ma |
|
|
| Jach wrote: | Hello, I have a package.mask file which contains "gnome-extra/gnome-screensaver" because I don't want it on my system. However, when I run | Code: | | emerge -avuD --keep-going world |
it ends with | Code: | !!! All ebuilds that could satisfy ">=gnome-extra/gnome-screensaver-2.30.2" have been masked.
!!! One of the following masked packages is required to complete your request:
- gnome-extra/gnome-screensaver-2.30.2 (masked by: package.mask) |
|
There should be a few more lines explaining why the ebuild is pulled on to your system, as a dependency of other ebuilds ("required by XX" ending with selected.) As such, it needs to be emerged for other ebuilds to work. It might be possible to obviate that requirement via a USE setting, but it would be on the ebuild using this one.
| Jach wrote: | So far I've had two solutions to the problem: editing the ebuild and redigesting it (but this is undone when I sync), and second, mysteriously it will print that error but still continue to do the emerge if I add the -N option to my emerge command.
Is there a way to shut it up over that or make it not fail even without the -N option? |
I'm not sure why -N continues with the build, but wrt editing anything you'd have to do that in a local overlay, and it would be the ebuild using gnome-screensaver (it might be several which depend on it, either directly or via a chain) you would edit, not gnome-screensaver itself. You'd also have to maintain those ebuilds in the overlay as new versions coming into portage would take precedence.. in a nutshell, it's not worth it for this. (Keeping an overlay can be good for your own packages or custom versions of stuff you care about.)
It's likely you need the package installed for something else on your system, so the first thing is to find out what that is.. If you don't get help from a gnome expert on here (I don't use it) then try #gentoo-gnome and #gentoo-desktop on chat.freenode.net in an IRC client. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
