unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: 02/02: gnu: nss, nss-certs: Update to 3.29.2.
Date: Sat, 4 Mar 2017 21:24:36 -0500	[thread overview]
Message-ID: <20170305022436.GA8108@jasmine> (raw)
In-Reply-To: <20170303164133.0350C25FC0@vcs0.savannah.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

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 <mbakke@fastmail.com>
> 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2017-03-05  2:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170303164131.9181.36224@vcs0.savannah.gnu.org>
     [not found] ` <20170303164133.0350C25FC0@vcs0.savannah.gnu.org>
2017-03-05  2:24   ` Leo Famulari [this message]
2017-03-05  3:23     ` 02/02: gnu: nss, nss-certs: Update to 3.29.2 Marius Bakke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170305022436.GA8108@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).