From: Alex Vong <alexvong1995@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: gccgo package does not include gccgo binary
Date: Tue, 12 Jul 2016 22:13:33 +0800 [thread overview]
Message-ID: <87y457q702.fsf@gmail.com> (raw)
In-Reply-To: <20160712123551.GA13332@jasmine> (Leo Famulari's message of "Tue, 12 Jul 2016 08:35:51 -0400")
Leo Famulari <leo@famulari.name> writes:
> On Tue, Jul 12, 2016 at 07:05:24PM +0800, Alex Vong wrote:
>> I forget to tell that I am not using Guix SD but using Guix on top of
>> Debian. Do you have any recommendation on this?
>
> This works for me in my login shell profile:
>
> if [ -d /etc/ssl/certs ]; then
> export SSL_CERT_DIR=/etc/ssl/certs
> export SSL_CERT_FILE=$SSL_CERT_DIR/ca-certificates.crt
> export GIT_SSL_CAINFO=$SSL_CERT_FILE
> fi
It turns out Guix profile already exported this environment variable for
me, so exporting it before sourcing Guix profile has no effect at all.
Eventually, I get this working with certificates from Debian,
GUIX_PROFILE="$HOME/.guix-profile" \
. "$HOME/.guix-profile/etc/profile"
GIT_SSL_CAINFO="/etc/ssl/certs/ca-certificates.crt"
export GIT_SSL_CAINFO
But why are the certificates from nss-certs not usable?
next prev parent reply other threads:[~2016-07-12 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 14:55 gccgo package does not include gccgo binary Alex Vong
2016-07-09 18:23 ` Leo Famulari
2016-07-09 22:09 ` Matthew Jordan
2016-07-10 15:29 ` Alex Vong
2016-07-10 17:16 ` Matthew Jordan
2016-07-12 1:20 ` Alex Vong
2016-07-12 9:38 ` Matthew Jordan
2016-07-12 11:05 ` Alex Vong
2016-07-12 12:35 ` Leo Famulari
2016-07-12 14:13 ` Alex Vong [this message]
2016-07-12 13:23 ` Ludovic Courtès
2016-07-13 14:41 ` git ca cert problems Alex Vong
2016-07-13 21:11 ` Ludovic Courtès
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=87y457q702.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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.
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).