[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 02/02: gnu: nss, nss-certs: Update to 3.29.2.
From: |
Marius Bakke |
Subject: |
Re: 02/02: gnu: nss, nss-certs: Update to 3.29.2. |
Date: |
Sun, 05 Mar 2017 04:23:57 +0100 |
User-agent: |
Notmuch/0.23.7 (https://notmuchmail.org) Emacs/25.1.1 (x86_64-unknown-linux-gnu) |
Leo Famulari <address@hidden> writes:
> On Fri, Mar 03, 2017 at 11:41:32AM -0500, Marius Bakke wrote:
>> mbakke pushed a commit to branch master
>> in repository guix.
>>
>> commit 3b175eab84f9899804b466506a57b5807285150a
>> Author: Marius Bakke <address@hidden>
>> Date: Fri Mar 3 17:21:58 2017 +0100
>>
>> gnu: nss, nss-certs: Update to 3.29.2.
>>
>> * gnu/packages/certs.scm (nss-certs): Update to 3.29.2.
>> * gnu/packages/gnuzilla.scm (nss): Update to 3.29.2.
>> * gnu/packages/patches/nss-pkgconfig.patch: Adapt to context changes.
>
> NSS 2.29.2 failed to build on armhf.
>
> This means that armhf users still do not have the most recent set of
> CA certificates as compiled by Mozilla and released on 2017-01-04 as NSS
> 3.28.1:
>
> https://wiki.mozilla.org/NSS:Release_Versions
>
> The build was restarted and I'm unable to access the log now, but the
> build process appeared to simply stop in the middle of printing a line.
> Here is the latest build attempt:
>
> https://hydra.gnu.org/job/gnu/master/nss-3.29.2.armhf-linux
I filed a bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1344493
I wonder if it would pass if we relaxed the timeout, it looks it might
be a race condition (test expecting error but client still connecting).
signature.asc
Description: PGP signature