From: Ricardo Wurmus <rekado@elephly.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/3] gnu: icedtea-6: Generate keystore.
Date: Sat, 23 Jul 2016 23:19:24 +0200 [thread overview]
Message-ID: <87twfgcasj.fsf@elephly.net> (raw)
In-Reply-To: <20160723183255.GA8067@solar>
Andreas Enge <andreas@enge.fr> writes:
> Hello, Ricardo!
>
> Icedtea@1 in master now fails to build in the install-keystore phase.
> http://hydra.gnu.org:3000/build/1309224
> http://hydra.gnu.org:3000/build/1308950
> Could you have a look, please?
Hmm, that’s strange. I ran “guix build icedtea” after removing the
validation filter and built out all three versions of icedtea before
pushing this.
I don’t have the very same version of the “keytool” binary on my machine
right now (with the very same version of nss-certs as on hydra), but in
principle this works without errors:
~~~~~~~~~~~~
/gnu/store/r63vag0814nz79xr9g2ph6fvhq5xp2f3-icedtea-2.6.6/bin/keytool \
-import \
-alias ACCVRAIZ1:2.8.94.195.183.166.67.127.164.224.pem \
-keystore /tmp/keystore \
-storepass changeit \
-file /gnu/store/lp7s9x1llgw1rc675yvslxsnpcyy05ld-nss-certs-3.23/etc/ssl/certs/ACCVRAIZ1:2.8.94.195.183.166.67.127.164.224.pem
…
Trust this certificate? [no]: yes
Certificate was added to keystore
~~~~~~~~~~~~
The pem file looks like a valid X.509 certificate to me.
I cannot build icedtea@1 on my machine right now as I’m traveling, but I
just started a build remotely on my workstation in the office and it
failed. I used to have an additional stripping phase that I removed at
some point. As I continued to refine the new phase I must have used the
cached build of icedtea@1 without ever rebuilding it. Sorry!
The keytool from icedtea@1 doesn’t like this certificate. My hunch is
that we may need to remove comments from the certificate files, only
leaving the certificate block.
I’ll fix this as soon as I can.
~~ Ricardo
next prev parent reply other threads:[~2016-07-23 21:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 11:59 [PATCH 0/3] icedtea: Generate keystore Ricardo Wurmus
2016-07-18 11:59 ` [PATCH 1/3] gnu: nss-certs: Stop inheriting from nss package Ricardo Wurmus
2016-07-18 16:39 ` Leo Famulari
2016-07-18 19:34 ` Ricardo Wurmus
2016-07-18 19:39 ` Leo Famulari
2016-07-19 12:44 ` Ludovic Courtès
2016-07-18 11:59 ` [PATCH 2/3] gnu: icedtea-6: Use modify-phases syntax Ricardo Wurmus
2016-07-19 12:45 ` Ludovic Courtès
2016-07-18 11:59 ` [PATCH 3/3] gnu: icedtea-6: Generate keystore Ricardo Wurmus
2016-07-19 12:51 ` Ludovic Courtès
2016-07-19 13:03 ` Ricardo Wurmus
2016-07-22 19:14 ` Ricardo Wurmus
2016-07-23 18:32 ` Andreas Enge
2016-07-23 21:19 ` Ricardo Wurmus [this message]
2016-07-23 21:33 ` Ricardo Wurmus
2016-07-23 23:27 ` Andreas Enge
2016-07-24 7:43 ` Ricardo Wurmus
2016-07-24 8:07 ` Andreas Enge
2016-07-18 17:51 ` [PATCH 0/3] icedtea: " Roel Janssen
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=87twfgcasj.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=andreas@enge.fr \
--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).