GNU bug report logs - #47202
"Bad Response-Line" error while fetching substitutes

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 47202 in the body.
You can then email your comments to 47202 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Charles Jackson <charles.b.jackson <at> protonmail.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: Guix Pull Error
Date: Wed, 17 Mar 2021 01:45:22 +0000

[Message part 1 (text/plain, inline)]

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

[Message part 2 (text/html, inline)]

[Screenshot from 2021-03-16 20-42-00.png (image/png, attachment)]

[Screenshot from 2021-03-16 20-42-38.png (image/png, attachment)]

[Screenshot from 2021-03-16 20-43-02.png (image/png, attachment)]

Message #8 received at 47202 <at> debbugs.gnu.org (full text, mbox):

From: Zachary Orlando via web <issues.guix.gnu.org <at> elephly.net>
To: 47202 <at> debbugs.gnu.org
Subject: Guix Pull Error
Date: Wed, 17 Mar 2021 13:20:19 +0100

I had this same issue, I suggest trying to cause the previous commit to pull from, 'guix pull --commit=728c908' (the number will be different for future readers.) keep in mind that this is not the best solution, it could be a security risk, but it's the fastest until a official fix is issued.

Message #11 received at 47202 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Zachary Orlando via web <issues.guix.gnu.org <at> elephly.net>,
 47202 <at> debbugs.gnu.org
Subject: Re: bug#47202: Guix Pull Error
Date: Wed, 17 Mar 2021 14:06:41 +0100

Hi,

On Wed, 17 Mar 2021 at 13:20, Zachary Orlando via web <issues.guix.gnu.org <at> elephly.net> wrote:
> I had this same issue, I suggest trying to cause the previous commit
> to pull from, 'guix pull --commit=728c908' (the number will be
> different for future readers.) keep in mind that this is not the best
> solution, it could be a security risk, but it's the fastest until a
> official fix is issued. 

I am not able to reproduce.  The command:

  guix pull --commit=728c908 -p /tmp/728c908

passes.  Idem with time-machine.

Could you retry the command?  The one above and report?


Thanks,
simon

Message #14 received at 47202 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Charles Jackson <charles.b.jackson <at> protonmail.com>
Cc: 47202 <at> debbugs.gnu.org
Subject: Re: bug#47202: Guix Pull Error
Date: Wed, 17 Mar 2021 14:06:08 +0100

Hi,

On Wed, 17 Mar 2021 at 01:45, Charles Jackson <charles.b.jackson <at> protonmail.com> wrote:
> Sorry about the screen shots, I couldn't copy in the virtual machine.

I am not able to reproduce.  The command:

   guix pull --commit=15423d38c5 -p /tmp/1542

passes.  Idem with time-machine.

Could you retry the command?  The one above and report?


Thanks,
simon

Message #17 received at 47202 <at> debbugs.gnu.org (full text, mbox):

From: Charles Jackson <charles.b.jackson <at> protonmail.com>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: "47202 <at> debbugs.gnu.org" <47202 <at> debbugs.gnu.org>
Subject: Re: bug#47202: Guix Pull Error
Date: Wed, 17 Mar 2021 19:03:46 +0000

I think the system was broken, and I have since deleted the VM. This is likely not a bug and can probably be dropped.
 Sorry for the inconvenience.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, March 17, 2021 8:06 AM, zimoun <zimon.toutoune <at> gmail.com> wrote:

> Hi,
>
> On Wed, 17 Mar 2021 at 01:45, Charles Jackson charles.b.jackson <at> protonmail.com wrote:
>
> > Sorry about the screen shots, I couldn't copy in the virtual machine.
>
> I am not able to reproduce. The command:
>
> guix pull --commit=15423d38c5 -p /tmp/1542
>
> passes. Idem with time-machine.
>
> Could you retry the command? The one above and report?
>
> Thanks,
> simon

Message #22 received at 47202-done <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Charles Jackson <charles.b.jackson <at> protonmail.com>, zimoun
 <zimon.toutoune <at> gmail.com>
Cc: "47202-done <at> debbugs.gnu.org" <47202-done <at> debbugs.gnu.org>
Subject: Re: bug#47202: Guix Pull Error
Date: Wed, 17 Mar 2021 22:16:31 +0100

[Message part 1 (text/plain, inline)]

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 (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.