Re: How do I fix a messed-up Guix?

[Konrad Hinsen]

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.