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