As of commit ed047cf2c607277629c20bf1a88d727a7f9bb79e we have sys-libs/glibc-2.23 in ~arch.
This breaks *lots* of stuff. For example coreutils was broken [1]. According to the tracker bug [2] most of the breakage was introduced in a gentoo-specific patch. On the upstream mailinglist [3] people seem to be concerned about the change: " It's risky enough that I think it's worth doing a distro rebuild with that change to find out what, if anything, breaks - who do I talk to to make that happen? " So why on earth are we applying a random patch that upstream is not using, *and* unleashing it on ~arch without any of the usual precautions like masking the package until some of the issues have been smoked out? I very strongly suggest bumping the glibc ebuild, removing the patch in the bump, and masking the broken version. Then asking people to test the patched version to smoke out failures, and in a few months we can consider re-enabling this tomfoolery. (And with very strongly suggest I mean QA might just do it because breaking random shit is not cool, yo. So please fix it soon) At this point I'm a little bit confused why Gentoo users are used as guinea pigs and stuff gets broken on purpose. It's not how one should do things, and excuses like "it finds bugs" are just lame excuses. So anyway. Please not to break things. For prosperous happy of users! [1] https://bugs.gentoo.org/580014 [2] https://bugs.gentoo.org/show_bug.cgi?id=575232#c7 [3] https://sourceware.org/ml/libc-alpha/2015-11/msg00253.html
