From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Re: doc: Proposed note about symlinks in section "invoking guix pull" Date: Wed, 14 Nov 2018 20:20:05 +0100 Message-ID: <67874006-9c7d-a3ae-bc7a-18c3d337c959@riseup.net> References: <87wopfhpi1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39653) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gN0hz-0006T6-7P for guix-devel@gnu.org; Wed, 14 Nov 2018 14:20:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gN0ht-0000kG-Px for guix-devel@gnu.org; Wed, 14 Nov 2018 14:20:14 -0500 In-Reply-To: <87wopfhpi1.fsf@gnu.org> Content-Language: en-US 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: =?UTF-8?Q?Ludovic_Court=c3=a8s?= Cc: guix-devel On 2018-11-14 12:23, Ludovic Court=C3=A8s wrote: > Hello, >=20 > swedebugia skribis: >=20 >> "Note: if your have wound up with a faulty guix after a "guix pull" yo= u can manually run an older version by looking at the symlinks in your /u= ser/home/.config/guix/ directory. >> E.g. if it lists: >> $ ls -l /root/.config/guix/ >> total 0 >> lrwxrwxrwx 1 root root 33 Nov 4 01:24 current -> /root/.config/guix/c= urrent-1-link >> ... >> Then your faulty guix is in current-1-link, and your former probably w= ell 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 > I think you=E2=80=99re describing a terrible bug, but a bug that=E2=80=99= s behind us > AFAIK. I=E2=80=99m reluctant to documenting an old bug that=E2=80=99s = hopefully no > longer relevant; I think it would clutter the manual. What makes you think it is behind us? There are probably a handful of our users who has old guix installations. This will not go away anytime soon unless we state very clearly how to=20 deal with it when they try to "pull". Maybe the manual is not the best=20 place for this. We could start by putting a big WARNING to users somewhere noticeable=20 when the guix they run is deprecated beyond repair. E.g. before 1.0 implement something that we can trigger to make older=20 guix signal to the user that they should reinstall instead of running=20 "guix pull" to no avail. E.g. "*** Warning: Your guix is so outdated that guix pull is not supported.=20 Please reinstall or otherwise obtain a newer guix binary e.g. by guix=20 copy from another machine.*** Thoughts? --=20 Cheers Swedebugia