From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: doc: Proposed note about symlinks in section "invoking guix pull" Date: Tue, 13 Nov 2018 00:05:31 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------624FF735A3A8378CAA11394A" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44440) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMLBS-00085M-0q for guix-devel@gnu.org; Mon, 12 Nov 2018 17:59:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMLBP-0003SC-7c for guix-devel@gnu.org; Mon, 12 Nov 2018 17:59:53 -0500 Received: from mx1.riseup.net ([198.252.153.129]:45424) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gMLBN-0003QC-1K for guix-devel@gnu.org; Mon, 12 Nov 2018 17:59:50 -0500 Received: from cotinga.riseup.net (cotinga-pn.riseup.net [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id D03851A0477 for ; Mon, 12 Nov 2018 14:59:46 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by cotinga.riseup.net with ESMTPSA id D29EC102E22 for ; Mon, 12 Nov 2018 14:59:45 -0800 (PST) Content-Language: sv-FI List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel This is a multi-part message in MIME format. --------------624FF735A3A8378CAA11394A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi The manual reads: "This |~/.config/guix/current| profile works like any other profile=20 created by |guix package| (see Invoking guix package=20 ).=20 That is, you can list generations, roll back to the previous=20 generation=E2=80=94i.e., the previous Guix=E2=80=94and so on: $ guix package -p ~/.config/guix/current --roll-back switched from generation 3 to 2 $ guix package -p ~/.config/guix/current --delete-generations=3D1 deleting /home/charlie/.config/guix/current-1-link" Users without a working guix is not helped by this. Ie they get errors when trying to run guix package -p ...: "Missing guile-gcrypt bla bla" I suggest a note below this saying: "Note: if your have wound up with a faulty guix after a "guix pull" you=20 can manually run an older version by looking at the symlinks in your=20 /user/home/.config/guix/ directory. E.g. if it lists: $ ls -l /root/.config/guix/ total 0 lrwxrwxrwx 1 root root 33 Nov=C2=A0 4 01:24 current ->=20 /root/.config/guix/current-1-link ... Then your faulty guix is in current-1-link, and your former probably=20 well working guix is in an older symlink, e.g. current-2-link. To run the guix-version before the last pull in the example above, run: /root/.config/guix/current-2-link/bin/guix Now go ahead and use that older guix to roll back as described above." What do you think? --=20 Cheers Swedebugia --------------624FF735A3A8378CAA11394A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi

The manual reads:=C2=A0

"This ~/.config/guix/current profile works like any other profile created by guix package (see Invoking guix package). That is, you can list generations, roll back to the previous generation=E2=80=94i.e., the previous Guix=E2=80=94and so on: 

$ guix package -p ~/.config/guix/current --r=
oll-back
switched from generation 3 to 2
$ guix package -p ~/.config/guix/current --delete-generations=3D1
deleting /home/charlie/.config/guix/current-1-link"
Users without a working guix is not helped by this.
Ie they get errors when trying to run guix package -p ...:
"Missing guile-gcrypt bla bla"

I suggest a note below this saying:
"Note: if your have wound up with a faulty guix after a "guix pull" you can manually run an older version by looking at the symlinks in your /user/home/.config/guix/ directory.
E.g. if it lists:
$ ls -l /root/.config/guix/
total 0
lrwxrwxrwx 1 root root 33 Nov=C2=A0 4 01:24 current -> /root/.config/guix/current-1-link
...
Then your faulty guix is in current-1-link, and your former probably well working guix is in an older symlink, e.g. current-2-link.
To run the guix-version before the last pull in the example above, run:
/root/.config/guix/current-2-link/bin/guix

Now go ahead and use that older guix to roll back as described above."

What do you think?
--
Cheers Swedebugia
--------------624FF735A3A8378CAA11394A--