I've try to update-world --prepare and get the following message: Calculating world dependencies | !!! All ebuilds that could satisfy ">=x11-wm/metacity-2.15.5" have been masked. !!! One of the following masked packages is required to complete your request: - x11-wm/metacity-2.16.3 (masked by: ~amd64 keyword) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by "dev-python/gnome-python-desktop-2.16.0" [ebuild]) Please don't make a package stable if it has a dependency which is not stable.
(In reply to comment #0) > Please don't make a package stable if it has a dependency which is not stable. Which package? Sorry but you didn't post any useful info, lacking paranormal skills here.
Whatever... 12 Dec 2006; Chris Gianelloni <wolf31o2@gentoo.org> metacity-2.16.3.ebuild: Stable on amd64 wrt bug #156662.
Not a bug.
(In reply to comment #1) > Which package? Sorry but you didn't post any useful info, lacking paranormal > skills here. From the original message: "(dependency required by "dev-python/gnome-python-desktop-2.16.0" [ebuild])" gnome-python-desktop-2.16.0 was keyworded amd64 2006/12/12 16:21:08 metacity-2.16.3 was keyworded amd64 2006/12/12 17:04:28 So this seems like a legitimate bug to me, although one that's fixed already.
*** Bug 158586 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > gnome-python-desktop-2.16.0 was keyworded amd64 2006/12/12 16:21:08 > metacity-2.16.3 was keyworded amd64 2006/12/12 17:04:28 Dunno how you, but other devs unfortunately lack the magic ability to keyword and commit tens on ebuilds in a single second.
OK but I was pretty, good user I've runned emerege --sync, and I get the error, I've re-emerged portage and get the same error. Now what to do? Any idea?
So the problem remained after emerge --sync so I reopen it.
So attach the ebuild here because it's amd64 (stable) in CVS, and it's stable on any mirror I tried.
Created attachment 104419 [details] metacity ebuild The ebuild is OK, but I get the error. So I think the bug is in the portage itself, not the ebuild. I've runned emerge --regen after I removed /var/cache/edb/dep, but the problem remain.
I'm waiting for further ideas.
If I give # emerge -puvD metacity I get [ebuild UD] x11-wm/metacity-2.14.5 [2.16.3] USE="-debug -xinerama" 0 kB Same with #emerge -pv metacity [ebuild UD] x11-wm/metacity-2.14.5 [2.16.3] USE="-debug -xinerama" 0 kB Why want the portage downgrade it?
I've solved! After removing the xeffects layer all problem solved. So sorry the problem was in the overlay. Maybe the emerge --sync could sync the overlays too, or a message would be shown after emerge --sync somthig like that "Please sync your overlays too." If the user has overlays.
Reopen to resolve properly. (Dunno why everyone feels the urge to overlay stuff that's up-to-date in portage, completely needlessly).
INVALID.
Closed.