From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH core-updates] gnu: nss, nss-certs: Update to 3.29.1.
Date: Wed, 1 Mar 2017 20:56:39 -0500 [thread overview]
Message-ID: <20170302015639.GB23686@jasmine> (raw)
In-Reply-To: <20170301235317.32331-1-mbakke@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Thu, Mar 02, 2017 at 12:53:17AM +0100, Marius Bakke wrote:
> I was not able to build 'nss' on core-updates. This patch works
> for me on x86_64.
>
> * gnu/packages/certs.scm (nss-certs): Update to 3.29.1.
> * gnu/packages/gnuzilla.scm (nss): Update to 3.29.1.
> * gnu/packages/patches/nss-pkgconfig.patch: Adjust to context changes.
Here are the release notes:
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.29.1_release_notes?utm_campaign=feed&utm_medium=rss&utm_source=developer.mozilla.org
The last time, this failed on armhf and the update stalled:
http://lists.gnu.org/archive/html/guix-devel/2016-12/msg00822.html
It would be great if we had an armhf machine outside of the build farm
to test on. We could always try virtualizing armhf with QEMU. Or maybe
just push it to master and cross our fingers. I don't like that we
aren't keeping up with changes to the certificate store in nss-certs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-02 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 23:53 [PATCH core-updates] gnu: nss, nss-certs: Update to 3.29.1 Marius Bakke
2017-03-02 1:56 ` Leo Famulari [this message]
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=20170302015639.GB23686@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).