From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: HELP needed with CA certificates! [PATCH] gnu: Add tup, Add pbpst.
Date: Thu, 1 Sep 2016 16:22:43 +0200 [thread overview]
Message-ID: <idja8fritsc.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87oa47sp7u.fsf@we.make.ritual.n0.is>
ng0 <ng0@we.make.ritual.n0.is> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi,
>>
>> ng0 <ng0@we.make.ritual.n0.is> skribis:
>>
>>>> The ‘nss-certs’ package provides X.509 certificates:
>>>>
>>>> https://www.gnu.org/software/guix/manual/html_node/X_002e509-Certificates.html
>>>
>>> I commented nss-certs, enabled or disabled it made no difference to the
>>> resulting binary.
>>
>> You need to have ‘nss-certs’ installed, *and* set the environment
>> variables mentioned above (depending on whether you use OpenSSL, GnuTLS,
>> Git, etc.; for GnuTLS, I think there’s no such environment variable.)
>>
>> HTH!
>> Ludo’.
>
> Thanks.
>
> Can you be more specific on why it could fail when all of this is set in
> the user environment? I did all of this, and it still fails. environment
> values exported in my user profile, nss-certs installed in user profile
> and system wide, set nss-certs as an input of pbpst, still:
What environment variables did you set? The patch for pbpst is very
hard to read, so it’s not obvious what you tried.
If this tool just shells out to “curl” then it might respect
“CURL_CA_BUNDLE” as per the Curl documentation.
~~ Ricardo
next prev parent reply other threads:[~2016-09-01 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 20:12 HELP needed with CA certificates! [PATCH] gnu: Add tup, Add pbpst ng0
2016-08-28 21:02 ` Ludovic Courtès
2016-08-28 21:34 ` ng0
2016-08-31 20:27 ` Ludovic Courtès
2016-09-01 13:51 ` ng0
2016-09-01 14:22 ` Ricardo Wurmus [this message]
2016-09-16 14:42 ` ng0
2016-09-27 18:48 ` Leo Famulari
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=idja8fritsc.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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).