Diego Elio Pettenò posted on Tue, 30 Oct 2012 10:56:11 -0700 as excerpted:
> On 30/10/2012 10:46, Duncan wrote: >> ... 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? > > Given that 3.1.2 is not in tree anymore there's no choice uh? Beside, I > don't go masking micro versions around. If you think there's a problem > with 3.1.3, please test and let us know as I haven't hit any (that's > what I've been using myself, and testing the tinderbox against). Followup, FWIW... I forgot I had copied the gnutls 3.1.2 ebuild from /var/db/pkg to keep portage from trying to unmerge it, when 3.1.3 wouldn't build. But it seems the problem I had must have been the parallel-build issue fixed on Oct. 19, according to the changelog. The date on my 3.1.2 binpkg rebuild is Oct. 17, while 3.1.2 was removed with the 3.1.3 introduction on the 13th. So I obviously tried to build it and failed, then with it masked again, found the old version unavailable in-tree, so copied it to my overlay from portage's pkg database, in ordered to keep portage from trying to downgrade to 2.x. But it built and installed just fine when I tried it just now. Thanks to you and Dane S. both! =:^) -- 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
