unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Charles Jackson <charles.b.jackson@protonmail.com>,
	zimoun <zimon.toutoune@gmail.com>
Cc: "47202-done@debbugs.gnu.org" <47202-done@debbugs.gnu.org>
Subject: bug#47202: Guix Pull Error
Date: Wed, 17 Mar 2021 22:16:31 +0100	[thread overview]
Message-ID: <880835897c94a303532fc8581038ff1fc86f2421.camel@telenet.be> (raw)
In-Reply-To: <agmekLdOLr-Pb0DCZSPlpIapliKpGCfOh9m6DXOn2Ax8nTWQgcg0x-xMp7Jq3W2tLluRT_Q-qA9-D4icYYpYzQ4tQWqt6B0Dc0IgWyrkYJA=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2021-03-17 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  1:45 bug#47202: Guix Pull Error Charles Jackson via Bug reports for GNU Guix
2021-03-17 12:20 ` Zachary Orlando via web
2021-03-17 13:06   ` zimoun
2021-03-17 13:06 ` zimoun
2021-03-17 19:03   ` Charles Jackson via Bug reports for GNU Guix
2021-03-17 21:16     ` Maxime Devos [this message]

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=880835897c94a303532fc8581038ff1fc86f2421.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=47202-done@debbugs.gnu.org \
    --cc=charles.b.jackson@protonmail.com \
    --cc=zimon.toutoune@gmail.com \
    /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).