Please stabilize 1.34.2, it's been in ~arch since february Also it's blocking an update of glib Reproducible: Always
We cannot stabilize gobject-introspection-1.34 until glib-2.34 is stabilized. To stabilize glib-2.34, we need to seriously test it with stable packages and fix issues like bug #450930
Sorry, I had glib keyworded for ~x86, didn't realize it... *grins sheepishly*
(In reply to Alexandre Rostovtsev from comment #1) > We cannot stabilize gobject-introspection-1.34 until glib-2.34 is stabilized. > > To stabilize glib-2.34, we need to seriously test it with stable packages > and fix issues like bug #450930 specially for this bug, there is a patch included with a successful test report provided by a user.
*** Bug 481072 has been marked as a duplicate of this bug. ***
*** Bug 481070 has been marked as a duplicate of this bug. ***
*** Bug 481068 has been marked as a duplicate of this bug. ***
To elaborate on the duplicate bugs I just erroneously created -- in order to allow stable users to emerge thunar[X,udev] without portage reporting a bunch of --autounmask keywording requirements (a bug that has been around for a year), please stabilize the following ASAP for KEYWORDS="alpha amd64 arm ia64 ppc ppc64 sh sparc x86" =gnome-base/gvfs-1.14.2 =dev-libs/glib-2.34.3 =dev-libs/gobject-introspection-1.34.2-r1 =dev-libs/gobject-introspection-common-1.34.2
Created attachment 356076 [details] list 1 Proposed minimum stabilization list. Do we need to stabilize gtk+-3.6.x at the same time?
Created attachment 356082 [details] list 2 Forgot to add pygobject and glib-networking
(In reply to Alexandre Rostovtsev from comment #8) > Created attachment 356076 [details] > list 1 > > Proposed minimum stabilization list. > > Do we need to stabilize gtk+-3.6.x at the same time? Won't that cause a Gnome 3 cascade?
Has anyone checked if new glib-2.34 and gtk+-3.6 are working ok with Gnome 2.32? And also, if old gnome packages are still building ok with them, because I jumped directly from glib-2.32 and old gnome2 to gnome 3.8 and latest glib :/
ping ; what can we do to speed this up so that ATs can get CC'd?
Created attachment 360004 [details] list 3 Updated stabilization list, now with gtk+-3.6, libsecret, glibmm/gtkmm, and webkit-gtk-1.10. Because really, all of them should be stabilized in one go, and now that gnome-3.10 has arrived, keeping 3 generations of ~arch glib and gtk+:3 in one tree would become unmanageable. [I am not very comfortable with stabilizing glib-2.36/gtk+-3.8 without the rest of gnome-3.8 due to e.g. glib type system changes that broke pygobject:2. And it looks like getting all of gnome-3.8 stable would take longer than expected.]
If you look at remaining blocks for gnome 3.8, I think it's more near than expected ;)
*sigh* ... The point of this bug was to get a newer glib etc. stabilized for gnome:2 compatibility so that udisks and others would work properly as per the defaults (ie bug 431424). ie, to have this done -long before- anything gnome:3 relates was going to be stabilized. Of course, since that never happened...
Created attachment 360090 [details] list 4 updated list - final version.
Arches, please test and stabilize the attached list of packages.
Created attachment 360124 [details] list 5 Updated list: added at-spi-1.32.0-r2 to ensure gtk2 accessibility works with both gnome2 and gnome3.
Created attachment 360334 [details] list 6 Bumped x11-libs/gtk+ stabilization candidate to 3.6.3-r3 in order to fix bug #487110.
arm stable
Stable for HPPA.
Please continue in gnome-3.8-stable bug *** This bug has been marked as a duplicate of bug 478252 ***
