From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Gnu Röoty" <walidslack@gmail.com>
Cc: 33253@debbugs.gnu.org
Subject: bug#33253: nss cannot build
Date: Sun, 4 Nov 2018 17:30:14 +0100 [thread overview]
Message-ID: <20181104173014.0a56d2dd@alma-ubu> (raw)
In-Reply-To: <CAOWR9dsydTMsydzA3UdSeHoYe1etdBZYK4_Jfk1pMpkbF8o8Gg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1799 bytes --]
On Sun, 4 Nov 2018 09:52:44 +0000
Gnu Röoty <walidslack@gmail.com> wrote:
> HI from 2 days I build the installation of guixSD to
> berlin.guixsd.org and nss-3.36.6 cant build.
This was also reported on guix-help by Brian Woodcox.
Here is some analysis I reported to that thread:
This package does not build reproducibly. At least in the long term:
There are tests that check certificates on temporal validity and that
depends on the system time.
I can reproduce your result with the 3.39 version. It looks like one
certificate is expired. All 6 failing tests look about like this one:
s -d AllDB -pp - PASSED
chains.sh: Verifying certificate(s) PayPalEE.cert with flags -d AllDB -pp
-o OID.2.16.840.1.114412.1.1
vfychain -d AllDB -pp -vv -o OID.2.16.840.1.114412.1.1 /tmp/guix-build-nss
-3.39.drv-0/nss-3.39/nss/tests/libpkix/certs/PayPalEE.cert
Chain is bad!
PROBLEM WITH THE CERT CHAIN:
CERT 0. PayPalEE :
ERROR -8181: Peer's Certificate has expired.
Returned value is 1, expected result is pass
chains.sh: #1555: RealCerts: Verifying certificate(s) PayPalEE.cert with flags -d AllDB -pp -o OID.2.16.840.1.114412.1.1 - FAILED
I don't know how to check the expiration date of PayPalEE.cert.
It looks like upstream has not yet worked on it, as the file was lastly
modified two years ago:
https://hg.mozilla.org/projects/nss/log/tip/tests/libpkix/certs/PayPalEE.cert
Cmp also this bug that demands non-expiration certificates:
https://bugzilla.mozilla.org/show_bug.cgi?id=1330010
Building 3.40 does not work with just updating version/hashsum.
A quick solution would be to build nss from a Guix git-checkout and
disable tests. But it has many dependencies, so you more or less rebuild the world.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-11-04 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 9:52 bug#33253: nss cannot build Gnu Röoty
2018-11-04 12:52 ` Quiliro Ordonez
2018-11-04 16:30 ` Björn Höfling [this message]
2021-04-03 4:44 ` Maxim Cournoyer
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=20181104173014.0a56d2dd@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=33253@debbugs.gnu.org \
--cc=walidslack@gmail.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).