From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: doc: Proposed note about symlinks in section "invoking guix pull" Date: Wed, 14 Nov 2018 12:23:18 +0100 Message-ID: <87wopfhpi1.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39816) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMtGh-0003m1-QQ for guix-devel@gnu.org; Wed, 14 Nov 2018 06:23:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMtGe-000615-N5 for guix-devel@gnu.org; Wed, 14 Nov 2018 06:23:35 -0500 In-Reply-To: (swedebugia's message of "Tue, 13 Nov 2018 00:05:31 +0100") 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: swedebugia Cc: guix-devel Hello, swedebugia skribis: > "Note: if your have wound up with a faulty guix after a "guix pull" you c= an manually run an older version by looking at the symlinks in your /user/h= ome/.config/guix/ directory. > E.g. if it lists:=20 > $ ls -l /root/.config/guix/ > total 0 > lrwxrwxrwx 1 root root 33 Nov 4 01:24 current -> /root/.config/guix/curr= ent-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.=20 > 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? I think you=E2=80=99re describing a terrible bug, but a bug that=E2=80=99s = behind us AFAIK. I=E2=80=99m reluctant to documenting an old bug that=E2=80=99s hope= fully no longer relevant; I think it would clutter the manual. Does that make sense? Ludo=E2=80=99.