From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
Subject: Re: How do I fix a messed-up Guix?
Date: Tue, 16 May 2017 17:21:52 +0200
Message-ID: <8f34e812-3606-6cde-4d3b-3e4807d84cd9@fastmail.net>
References: <c72429db-d89d-0d37-7a34-0b5f9e1e101e@fastmail.net>
	<adaeddf6-45a7-4a2a-2f8f-74f06b0afcfe@fastmail.net>
	<38fe62eadaffe4f7823c81af2e1cc1ea@lepiller.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37056)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <konrad.hinsen@fastmail.net>) id 1dAeIS-00053P-C5
	for guix-devel@gnu.org; Tue, 16 May 2017 11:22:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <konrad.hinsen@fastmail.net>) id 1dAeIN-0006x8-Bv
	for guix-devel@gnu.org; Tue, 16 May 2017 11:22:00 -0400
Received: from out1-smtp.messagingengine.com ([66.111.4.25]:38487)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <konrad.hinsen@fastmail.net>)
	id 1dAeIN-0006wj-10
	for guix-devel@gnu.org; Tue, 16 May 2017 11:21:55 -0400
In-Reply-To: <38fe62eadaffe4f7823c81af2e1cc1ea@lepiller.eu>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: guix-devel@gnu.org

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.