dev-python/pygobject-2.12.2 is blocked by <dev-python/pygtk-2.9. This means that any ~x86 user with both software requiring the older version of dev-python/pygtk-0.6.11-r1 (which I believe is GTK1) and software requiring pygobject (which uses the newer dev-python/pygtk-2.10.3, which is in a different SLOT to 0.6.11-r1) can no longer run "emerge -uDav world". I assume this is unintentional.
No, that's perfectly intentional. Otherwise you'll get collisions.
Eh, scratch the above, missed the slot stuff (plus the blocker doesn't work properly w/ portage-2.1.2 anyway (Bug 150879)
*** Bug 151447 has been marked as a duplicate of this bug. ***
Hmm, this didn't move much... :) Oh well, a sucky patch but the only solution until portage supports ranged deps (Bug 4315). Or we can just WONTFIX this. :) <snip> --- pygobject-2.12.2.ebuild.old 2006-10-30 11:36:21.000000000 +0100 +++ pygobject-2.12.2.ebuild 2006-11-08 19:37:38.000000000 +0100 @@ -16,7 +16,14 @@ RDEPEND=">=dev-lang/python-2.3.5 >=dev-libs/glib-2.8 - !<dev-python/pygtk-2.9" + !=dev-python/pygtk-1.9* + !=dev-python/pygtk-2.0* + !=dev-python/pygtk-2.2* + !=dev-python/pygtk-2.3* + !=dev-python/pygtk-2.4* + !=dev-python/pygtk-2.6* + !=dev-python/pygtk-2.7* + !=dev-python/pygtk-2.8*" DEPEND="${RDEPEND} doc? ( dev-libs/libxslt >=app-text/docbook-xsl-stylesheets-1.70.1 ) >=dev-util/pkgconfig-0.12.0" </snip>
<dev-python/pygtk-2 package.masked for gnome-1 removal, together with stuff that depends on it. Not much of an issue any longer, closing.