Tracker bug for build breakage induced by gtk+ 2.14 (required for Gnome 2.24)
When it's first pass stabilization time, at least >=dev-util/intltool-0.40.4 and >=gnome-base/libgnomeui-2.24.0 need to go stable at the same time as well. libgnomeui just removes the filechooser backend modules (and gtk3 compatibility preparations), because the semi-private GtkFileSystem API doesn't exist anymore in this form - has to go stable at the same time primarily because libgnomeui-2.22 doesn't build anymore due to no GtkFileSystem.
intltool-0.40 is just a dep of new libgnomeui
gtk+-2.14 is now unmasked. Hopefully not too many additional broken packages turn up :P
Please consider dev-java/java-gnome-4.0.7-r2 in stabilization list because the current stable (4.0.7) has a crasher bug with 2.14 which is fixed in this revision.
I've just filed #244471 to stabilize ruby-gtk2+-0.16.0-r4.
Current stable gnome-sharp (and related) 2.16 won't work with gtk+-2.14, then. maybe all new gnome/gtk-sharp stuff will need to be stabilized with new gtk+/glib (I can open a separate bug report for gnome-sharp not compiling if you want)
Yes, please a new bug blocking 253934 as I'm closing this one now, as the known and filed stuff is all fixed.
(In reply to comment #6)
> Yes, please a new bug blocking 253934 as I'm closing this one now, as the known
> and filed stuff is all fixed.
New gtk-sharp will require mono-2, then, I think that bug 234305 is the one that should block bug 253934 (sorry for the inconvenience if I am wrong)