From: Roel Janssen <roel@gnu.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: icedtea-8: Build keystore without id-ecPublicKey certificates.
Date: Mon, 27 Feb 2017 15:02:48 +0100 [thread overview]
Message-ID: <rbuzih7zq7r.fsf@gnu.org> (raw)
In-Reply-To: <87y3wr2465.fsf@zancanaro.id.au> (Carlo Zancanaro's message of "Mon, 27 Feb 2017 23:45:22 +1100")
Carlo Zancanaro <carlo@zancanaro.id.au> writes:
> On Sun, Feb 26 2017, Roel Janssen wrote
>> Great idea. This is also a more durable solution for when certificates
>> change in nss-certs.
>
> Yeah, that was my thinking. I had tried to do it earlier, but hadn't
> noticed the incorrect permissions later on in the build (which had
> caused my attempts to fail).
>
>> I think we should add ourselves to the copyright notice.
>> Other than that, I think this patch is good to be pushed.
>
> I've added both of us to the copyright notice (I hope that isn't too
> presumptuous). Patch is attached.
Great!
Unfortunately, I don't seem to be able to apply your patch. It errors
with the following:
error: patch failed: gnu/packages/java.scm:1
error: gnu/packages/java.scm: patch does not apply
I tried with two different machines, both resulting in the error
displayed above.
Sorry for the inconvenience, but could you redo the patch?
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2017-02-27 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 11:32 [PATCH] gnu: icedtea-8: Build keystore without id-ecPublicKey certificates Roel Janssen
2017-02-26 0:44 ` Carlo Zancanaro
2017-02-26 17:02 ` Roel Janssen
2017-02-27 12:45 ` Carlo Zancanaro
2017-02-27 14:02 ` Roel Janssen [this message]
2017-03-01 21:23 ` Carlo Zancanaro
2017-03-01 22:31 ` Ricardo Wurmus
2017-03-01 22:52 ` Roel Janssen
2017-03-02 7:07 ` Ricardo Wurmus
2017-02-27 15:01 ` Ricardo Wurmus
2017-02-27 21:16 ` Carlo Zancanaro
2017-02-27 22:07 ` Leo Famulari
2017-03-01 22:34 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rbuzih7zq7r.fsf@gnu.org \
--to=roel@gnu.org \
--cc=carlo@zancanaro.id.au \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.