From: swedebugia <swedebugia@riseup.net>
To: Leo Famulari <leo@famulari.name>, 33272@debbugs.gnu.org
Subject: bug#33272: guix refresh/download backtrace error when missing nss-certs
Date: Mon, 5 Nov 2018 21:39:15 +0100 [thread overview]
Message-ID: <f700a2d4-7f80-e342-ce84-20a38add0f83@riseup.net> (raw)
In-Reply-To: <20181105202650.GB19298@jasmine.lan>
Hi
On 2018-11-05 21:26, Leo Famulari wrote:
> On Mon, Nov 05, 2018 at 12:16:08PM +0100, swedebugia wrote:
> 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.
Agreed.
>
> 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
Sounds like a good idea.
How do we catch the error?
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-11-05 20:40 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
2018-11-05 20:39 ` swedebugia [this message]
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
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=f700a2d4-7f80-e342-ce84-20a38add0f83@riseup.net \
--to=swedebugia@riseup.net \
--cc=33272@debbugs.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.
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).