unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: gnu: nss, nss-certs: Update to 3.27.2.
Date: Tue, 20 Dec 2016 13:56:03 -0500	[thread overview]
Message-ID: <878traa0qk.fsf@netris.org> (raw)
In-Reply-To: <20161214151942.79CB12201D1@vcs.savannah.gnu.org> (Leo Famulari's message of "Wed, 14 Dec 2016 15:19:42 +0000 (UTC)")

leo@famulari.name (Leo Famulari) writes:

> lfam pushed a commit to branch master
> in repository guix.
>
> commit 7ab3ea426640e4e7ae798a8f72b3c90b383cb824
> Author: Leo Famulari <leo@famulari.name>
> Date:   Tue Dec 13 18:59:50 2016 -0500
>
>     gnu: nss, nss-certs: Update to 3.27.2.
>     
>     * gnu/packages/gnuzilla.scm (nss): Update to 3.27.2.
>     * gnu/packages/certs.scm (nss-certs): Update to 3.27.2.

Thanks for this, but unfortunately this version of 'nss' seems to
consistently fail its test suite on armhf, or at least it has failed 3
times in a row.

  https://hydra.gnu.org/build/1712083

Given the importance of the proper functioning of this package, I'm not
comfortable disabling the tests.

Do we have reason to believe that this update fixes security flaws?  Is
there a compelling reason not to revert this update until a version is
released that passes the test suite on our supported systems?

     Thanks,
       Mark

       reply	other threads:[~2016-12-20 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161214151942.11288.43191@vcs.savannah.gnu.org>
     [not found] ` <20161214151942.79CB12201D1@vcs.savannah.gnu.org>
2016-12-20 18:56   ` Mark H Weaver [this message]
2016-12-20 19:39     ` 03/03: gnu: nss, nss-certs: Update to 3.27.2 Leo Famulari
2016-12-21  6:09     ` Leo Famulari
2016-12-21 16:38       ` Leo Famulari
2016-12-29 18:24         ` Leo Famulari

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=878traa0qk.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).