unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 48045-done@debbugs.gnu.org
Subject: bug#48045: guix challenge error
Date: Tue, 11 May 2021 10:45:05 +0200	[thread overview]
Message-ID: <87cztx4q26.fsf@gnu.org> (raw)
In-Reply-To: <87eeerlj5o.fsf@disroot.org> (Bone Baboon's message of "Fri, 30 Apr 2021 14:30:27 -0400")

Hi,

Bone Baboon <bone.baboon@disroot.org> skribis:

> Ludovic Courtès writes:
>> The bug comes from the fact that it’s gone beyond 100%.  We could solve
>> it by programming more defensively, but it’d be great to see where the
>> problem comes from.
>>
>> Can you reproduce it with:
>>
>>   ./pre-inst-env guix challenge /gnu/store/5ds5bli4p6gja2yzmzzc0sik1kzrasp9-guix-extra
>>
>> ?
>>
>> If so, could you apply the patch below and send the output of this
>> command?  We can discuss it on IRC if anything’s unclear.
>
> I can not reproduce this error any more.
>
> I have a new clone of the Guix repository.
>
> I ran `./pre-inst-env guix challenge
> /gnu/store/5ds5bli4p6gja2yzmzzc0sik1kzrasp9-guix-extra` 20 times and the
> error was no error.
>
> I ran `./pre-inst-env guix challenge` several times and there was no
> error.
>
> I tried running `guix challenge
> /gnu/store/5ds5bli4p6gja2yzmzzc0sik1kzrasp9-guix-extra` outside of the
> Guix repository 20 times and there was no error.

Thanks for checking.  I’m closing it, but please do reopen if you
stumble upon it again.

Ludo’.




      reply	other threads:[~2021-05-11  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 18:40 bug#48045: guix challenge error Bone Baboon via Bug reports for GNU Guix
2021-04-28 21:20 ` Ludovic Courtès
2021-04-30 18:30   ` Bone Baboon via Bug reports for GNU Guix
2021-05-11  8:45     ` Ludovic Courtès [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=87cztx4q26.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=48045-done@debbugs.gnu.org \
    --cc=bone.baboon@disroot.org \
    /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).