From: Christopher Howard <christopher@librehacker.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Broken Guix Pull
Date: Fri, 02 Jul 2021 14:56:45 -0800 [thread overview]
Message-ID: <e0e21927198fb55f82784c0f3ad661d82104c80e.camel@librehacker.com> (raw)
In-Reply-To: <87wnq8tl52.fsf@nckx>
Hi, that's me!
I picked a random /gnu/store/*/bin/guix, and got the same error
message. I also, as I mentioned, did a separate checkout from guix and
built it myself, and running the guix pull from that. I could do try a
few more /gnu/store/*/bin/guix binaries to be thorough, but I expect I
would continue to get the same result.
Something is certainly corrupted somewhere, but I can't figure out
where, or what it is exactly that I need to repair or delete or
whatever.
From that repair command error message I posted, you would think it
would have to be that one guix package in the store. But then, why
doesn't it work with other guix binaries?
From the build log I posted, it seems like guix is trying to load guix
code from some dependency package, but it definitely isn't clear to me
how that works.
-----Original Message-----
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Christopher Howard <christopher@librehacker.com>, help-guix@gnu.org
Subject: Re: Broken Guix Pull
Date: Sat, 03 Jul 2021 00:16:25 +0200
Maxim Cournoyer 写道:
> I hope others will have more helpful replies than mine, but
> perhaps your
> file system was badly damaged.
If this is lispmacs from #guix, that's exactly what happened after
a power failure.
I don't see it mentioned in the OP but I also suggested running
‘guix pull’ from each /gnu/store/*/bin/guix, but apparently that
didn't work(?).
Kind regards,
T G-R
next prev parent reply other threads:[~2021-07-02 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 15:29 Broken Guix Pull Christopher Howard
2021-07-02 21:16 ` Maxim Cournoyer
2021-07-02 22:16 ` Tobias Geerinckx-Rice
2021-07-02 22:56 ` Christopher Howard [this message]
2021-07-03 5:17 ` Christopher Howard
2021-07-03 5:59 ` Christopher Howard
-- strict thread matches above, loose matches on Subject: below --
2016-12-18 20:20 Broken guix pull Dmitri Anikin
2016-12-18 20:30 ` David Craven
2016-12-18 21:03 ` David Craven
2016-12-18 21:16 ` Leo Famulari
2016-12-19 11:34 ` Dmitri Anikin
2016-12-19 15:14 ` Leo Famulari
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=e0e21927198fb55f82784c0f3ad661d82104c80e.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=help-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=me@tobias.gr \
/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.
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).