everyone is doing it, so should you
Stable.
The recent portage update has made the glibc-2.3.6-r3 unstable AGAIN. I've updated the system today in the morning and in the evening it wants do downgrade to glibc-2.3.5-r3 :-(( Check this: # diff -u /var/db/pkg/sys-libs/glibc-2.3.6-r3/glibc-2.3.6-r3.ebuild /usr/portage/sys-libs/glibc/glibc-2.3.6-r3.ebuild --- /var/db/pkg/sys-libs/glibc-2.3.6-r3/glibc-2.3.6-r3.ebuild 2006-05-04 10:09:46.000000000 +0200 +++ /usr/portage/sys-libs/glibc/glibc-2.3.6-r3.ebuild 2006-05-04 17:07:09.000000000 +0200 @@ -1,6 +1,6 @@ # Copyright 1999-2006 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 -# $Header: /var/cvsroot/gentoo-x86/sys-libs/glibc/glibc-2.3.6-r3.ebuild,v 1.16 2006/05/04 02:39:53 josejx Exp $ +# $Header: /var/cvsroot/gentoo-x86/sys-libs/glibc/glibc-2.3.6-r3.ebuild,v 1.17 2006/05/04 14:43:18 dang Exp $ # TODO: # - fix warning from glibc build system: @@ -25,7 +25,7 @@ # CHOST != CTARGET - install into /usr/CTARGET/ #KEYWORDS="~amd64 ~arm -hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86" -KEYWORDS="-* ~alpha amd64 arm ~ia64 mips ppc ~ppc64 ~s390 sparc x86" +KEYWORDS="-* ~alpha ~amd64 arm ~ia64 mips ppc ~ppc64 ~s390 sparc x86" BRANCH_UPDATE=""
Yes. It turns out 2.3.6-r3 was broken, and known broken, but the bug had been closed as fixed, so I missed it. If 2.3.6-r4 turns out to be stable, we'll mark that. 2.3.6-r3 won't be marked stable. Sorry for the problems.
2.3.6-r3 is once again amd64 stable working around the string/hardened issue is trivial