View previous topic :: View next topic |
Author |
Message |
zaggo n00b
Joined: 02 Sep 2002 Posts: 51 Location: Austria
|
Posted: Wed Jan 08, 2003 5:48 pm Post subject: "emerge -u world" |
|
|
Hi!
When i make a emerge -u world or an -pu world i get the error-message
Code: |
!!! all ebuilds that could satisfy "sys-apps/baselayout" have been masked.
!!! (dependency required by "sys-libs/glibc-2.3.1-r2" [ebuild])
|
I've got an 1.4 rc1 system. Maybe somebody already solved that problem.
Thx for advice.
Manuel |
|
Back to top |
|
|
elzbal Guru
Joined: 31 Aug 2002 Posts: 364 Location: Seattle, WA, USA
|
Posted: Wed Jan 08, 2003 6:33 pm Post subject: |
|
|
I have a similar problem, and I've been rsync'ing 4 times a day for the past 3 days or so waiting for it to clear:
Code: | # emerge -up world
These are the packages that I would merge, in order:
Calculating world dependencies -
!!! all ebuilds that could satisfy ">=gnome-base/control-center-2.0.3-r1" have been masked.
!!! (dependency required by "gnome-base/gnome-2.0.3-r1" [ebuild]) |
The interesting thing about my case is that control-center-2.0.3-r1 is installed. I installed it the other day by directly specifying the ebuild file:
Code: | # emerge -s control-center
Searching...
[ Results for search key : control-center ]
[ Applications found : 1 ]
* gnome-base/control-center
Latest version available: 2.0.3
Latest version installed: 2.0.3-r1
Size of downloaded files: 1,184 kB
Homepage: http://www.gnome.org/
Description: the gnome2 Desktop configuration tool
# emerge -c control-center
gnome-base/control-center
selected: none
protected: 1.4.0.5-r1 2.0.3-r1
omitted: none
>>> clean: No packages selected for removal.
# ACCEPT_KEYWORDS="~x86" emerge -up control-center
These are the packages that I would merge, in order:
Calculating dependencies ...done!
|
I checked out the ebuild and found the following:
There are 11 dependencies to control-center. They are all installed and up to date, and none of them exhibit any problems with 'emerge -up xxx'.
According to the keywords line, "x86" is listed (as opposed to "~x86"), so it does not appear to be in the 'unstable' branch. Furthermore, this package is not masked out.
My first question is... How do I continue? Is this problem unique to myself? Is this an issue with the ebuild that will be fixed soon? Is there something else in the ebuild that I can change to continue?
My second question is... Is this a bug that 'emerge -u' would trip over a package that is already installed? If someone more knowledgeable than myself about portage can verify that this is not some obscure but desired feature, I will gladly add this to bugzilla.
Thanks! |
|
Back to top |
|
|
radfaraf n00b
Joined: 25 May 2002 Posts: 55 Location: NJ
|
Posted: Wed Jan 08, 2003 6:46 pm Post subject: |
|
|
Same deal here today.
emerge -pu world
These are the packages that I would merge, in order:
Calculating world dependencies /
!!! all ebuilds that could satisfy ">=gnome-extra/gal-0.21" have been masked.
!!! (dependency required by "gnome-extra/gtkhtml-1.1.7-r1" [ebuild]) |
|
Back to top |
|
|
Zr40 Tux's lil' helper
Joined: 19 Sep 2002 Posts: 76
|
Posted: Wed Jan 08, 2003 7:54 pm Post subject: |
|
|
Here too.
Quote: | emerge -p world
These are the packages that I would merge, in order:
Calculating world dependencies |
!!! all ebuilds that could satisfy "=sys-devel/libperl-5.8.0*" have been masked.
!!! (dependency required by "sys-devel/perl-5.8.0-r8" [ebuild]) |
This is odd, because libperl-5.8.0 isn't masked at all. |
|
Back to top |
|
|
Qubax Guru
Joined: 19 Jul 2002 Posts: 451 Location: Tirol, Austria
|
Posted: Wed Jan 08, 2003 8:18 pm Post subject: |
|
|
emerge -pu world
These are the packages that I would merge, in order:
Calculating world dependencies /
!!! all ebuilds that could satisfy ">=app-crypt/gpgme-0.3.10" have been masked.
!!! (dependency required by "net-mail/sylpheed-claws-0.8.8" [ebuild]) |
|
Back to top |
|
|
pilla Bodhisattva
Joined: 07 Aug 2002 Posts: 7729 Location: Underworld
|
Posted: Wed Jan 08, 2003 8:23 pm Post subject: |
|
|
aren't these ebuilds masked with ~ARCH?
Try
ACCEPT_KEYWORDS="~x86" emerge -pu world _________________ "I'm just very selective about the reality I choose to accept." -- Calvin |
|
Back to top |
|
|
zaggo n00b
Joined: 02 Sep 2002 Posts: 51 Location: Austria
|
Posted: Wed Jan 08, 2003 8:41 pm Post subject: |
|
|
Bloody Bastard wrote: | aren't these ebuilds masked with ~ARCH?
Try
ACCEPT_KEYWORDS="~x86" emerge -pu world |
That doesn't work for me.
Code: |
b-28 root # ACCEPT_KEYWORDS="~x86"
b-28 root # emerge -pu world
These are the packages that I would merge, in order.
Calculating world dependencies |
!!! all ebuilds that could satisfy "sys-apps/baselayout" have been masked.
!!! (dependency required by "sys-libs/glibc-2.3.1-r2" [ebuild])
b-28 root #
|
|
|
Back to top |
|
|
elzbal Guru
Joined: 31 Aug 2002 Posts: 364 Location: Seattle, WA, USA
|
Posted: Wed Jan 08, 2003 8:50 pm Post subject: |
|
|
Bloody Bastard wrote: | aren't these ebuilds masked with ~ARCH?
Try
ACCEPT_KEYWORDS="~x86" emerge -pu world |
I'm no expert, but I don't think that they are.
If it were masked as unstable for x86, I would expect to see the following in the ebuild (for control-center):
Code: | KEYWORDS="~x86 ~ppc ~sparc ~alpha" |
Instead, I see:
Code: | KEYWORDS="x86 ~ppc ~sparc ~alpha" |
Furthermore, these packages do not appear in the package.mask file.
I have checked a few of these cases (at least control-center, libperl, and baselayout), and they all seem to be unmasked. Futhermore, I am not having any trouble emerge -up'ing libperl and baselayout. I know my portage tree is up-to-date (as of a few hours ago), and I assume that the rest of these folks are as well.
Could we be seeing the beginning of a new emerge bug emerging (no pun intended)? Is mask data cached in any other place, say, in /var/db/pkg?
(FWIW, my /var/db/pkg/gnome-base/control-center-2.0.3-r1/control-center-2.0.3-r1.ebuild file has the correct unmasked ACCEPT_KEYWORDS.)
And by the way, 'ACCEPT_KEYWORDS="~x86" emerge -pu world' works fine, but I'd rather not upgrade everything to the unstable branch. |
|
Back to top |
|
|
radfaraf n00b
Joined: 25 May 2002 Posts: 55 Location: NJ
|
Posted: Wed Jan 08, 2003 9:53 pm Post subject: |
|
|
Whatever it was has fixed itself now. I did a few emerge rsync's in the meantime and the one I did now fixed it. |
|
Back to top |
|
|
Zr40 Tux's lil' helper
Joined: 19 Sep 2002 Posts: 76
|
Posted: Wed Jan 08, 2003 10:30 pm Post subject: |
|
|
radfaraf wrote: | Whatever it was has fixed itself now. I did a few emerge rsync's in the meantime and the one I did now fixed it. |
Unfortunately not here. It still quits with the masked perl ebuild. |
|
Back to top |
|
|
zaggo n00b
Joined: 02 Sep 2002 Posts: 51 Location: Austria
|
Posted: Wed Jan 08, 2003 10:49 pm Post subject: |
|
|
I tried some things but nothin worked, but what i don't understand is that when i emerge a new package it works without a problem. In addition when i do an emerge -p xfree:
Code: |
b-28 root # emerge -p xfree
These are the packages that I would merge, in order.
Calculating dependencies ...done!
[ebuild N ] x11-misc/ttmkfdir-3.0.4
[ebuild U ] media-libs/freetype-2.1.2-r2
[ebuild U ] media-libs/fontconfig-2.1
[ebuild U ] x11-base/xfree-4.2.1-r2
|
but when i do an emerge -pu xfree i get the error:
Code: |
b-28 root # emerge -pu xfree
These are the packages that I would merge, in order.
Calculating dependencies -
!!! all ebuilds that could satisfy "sys-apps/baselayout" have been masked.
!!! (dependency required by "sys-libs/glibc-2.3.1-r2" [ebuild])
|
The same is with glibc and so on.
Greets,
Manuel |
|
Back to top |
|
|
radfaraf n00b
Joined: 25 May 2002 Posts: 55 Location: NJ
|
Posted: Thu Jan 09, 2003 2:11 am Post subject: |
|
|
rsynced again
problem is back |
|
Back to top |
|
|
pilla Bodhisattva
Joined: 07 Aug 2002 Posts: 7729 Location: Underworld
|
Posted: Thu Jan 09, 2003 3:11 am Post subject: |
|
|
Maybe you've got a lazy rsync server, which is still outdated
radfaraf wrote: | rsynced again
problem is back |
_________________ "I'm just very selective about the reality I choose to accept." -- Calvin |
|
Back to top |
|
|
^Martin^ n00b
Joined: 09 Jan 2003 Posts: 2
|
Posted: Thu Jan 09, 2003 4:24 am Post subject: how about this? |
|
|
I have the same problem. Maybe it has something to do with the fact that most of us are still probbaly on gcc2? (am I right in assuming that?) Maybe its trying to upgrade to gcc3 but is getting confused? |
|
Back to top |
|
|
dangerweasel n00b
Joined: 15 Aug 2002 Posts: 47 Location: Outer Rim
|
Posted: Thu Jan 09, 2003 4:32 am Post subject: |
|
|
I was having this problem, continually, until I added
Code: | ACCEPT_KEYWORD=¨~x86¨ |
to my make.conf file.
Now I am running into other problems with masked packages. I am still trying to get winex to install again. I keep getting an error in the ebuild. |
|
Back to top |
|
|
pilla Bodhisattva
Joined: 07 Aug 2002 Posts: 7729 Location: Underworld
|
Posted: Thu Jan 09, 2003 4:43 am Post subject: |
|
|
Be aware that running software from the unstable branch may be dangerous to your health.
dangerweasel wrote: | I was having this problem, continually, until I added
Code: | ACCEPT_KEYWORD=¨~x86¨ |
to my make.conf file.
Now I am running into other problems with masked packages. I am still trying to get winex to install again. I keep getting an error in the ebuild. |
_________________ "I'm just very selective about the reality I choose to accept." -- Calvin |
|
Back to top |
|
|
^Martin^ n00b
Joined: 09 Jan 2003 Posts: 2
|
Posted: Thu Jan 09, 2003 4:54 am Post subject: |
|
|
Just talked to some folks on IRC. Just emerge rsync, and it should be all fixed. |
|
Back to top |
|
|
elzbal Guru
Joined: 31 Aug 2002 Posts: 364 Location: Seattle, WA, USA
|
Posted: Thu Jan 09, 2003 5:48 am Post subject: |
|
|
^Martin^ wrote: | Just talked to some folks on IRC. Just emerge rsync, and it should be all fixed. |
I for one have been emerging rsync at least 5 times a day for the past 3-4 days, and at least 10 times today. (There, I just did it again!) I have seen a number of rsync servers serving up a number of new ebuilds. For what it's worth, I have a Gentoo 1.4 rc1 system whose base package has been updated to that of rc2.
I have no problems with unstable packages (I'm happily running KDE3.1rc5, soon to be rc6), but I'd rather do this on a package-by-package basis where I know the specific benefits as well as the risks. I would prefer not to move to unstable just to get around this issue - that has the potential to open a whole new can of worms.
I think I am noticing a trend here where random packages, which are NOT masked or in any way part of the unstable tree, are somehow tagged as 'masked' on certain systems. These packages seem to be random (baselayout, libperl, control-center, etc).
For those of you who are experiencing this problem, please answer the following questions:
Have you rsynced multiple times? Have you confirmed that this package and all of its dependencies are NOT masked?
What version of Gentoo are you on? What version of emerge?
Have you done anything additional to troubleshoot this problem?
For me, I verified that the KEYWORDS line in the affected ebuild included 'x86' and not '~x86'. I verified that it was not masked in the package.mask file. I went through each and every dependency listed in the affected package (there were 11 in my case) and verified that I could 'emerge -up' them with no errors (additionally, no action needed to be taken for those - they were all installed).
As I mentioned, I am effectively on Gentoo 1.4rc2, having recently upgraded the base system (emerge -u system) from rc1. This was within the last few days, and I did not have any trouble with emerge -up world at that time (although I did not upgrade the entire world at that time either - I started with specific packages I cared about the most). 'emerge --version' shows me 'Portage 2.0.46-r4 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r2)'.
I have additionally emerged the specific required package by specifying the ebuild on the command line, so the package in question is already installed.
I am somewhat new to Gentoo and Linux in general compared to many of the folks around here, but I certainly wouldn't consider myself a newbie. I also have years of experience with administering Solaris and *BSD systems. Based on the behavior I have seen, I think this is almost certainly a bug. I would like to get some information from some of the other folks experiencing this problem to compile a decent bug report.
If some of the folks who have been around the Gentoo block a few more times than I (Bloody Bastard?) would like to chime in with their opinions, I would appreciate that as well. Is there anything fundamental or obscure that I am missing? Is this worthy of a bug report? |
|
Back to top |
|
|
zaggo n00b
Joined: 02 Sep 2002 Posts: 51 Location: Austria
|
Posted: Thu Jan 09, 2003 8:11 am Post subject: |
|
|
Ok i solved the problem for my case.
I think the problem was the "old" portage system. I emerge portage again (not -u because that's not working --> same error as before) and now emerge -pu world and everything else works again.
greets
Manuel |
|
Back to top |
|
|
elzbal Guru
Joined: 31 Aug 2002 Posts: 364 Location: Seattle, WA, USA
|
Posted: Thu Jan 09, 2003 5:19 pm Post subject: |
|
|
Thanks, Zaggo, you helped me to resolve my problem as well. I was already on the latest 'stable' version of portage (2.0.46-r4). I re-emerged it, and it didn't work either. But on a hunch, I upgraded to an unstable portage (2.0.47), and 'emerge -up world' works fine now.
I still feel that there was a bug, but so long as it seems to be fixed in the latest version, that is a good workaround. |
|
Back to top |
|
|
xlyz Veteran
Joined: 27 Oct 2002 Posts: 1470 Location: Italy
|
Posted: Thu Jan 09, 2003 8:33 pm Post subject: |
|
|
zaggo wrote: | Ok i solved the problem for my case.
I think the problem was the "old" portage system. I emerge portage again (not -u because that's not working --> same error as before) and now emerge -pu world and everything else works again.
greets
Manuel |
same problem, but if I try your solution:
Code: | ACCEPT_KEYWORDS="~x86" emerge -p sys-apps/portage
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] sys-apps/portage-2.0.46-r4
|
and
Code: |
ACCEPT_KEYWORDS="~x86" emerge -p sys-apps/portage-2.0.47.ebuild
These are the packages that I would merge, in order:
Calculating dependencies \!!! Failed to stat ebuild: /usr/portage/root/portage/portage-2.0.47.ebuild
!!! doebuild: /usr/portage/root/portage/portage-2.0.47.ebuild not found.
aux_get(): (1) couldn't open cache entry for root/portage-2.0.47
Check for syntax error or corruption in the ebuild.
emerge: create(): aux_get() error on root/portage-2.0.47; aborting...
|
suggestions? |
|
Back to top |
|
|
hhaamu Apprentice
Joined: 23 Aug 2002 Posts: 253 Location: Finland
|
Posted: Thu Jan 09, 2003 8:46 pm Post subject: |
|
|
Do the 'emerge portage' line like this:
Code: | emerge /usr/portage/sys-apps/portage/portage-2.0.47.ebuild |
|
|
Back to top |
|
|
xlyz Veteran
Joined: 27 Oct 2002 Posts: 1470 Location: Italy
|
Posted: Thu Jan 09, 2003 8:56 pm Post subject: |
|
|
compiling
...
It did not fix it
Code: | emerge -pu world
These are the packages that I would merge, in order:
Calculating world dependencies /
!!! all ebuilds that could satisfy ">=sys-apps/groff-1.18" have been masked.
!!! (dependency required by "sys-apps/man-1.5k-r1" [ebuild])
|
|
|
Back to top |
|
|
xlyz Veteran
Joined: 27 Oct 2002 Posts: 1470 Location: Italy
|
Posted: Thu Jan 09, 2003 10:34 pm Post subject: |
|
|
emerged again 2.0.46 and now it works
(well, almost, -u is fine -u --deep not ) |
|
Back to top |
|
|
dsmoot n00b
Joined: 09 Jan 2003 Posts: 6
|
Posted: Thu Jan 09, 2003 10:54 pm Post subject: Same Here |
|
|
I get this same thing:
%emerge world
These are the packages that I would merge, in order:
Calculating world dependencies /
!!! all ebuilds that could satisfy ">=sys-apps/groff-1.18" have been masked.
!!! (dependency required by "sys-apps/man-1.5k-r1" [ebuild])
I've tried to emerge portage 2.0.46, 2.0.47
and everything else in this thread,
Any suggestions? will this fix itself in some time? |
|
Back to top |
|
|
|