From: "Ludovic Courtès" <ludo@gnu.org>
To: Christoph Schumacher <christoph.schumacher@mathematik.tu-dortmund.de>
Cc: 47266@debbugs.gnu.org
Subject: bug#47266: guix pull: error (substituter)
Date: Sat, 20 Mar 2021 11:48:15 +0100 [thread overview]
Message-ID: <87blbeayog.fsf@gnu.org> (raw)
In-Reply-To: <20210319215725.GA110891@greenhouse1.mathematik.tu-dortmund.de> (Christoph Schumacher's message of "Fri, 19 Mar 2021 22:57:25 +0100")
Hi,
Christoph Schumacher <christoph.schumacher@mathematik.tu-dortmund.de>
skribis:
>> I suspect the bug is the same as <https://issues.guix.gnu.org/47157>.
[...]
> $ guix describe -p /var/guix/profiles/per-user/root/current-guix
> Generation 136 Mar 12 2021 20:25:23 (current)
> guix 35b3ab8
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 35b3ab8e5748d9911ae7a0189065d0c25392895b
>
> $ /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --version
> guix-daemon (GNU Guix) 1.2.0-15.f8953be
OK, that confirms my guess. To get the fix for
<https://issues.guix.gnu.org/47157>, you need to pull (concretely, it
was fixed by the ‘guix’ package upgrade in
94f03125463ee0dba2f7916fcd43fd19d4b6c892).
Could you upgrade and restart your daemon?
https://guix.gnu.org/manual/en/html_node/Upgrading-Guix.html
(If you get a bad-response crash while attempting to upgrade, just retry
the operation; it’s transient so every retry makes progress.)
Let us know if the problem still appears after that. I’m closing the
bug meanwhile.
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2021-03-20 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 16:04 bug#47266: guix pull: error (substituter) Christoph Schumacher
2021-03-19 18:25 ` Brian Zwahr
2021-03-19 20:12 ` Ludovic Courtès
2021-03-19 21:57 ` Christoph Schumacher
2021-03-20 10:48 ` Ludovic Courtès [this message]
2021-03-20 20:12 ` Christoph Schumacher
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=87blbeayog.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=47266@debbugs.gnu.org \
--cc=christoph.schumacher@mathematik.tu-dortmund.de \
/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).