Eric Livingston wrote:
Here's what I get when I try to perform an "update world" operation. I
get
other versions of the same thing if I try --deep and other options
(meaning
other packages besides baselayout crap out with the same message).
For some reason, it seems my portage ebuilds are masked? I originally
got this
error with portage 2.0.47, then manually upgrades to 2.0.48 (same
thing), and
now I'm at 2.0.49-r1 and still get the message. (apparently I can still manually emerge specific .ebuild files, including portage ones.).
Any help would be *greatly* appreciated, as I'm now stuck it seems.
---------------- example ---------------- www profiles # emerge -pu world
These are the packages that I would merge, in order:
Calculating world dependencies - !!! all ebuilds that could satisfy ">=sys-apps/portage-2.0.23" have been masked. !!! (dependency required by "sys-apps/baselayout-1.8.6.12-r3"
[ebuild])
!!! Problem with ebuild sys-libs/zlib-1.2.1-r2 !!! Possibly a DEPEND/*DEPEND problem.
!!! Depgraph creation failed.
Is portage referenced anywhere in /etc/portage/package.mask?
Hmmm, ok. I guess I see what happened. After the last "emerge sync", the only two portage ebuilds left under sys-apps/portage are 2.0.49-r19 and 2.0.50-pre9. /usr/portage/profiles/package.mask does have a filter of ">=sys-apps/portage-2.0.49-r19".
So, apparently my last "emerge sync" left me with only masked-out versions of portage! I had manually upagraded to 2.0.49-r19 to see if it would fix this problem, but it didn't for clear reasons (now).
I changed the filter to ">sys-apps/portage-2.0.49-r19" (my version) and "emerge -pu --deep world" works fine, apparently, so I guess that fixed it.
However, now I have another concern: in the comments to that portage filter in package.mask, it talks about an API change, etc. By upgrading my portage to that level, have I broken something? Should I somehow go backwards? Given that I now have no ebuilds earlier than 2.0.49-r19, how would I go backwards if I wanted to? Should I just continue on from here?
Thanks, Eric
P.S. - Oh, by the way: my package.mask is in /usr/portage/profiles. I don't have a /etc/portage directory. Should I? Is my installation mis-configured somehow?
No. '/etc/portage' is a user-defined over-ride directory for the stuff in '/usr/portage/profiles'.
-- Andrew Gaffney System Administrator Skyline Aeronautics, LLC. 776 North Bell Avenue Chesterfield, MO 63005 636-357-1548
-- [EMAIL PROTECTED] mailing list
