From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: guix-devel@gnu.org
Subject: Re: How do I fix a messed-up Guix?
Date: Tue, 16 May 2017 17:21:52 +0200 [thread overview]
Message-ID: <8f34e812-3606-6cde-4d3b-3e4807d84cd9@fastmail.net> (raw)
In-Reply-To: <38fe62eadaffe4f7823c81af2e1cc1ea@lepiller.eu>
Hi Julien,
> You could probably use the other user's guix version. Copy
> ~otheruser/.config/guix/latest to your own user's .config/guix, and try
> to guix pull from that. That won't mess with the other user's profile.
Thanks, that helped, though not directly: the other user didn't have
~/.config/guix at all. But now I know where guix stores the pointer to
its current version, and that helped me figure out how to revive an
older version of guix-latest, which... works!
Unfortunately, compiling the current git checkout with that version fails:
GUILEC guix/tests/http.go
Backtrace:
In ice-9/boot-9.scm:
160: 9 [catch #t #<catch-closure 1a9de20> ...]
In unknown file:
?: 8 [apply-smob/1 #<catch-closure 1a9de20>]
In ice-9/boot-9.scm:
66: 7 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
432: 6 [eval # #]
In ice-9/boot-9.scm:
2404: 5 [save-module-excursion #<procedure 1ad87c0 at
ice-9/boot-9.scm:4051:3 ()>]
4058: 4 [#<procedure 1ad87c0 at ice-9/boot-9.scm:4051:3 ()>]
1727: 3 [%start-stack load-stack ...]
1732: 2 [#<procedure 1aea6f0 ()>]
In unknown file:
?: 1 [primitive-load
"/home/hinsen/Development/guix/./build-aux/compile-all.scm"]
In ice-9/threads.scm:
99: 0 [loop (("guix/base16.scm" "guix/base64.scm" "guix/records.scm"
...))]
ice-9/threads.scm:99:22: In procedure loop:
ice-9/threads.scm:99:22: In procedure fport_write: Bad address
But I could run "guix pull" to get the latest release, which is good
enough for my current needs.
Thanks again,
Konrad.
prev parent reply other threads:[~2017-05-16 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 13:02 How do I fix a messed-up Guix? Konrad Hinsen
2017-05-16 13:11 ` Konrad Hinsen
2017-05-16 14:03 ` julien lepiller
2017-05-16 14:47 ` Pjotr Prins
2017-05-16 15:21 ` Konrad Hinsen [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=8f34e812-3606-6cde-4d3b-3e4807d84cd9@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.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).