From: Simon Tournier <zimon.toutoune@gmail.com>
To: a <aaaaa@tuxpa.in>
Cc: 63451@debbugs.gnu.org
Subject: bug#63451: Guix pull not successful
Date: Tue, 23 May 2023 11:04:35 +0200 [thread overview]
Message-ID: <86edn7v2os.fsf@gmail.com> (raw)
In-Reply-To: <CAMmhH1sZiw8Yhva5X99e5bGNGUhaMGtAFRzFH0dYHUUfMF0UJg@mail.gmail.com>
Hi,
On Mon, 22 May 2023 at 23:31, a <aaaaa@tuxpa.in> wrote:
This:
> ~ guix pull -l
>
> Generation 1 Feb 05 2023 20:46:03
> guix 4b9e1e8
> Generation 2 Feb 06 2023 10:23:38
> guix a582d86
> Generation 3 May 08 2023 07:32:24
> guix e118b92
> Generation 4 May 11 2023 13:02:21
> guix d6f6b57
> Generation 5 May 14 2023 21:53:47 (current)
> guix c5fa9dd
is inconsistent with the initial report:
> λ ~ guix pull
> [1259]
> Updating channel 'guix' from Git repository at '
> https://git.savannah.gnu.org/git/guix.git'...
> Authenticating channel 'guix', commits 9edb3f6 to d6f6b57 (667 new commits)...
[...]
> guix pull: error: You found a bug: the program
> '/gnu/store/s2rl9h1zmxx84iyk25ndmn7rmy9508dj-compute-guix-derivation'
> failed to compute the derivation for Guix (version:
> "d6f6b57766e95d2fa8af63d4460a2b303ca4d867"; system: "x86_64-linux";
> host version: "1.4.0"; pull-version: 1).
And as pointed previously, this last message is also inconsistent by
itself.
>> Well, can you share the output of “guix pull -l”? It would not explain
>> why the Guile ’module-gensym’ failed though.
Well, since the error seems from:
--8<---------------cut here---------------start------------->8---
\Backtrace:
In ice-9/boot-9.scm:
222:29 19 (map1 (#<syntax ((#<syntax lambda> (#<syntax x>) #<syntax x>)
#<syntax:packages.scm:609:30 %supporte?> ?))
222:29 18 (map1 (#<syntax ((#<syntax lambda> (#<syntax x>) #<syntax x>)
(#<syntax quote> ()))> #<syntax (#<syn?> ?))
222:17 17 (map1 (#<syntax (#<syntax:packages.scm:615:31
sanitize-location> (#<syntax:packages.scm:614:22 curre?> ?))
In ice-9/psyntax.scm:
Exception thrown while printing backtrace:
Wrong type to apply: 129
>
ice-9/boot-9.scm:3165:6: In procedure module-gensym:
Invalid read access of chars of wide string: "m-1bcbf699e1749862-28a08"
--8<---------------cut here---------------end--------------->8---
Well, I do not know if it’s possible to investigate more. Especially,
when you re-run “guix pull” and it passes.
As Csepp is saying, maybe it comes from your hardware or your
filesystem.
Cheers,
simon
next prev parent reply other threads:[~2023-05-23 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 18:03 bug#63451: Guix pull not successful a
2023-05-14 14:01 ` Csepp
2023-05-15 2:52 ` a
2023-05-16 11:37 ` Simon Tournier
2023-05-23 4:31 ` a
2023-05-23 9:04 ` Simon Tournier [this message]
2023-05-25 2:31 ` a
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=86edn7v2os.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=63451@debbugs.gnu.org \
--cc=aaaaa@tuxpa.in \
/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).