From: swedebugia <swedebugia@riseup.net>
To: Leo Famulari <leo@famulari.name>
Cc: 33272@debbugs.gnu.org
Subject: bug#33272: guix refresh/download backtrace error when missing nss-certs
Date: Tue, 6 Nov 2018 12:42:07 +0100 [thread overview]
Message-ID: <a76aa405-f804-587c-85c9-ff6cbc4f5835@riseup.net> (raw)
In-Reply-To: <20181105204802.GD19298@jasmine.lan>
Hi
On 2018-11-05 21:48, Leo Famulari wrote:
> On Mon, Nov 05, 2018 at 09:39:15PM +0100, swedebugia wrote:
>> How do we catch the error?
> I am basically a novice Schemer still, so you will have to figure out
> most of this on your own, unless someone else brings more advice :)
Me too
> In general, dealing with exceptions in Guile:
>
> https://www.gnu.org/software/guile/manual/html_node/Exceptions.html
>
> There are lots of examples of how to use those mechanisms in the Guix
> source code — the error message in your original email comes from a
> caught exception in (guix build download).
>
> You'll need to find out what is crashing and generating the backtrace,
> and then decide what counts as a failure mode that we want to catch in
> that context.
Thank you for the tips. This sounds too complicated for me to bite at my
current skill level.
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-11-06 11:37 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
2018-11-05 20:48 ` Leo Famulari
2018-11-06 11:42 ` swedebugia [this message]
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=a76aa405-f804-587c-85c9-ff6cbc4f5835@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).