From: zimoun <zimon.toutoune@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 25719@debbugs.gnu.org
Subject: bug#25719: "guix package -i" exception should be a normal error message
Date: Tue, 01 Dec 2020 19:28:12 +0100 [thread overview]
Message-ID: <868sahv0sj.fsf@gmail.com> (raw)
In-Reply-To: <20170214094106.73469612@scratchpost.org> (Danny Milosavljevic's message of "Tue, 14 Feb 2017 09:41:06 +0100")
Hi Danny,
This old bug #25719 is about exception and error message. See:
<http://issues.guix.gnu.org/issue/25719>
On Tue, 14 Feb 2017 at 09:41, Danny Milosavljevic <dannym@scratchpost.org> wrote:
> When I have network problems sometimes I get a backtrace like this:
First, do you still experiment such behaviour? Since it 3 years old.
> ...
> substitute: 1727: 3 [%start-stack load-stack #<procedure a97d60 at ice-9/boot-9.scm:4047:10 ()>]
> substitute: 1732: 2 [#<procedure a99b70 ()>]
> substitute: In unknown file:
> substitute: ?: 1 [primitive-load "/gnu/store/175nlv448nk5kagwwl3zyy2w4726qfz6-guix-0.12.0-4.d9da/bin/.guix-real"]
> substitute: In guix/ui.scm:
> substitute: 1228: 0 [run-guix-command substitute "--query"]
> substitute:
> substitute: guix/ui.scm:1228:8: In procedure run-guix-command:
> substitute: guix/ui.scm:1228:8: Throw to key `bad-response' with args `("Bad Response-Line: ~s" (""))'.
>
> It might make sense to
>
> (a) convert that into a normal runtime error message and
What do you mean?
> (b) Fallback to substituteless building (maybe only for this thing).
Is it not the case currently?
All the best,
simon
next prev parent reply other threads:[~2020-12-01 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 8:41 bug#25719: "guix package -i" exception should be a normal error message Danny Milosavljevic
2020-12-01 18:28 ` zimoun [this message]
2020-12-02 13:35 ` Danny Milosavljevic
2020-12-14 13:11 ` zimoun
2021-03-24 21:57 ` zimoun
2021-03-24 22:23 ` Danny Milosavljevic
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=868sahv0sj.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=25719@debbugs.gnu.org \
--cc=dannym@scratchpost.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 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).