From: Leo Famulari <leo@famulari.name>
To: swedebugia <swedebugia@riseup.net>
Cc: 33272@debbugs.gnu.org
Subject: bug#33272: guix refresh/download backtrace error when missing nss-certs
Date: Mon, 5 Nov 2018 15:26:50 -0500 [thread overview]
Message-ID: <20181105202650.GB19298@jasmine.lan> (raw)
In-Reply-To: <c3452987-de4e-fc70-ef01-c0c717141561@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On Mon, Nov 05, 2018 at 12:16:08PM +0100, swedebugia wrote:
> I suggest we change it to fail nicely. I am willing to create a patch. Would
> somebody be willing to mentor me?
>
> As a start:
>
> How do I check if nss-certs is installed?
>
> This is the first thing we should do when handling https-URIs
>
> (define tls-wrap is a quite complicated procedure, maybe an extra (if at the
> body (of the let) will do?
>
> something like
>
> (if package-available? nss-certs
>
> true; continue
>
> false-> error nicely
IMO a better solution is to catch the error and print an informative
message. Already, the error message at the end is coming from Guix, but
we should hide the backtrace and add a hint towards a solution.
I think handling the TLS error gracefully is orthogonal to whether or
not nss-certs is installed.
There are other X.509 certificate collections available on the systems
that Guix supports, and even some Guix packages use their own
collections. Also, programs that need to look up certificates tend to
find them via environment variables, so if one wanted to use nss-certs,
it's not enough just to install it.
https://www.gnu.org/software/guix/manual/en/html_node/X_002e509-Certificates.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-05 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 11:16 bug#33272: guix refresh/download backtrace error when missing nss-certs swedebugia
2018-11-05 20:26 ` Leo Famulari [this message]
2018-11-05 20:39 ` swedebugia
2018-11-05 20:48 ` Leo Famulari
2018-11-06 11:42 ` swedebugia
2018-11-06 17:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181105202650.GB19298@jasmine.lan \
--to=leo@famulari.name \
--cc=33272@debbugs.gnu.org \
--cc=swedebugia@riseup.net \
/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.