From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 02/05: gnu: nss, nss-certs: Update to 3.29.3.
Date: Tue, 14 Mar 2017 17:27:01 -0400 [thread overview]
Message-ID: <20170314212701.GA8440@jasmine> (raw)
In-Reply-To: <871stzh8rv.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On Tue, Mar 14, 2017 at 05:02:12PM -0400, Mark H Weaver wrote:
> This is not really sustainable. A single build attempt takes 7 hours on
> armhf, and about 40 hours on mips. When the failure occurs, it causes
> hundreds of other dependency failures, which must be restarted manually,
> one at a time, via the web interface. (We have a way to restart *all*
> dependency failures, but that results in a huge amount of wasted work
> for Hydra).
>
> We need test suites to be robust on heavily loaded build machines.
I agree that this situation is not sustainable. If we are committed to
offering substitutes, we can't have such a critical package not building
reliably.
But, it seems unsatisfactory to not update NSS / nss-certs without
working towards a real solution.
Nss-certs provides the CA certificate store in Guix. It does get updated
along with NSS [0], although not in every NSS release.
I think we should find a way to decouple the certificate store from NSS,
since we can't build NSS reliably.
> Is there a compelling reason not to revert this update for now?
Since there were no changes to the certificates between 3.29.2 and
3.29.3, I think it's fine to revert.
[0]
https://wiki.mozilla.org/NSS:Release_Versions
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-14 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170313174039.25881.89989@vcs0.savannah.gnu.org>
[not found] ` <20170313174040.C5C6B20CAB@vcs0.savannah.gnu.org>
2017-03-14 6:24 ` 02/05: gnu: nss, nss-certs: Update to 3.29.3 Mark H Weaver
2017-03-14 6:31 ` Mark H Weaver
2017-03-14 9:14 ` Marius Bakke
2017-03-14 21:02 ` Mark H Weaver
2017-03-14 21:27 ` Leo Famulari [this message]
2017-03-14 21:39 ` Marius Bakke
2017-03-14 21:59 ` Leo Famulari
2017-03-14 22:12 ` Marius Bakke
2017-03-15 13:12 ` Marius Bakke
2017-03-15 16:26 ` Ludovic Courtès
2017-03-15 17:04 ` Marius Bakke
2017-03-15 18:42 ` Mark H Weaver
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=20170314212701.GA8440@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).