all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 25422@debbugs.gnu.org
Subject: bug#25422: GIT_SSL_CAINFO set incorrectly
Date: Wed, 11 Jan 2017 15:36:31 -0500	[thread overview]
Message-ID: <20170111203631.GA30202@jasmine> (raw)

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]

Recently, Guix started to set the environment GIT_SSL_CAINFO like a
search path, instead of pointing to single file, which is what it should
be.

This makes Git unable to access remotes over HTTPS. It show a message
like this:

fatal: unable to access 'https://example.com/repo.git': Problem with the
SSL CA cert (path? access rights?)

I think this used to work "out of the box", at least on GuixSD.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2017-01-11 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 20:36 Leo Famulari [this message]
2017-01-14 21:20 ` bug#25422: GIT_SSL_CAINFO set incorrectly Ludovic Courtès
2017-01-22 21:51   ` bug#25422: [PATCH 0/2] Support single-entry search paths Ludovic Courtès
2017-01-22 21:52     ` bug#25422: [PATCH 1/2] guix package: Honor the order of profiles when -p appears multiple times Ludovic Courtès
2017-01-22 21:52     ` bug#25422: [PATCH 2/2] search-paths: Allow specs with #f as their separator Ludovic Courtès
2017-01-23 13:00     ` bug#25422: [PATCH 0/2] Support single-entry search paths Ricardo Wurmus
2017-01-23 22:02       ` Ludovic Courtès
2017-04-02 22:22         ` Ludovic Courtès
2017-01-20  4:27 ` bug#25422: GIT_SSL_CAINFO set incorrectly Mekeor Melire
2017-01-23 13:57   ` Ludovic Courtès
2017-02-10 16:22     ` Mekeor Melire
2017-02-10 20:51       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170111203631.GA30202@jasmine \
    --to=leo@famulari.name \
    --cc=25422@debbugs.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.