bug#47202: closed (Guix Pull Error)

[GNU bug Tracking System]

Your message dated Wed, 17 Mar 2021 22:16:31 +0100
with message-id <880835897c94a303532fc8581038ff1fc86f2421.camel@telenet.be>
and subject line Re: bug#47202: Guix Pull Error
has caused the debbugs.gnu.org bug report #47202,
regarding Guix Pull Error
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
47202: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=47202
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Guix Pull Error Date: Wed, 17 Mar 2021 01:45:22 +0000

Sorry about the screen shots, I couldn't copy in the virtual machine.

Screenshot from 2021-03-16 20-42-00.png
Description: PNG image

Screenshot from 2021-03-16 20-42-38.png
Description: PNG image

Screenshot from 2021-03-16 20-43-02.png
Description: PNG image

--- End Message ---

--- Begin Message --- Subject: Re: bug#47202: Guix Pull Error Date: Wed, 17 Mar 2021 22:16:31 +0100 User-agent: Evolution 3.34.2

On Wed, 2021-03-17 at 19:03 +0000, Charles Jackson via Bug reports for GNU Guix 
wrote:
> I think the system was broken, and I have since deleted the VM.
>  This is likely not a bug and can probably be dropped.

For what it is worth now the VM has been deleted: the backtrace
is in the HTTP code of the substituter, which has some known
but tricky to identify and fix issues.  The work-around usually
is to run  "guix pull" again.  (Or "guix build", "guix install",
"guix system reconfigure" ...)

So, likely not a broken system, but rather a known issue in guix
that can be worked-around by retrying the command.

In the future, please include the commit of the guix daemon,
as that's were the substitution code is.

Thanks (& closing),
Maxime

signature.asc
Description: This is a digitally signed message part

--- End Message ---