Diego Elio Pettenò posted on Tue, 30 Oct 2012 07:44:20 -0700 as excerpted:
> On 30/10/2012 00:22, Mike Frysinger wrote: >> reminder: plan on landing this week. glibc-2.17 is in the process of >> shaking out upstream. > > *shrug* we've got the warning so it's fair for it to land. I recommend > people who're using ~arch to mask it on their systems for a short while > though, as we still have quite a few failures that haven't been solved — > but if they haven't been solved this month they'll require the > maintainer to stumble across them *hard*. > > https://bugs.gentoo.org/show_bug.cgi?id=glibc-2.16 FWIW, I unmasked and have been running glibc-2.16 since a couple days after the earlier announcement. I had boost-1.50 unmasked and merged before trying glibc-2.16, so that wasn't a problem, and... > Speaking of which, I confirm my plan to unmask GnuTLS 3.1 for basically > the same reason. Upstream is moving on to new versions, we're behind one > major and one minor right now. > > https://bugs.gentoo.org/show_bug.cgi?id=gnutls-3 ... I've been running gnutls-3.x for some time (at one point it was needed for the live-git pan I run), tho I had to remask gnutls-3.1.3 as I experienced some problem (IDR what) with it. But I'm running 3.1.2 without issue. What gnutls-3.1.x are you planning to unmask? Do I need to try 3.1.3 again and file a bug (if there's not one filed already) if the problem still exists, or is 3.1.2 good enough? FWIW, I also recently did a full emerge --empty-tree @world too, so there shouldn't be any hidden problems lurking around to bite on either package, at least with my @world and USE flag combo, either. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
