Bug 245092 – Please stabilize dev-libs/glib-2.16.6

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Markos Chandras (RETIRED) 2008-10-31 19:20:45 UTC]

Please stabilize dev-libs/glib-2.16.6 . Compiles fine with gcc-4.3

Reproducible: Always




Due to upcoming stabilization of gcc-4.3 , Please stabilize dev-libs/glib-2.16.6

[Comment 1 Mart Raudsepp 2008-11-03 05:54:11 UTC]

2.18.x is about ready to go stable within a week instead.

[Comment 2 Daniel Gryniewicz (RETIRED) 2008-11-03 14:46:56 UTC]

Does this mean we're going to just leave 2.16.6 ~arch?  Or nuke it?  I'd say it should probably go stable anyway, since 2.16 isn't going to be removed any time soon.  (and before 2.18 goes stable would be easier for arch teams to test).

[Comment 3 Markos Chandras (RETIRED) 2008-11-03 16:18:22 UTC]

I think the best is to mark 2.16.6 as stable and leave 2.18.X for more testing. Since gcc-4.3 is about to be marked as stable , i can confirm that the glib-2.16.6 works with gcc-4.3 just fine. I dont know about 2.6.18 cause i am not using it

[Comment 4 Mart Raudsepp 2008-11-03 19:30:48 UTC]

(In reply to comment #3)
> I think the best is to mark 2.16.6 as stable and leave 2.18.X for more testing.
> Since gcc-4.3 is about to be marked as stable

Not before many weeks or even months. This is huge work, and tracking of everything is just starting.

(In reply to comment #2)
> Does this mean we're going to just leave 2.16.6 ~arch?  Or nuke it?  I'd say it
> should probably go stable anyway, since 2.16 isn't going to be removed any time
> soon.

I don't particularly care. We will be stuck with 2.16.5 anyway, because some certain arches won't stabilize 2.16.6 before 2.18 is up for it already.

[Comment 5 Gilles Dartiguelongue (RETIRED) 2009-01-11 22:44:09 UTC]

so two months later, what do we do ? Is 2.18 going stable now or what ?

[Comment 6 Joeri Capens 2009-01-13 11:07:21 UTC]

On my system I get a "GLib-CRITICAL **: g_bookmark_file_get_size: assertion `bookmark !=
NULL' failed" error message on system shutdown.

This error is mentioned in http://bugzilla.gnome.org/show_bug.cgi?id=550096 and fixed in glib 2.16.6 .

After updating to this version, the error message is not shown anymore on my system.

Glib 2.18 getting ready has nothing to do with this. People have 2.16 on their system now and 2.16.6 is slightly better than 2.16.5, so it should be stabilized.

[Comment 7 Gilles Dartiguelongue (RETIRED) 2009-02-09 21:43:11 UTC]

Hello arches, 

target keywords are:
alpha amd64 arm hppa ia64 m68k ppc ppc64 s390 sh sparc x86

thanks in advance for the magic.

[Comment 8 Jeroen Roovers (RETIRED) 2009-02-11 16:59:10 UTC]

Stable for HPPA.

[Comment 9 Tobias Klausmann (RETIRED) 2009-02-11 21:57:03 UTC]

Stable on alpha.

[Comment 10 Daniel Gryniewicz (RETIRED) 2009-02-13 21:12:09 UTC]

alpha: you stabilized 2.18.1, not 2.16.6.  Please switch it back.

[Comment 11 Tobias Klausmann (RETIRED) 2009-02-13 21:42:32 UTC]

Fixed (and stabilized 16.6). Thanks for the heads up.

[Comment 12 Markus Meier 2009-02-14 22:17:18 UTC]

amd64/x86 stable

[Comment 13 Raúl Porcel (RETIRED) 2009-02-15 12:33:10 UTC]

arm/ia64/s390/sh/sparc stable

[Comment 14 Brent Baude (RETIRED) 2009-02-16 15:39:44 UTC]

ppc stable

[Comment 15 Brent Baude (RETIRED) 2009-03-02 21:04:24 UTC]

ppc64 done

[Comment 16 Gilles Dartiguelongue (RETIRED) 2009-03-15 12:21:05 UTC]

@m68k, ping ?

[Comment 17 Raúl Porcel (RETIRED) 2009-03-17 10:17:56 UTC]

m68k stable, thanks to kolla for testing, closing