unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: a <aaaaa@tuxpa.in>
Cc: 63451@debbugs.gnu.org
Subject: bug#63451: Guix pull not successful
Date: Sun, 14 May 2023 16:01:45 +0200	[thread overview]
Message-ID: <87r0rjm2n8.fsf@riseup.net> (raw)
In-Reply-To: <CAMmhH1uJs_veUfNQwb67tFuwQbpg6sRFyRh2bkKwWcqPHguFdw@mail.gmail.com>


a <aaaaa@tuxpa.in> writes:

> first, i i ran guix pull and this happened. 
> i don't see anything in my kernel logs around this time
>
> λ ~ 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)...
> Building from this channel:
>   guix      https://git.savannah.gnu.org/git/guix.git   d6f6b57
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
> substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'... 100.0%
> building /gnu/store/kxhxsxmann4jv6z62z0ssh011sahk88k-compute-guix-derivation.drv...
> Computing Guix derivation for 'x86_64-linux'... /warning: 'texlive-latex-tools' is deprecated, use 'texlive-tools' instead
> warning: 'texlive-latex-graphics' is deprecated, use 'texlive-graphics' instead
> warning: 'texlive-generic-etexcmds' is deprecated, use 'texlive-etexcmds' instead
> warning: 'texlive-generic-infwarerr' is deprecated, use 'texlive-infwarerr' instead
> warning: 'texlive-latex-graphics' is deprecated, use 'texlive-graphics' instead
> warning: 'texlive-latex-graphics' is deprecated, use 'texlive-graphics' instead
> warning: 'texlive-generic-atbegshi' is deprecated, use 'texlive-atbegshi' instead
> warning: 'texlive-latex-atveryend' is deprecated, use 'texlive-atveryend' instead
> \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"

This looks very weird, could you run a disk check and a guix store check
just to be safe?




  reply	other threads:[~2023-05-14 14:04 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 [this message]
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
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=87r0rjm2n8.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --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).