From: Jelle Licht <jlicht@fsfe.org>
To: help-guix <help-guix@gnu.org>
Subject: tls woes with importers
Date: Tue, 24 Jul 2018 15:25:46 +0200 [thread overview]
Message-ID: <87fu089351.fsf@fsfe.org> (raw)
Hi all,
Recently, I have been running into some gnutls-issues again. The
biggest issue for me right now is the lack of a working importer, as
follows:
--8<---------------cut here---------------start------------->8---
$ guix import elpa org
Backtrace:
13 (primitive-load "/home/jelle/.config/guix/current/bin/g…")
In guix/ui.scm:
1579:12 12 (run-guix-command _ . _)
In guix/scripts/import.scm:
115:11 11 (guix-import . _)
In guix/scripts/import/elpa.scm:
108:23 10 (guix-import-elpa . _)
In guix/import/elpa.scm:
249:2 9 (elpa->guix-package "org" _)
182:13 8 (fetch-elpa-package "org" _)
113:18 7 (elpa-package-info "org" _)
85:21 6 (elpa-fetch-archive _)
In ice-9/boot-9.scm:
829:9 5 (catch system-error #<procedure 10fb300 at guix/http-c…> …)
829:9 4 (catch srfi-34 #<procedure 10e6f50 at guix/http-client…> …)
In guix/http-client.scm:
182:20 3 (_)
88:25 2 (http-fetch _ #:port _ #:text? _ #:buffered? _ # _ # _ # …)
In guix/build/download.scm:
398:4 1 (open-connection-for-uri _ #:timeout _ # _)
296:6 0 (tls-wrap #<closed: file 101f0e0> _ # _)
guix/build/download.scm:296:6: In procedure tls-wrap:
X.509 certificate of 'elpa.gnu.org' could not be verified:
signer-not-found
invalid
--8<---------------cut here---------------end--------------->8---
I am running GuixSD, with
--8<---------------cut here---------------start------------->8---
$ guix --version
guix (GNU Guix) 19f2a52644ffabf4902d0506329aa29d835dda4f
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
--8<---------------cut here---------------end--------------->8---
I have verified that I have nss-certs installed in my system profile.
Other programs using TLS connections seem to not have this issue
(e.g. Emacs and Icecat).
I have already tried:
- installing nss-certs to my user profile as well.
- installing gnutls to my user profile.
... but none of this changed anything for me sadly. Does anyone know
what I can do to remedy this situation?
Regards,
Jelle
next reply other threads:[~2018-07-24 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 13:25 Jelle Licht [this message]
2018-07-26 23:23 ` tls woes with importers Ludovic Courtès
2018-07-27 10:38 ` Jelle Licht
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=87fu089351.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=help-guix@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.
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).