help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: build failed: substituter `substitute' died unexpectedly


From: Christopher Allan Webber
Subject: Re: build failed: substituter `substitute' died unexpectedly
Date: Sat, 29 Apr 2017 19:59:27 -0500
User-agent: mu4e 0.9.18; emacs 25.2.1

Tobias Geerinckx-Rice writes:

> On 28/04/17 23:21, Tobias Geerinckx-Rice wrote:
>> On 28/04/17 23:16, Christopher Allan Webber wrote:
>>> Gave it a shot... still seems to be breaking here.
>> 
>> Oh :-(
>> 
>> Did you re-launch guix-daemon after re-building it?

Oh, I didn't!

> I forgot to mention: adding
>
>     --substitute-urls="http://bad.http.response.tobias.gr";
>
> should serve as a simple test. It always triggers the the patch for me.
>
> Kind regards,
>
> T G-R

I think I tried it right...

address@hidden:~$ guix environment --ad-hoc julia 
--substitute-urls="http://bad.http.response.tobias.gr";
substitute: Backtrace:
substitute: In ice-9/boot-9.scm:
substitute:  160: 9 [catch #t #<catch-closure 25c0ae0> ...]
substitute: In unknown file:
substitute:    ?: 8 [apply-smob/1 #<catch-closure 25c0ae0>]
substitute: In ice-9/boot-9.scm:
substitute:   66: 7 [call-with-prompt prompt0 ...]
substitute: In ice-9/eval.scm:
substitute:  432: 6 [eval # #]
substitute: In ice-9/boot-9.scm:
substitute: 2412: 5 [save-module-excursion #<procedure 25e1900 at 
ice-9/boot-9.scm:4084:3 ()>]
substitute: 4089: 4 [#<procedure 25e1900 at ice-9/boot-9.scm:4084:3 ()>]
substitute: 1734: 3 [%start-stack load-stack ...]
substitute: 1739: 2 [#<procedure 25f3ba0 ()>]
substitute: In unknown file:
substitute:    ?: 1 [primitive-load "/home/cwebber/devel/guix/scripts/guix"]
substitute: In guix/ui.scm:
substitute: 1255: 0 [run-guix-command substitute "--query"]
substitute: 
substitute: guix/ui.scm:1255:8: In procedure run-guix-command:
substitute: guix/ui.scm:1255:8: Throw to key `bad-response' with args `("Bad 
Response-Line: ~s" (""))'.
guix environment: error: corrupt input while restoring archive from #<closed: 
file 0>

I'm not really sure if this triggered the patch or not?  It does look
like a different error message, so I'm guessing it did?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]