In subject Reproducible: Always
It's a development version and we already know what to fix in current version in the tree, simply be a bit patient ;)
Indeed. Released September 26 glib-2.30 already has never been stable, which was added to the portage tree in a test version. But pango-1.29, released in mid-August, is profoundly unstable test version and not worthy to get into a tree portage. What nonsense all the same
gnome-base/libglade-2.6.4 and gnome-base/gnome-shell-3.0.2-r1 compiles successfully with x11-libs/pango-1.29.4 [+dev-libs/glib-2.30]
(In reply to comment #1) > It's a development version and we already know what to fix in current version > in the tree, simply be a bit patient ;) Pacho, I think you should reconsider; pango-1.29.4 is officially part of the gnome-3.2.0 final release, just like glib-2.30 (which is in portage), meaning that gnome upstream considers it to be stable enough. See http://ftp.gnome.org/pub/GNOME/teams/releng/3.2.0/gnome-suites-core-deps-3.2.0.modules
Then, I would wait until, either, a 1.30 version is released or any app in the tree needs it, until then, I think it can live in gnome overlay with Gnome 3.2 I think :)
pango-1.29.4 is now in portage and unmasked, since it's required for gtk+-3.2.