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: Fri, 16 Nov 2018 19:15:47 +0100 Message-ID: <878t1svqgc.fsf@gnu.org> References: <87wopfhpi1.fsf@gnu.org> <67874006-9c7d-a3ae-bc7a-18c3d337c959@riseup.net> 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]:39184) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gNiel-0002m4-1l for guix-devel@gnu.org; Fri, 16 Nov 2018 13:15:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gNiej-0008PU-AS for guix-devel@gnu.org; Fri, 16 Nov 2018 13:15:51 -0500 In-Reply-To: <67874006-9c7d-a3ae-bc7a-18c3d337c959@riseup.net> (swedebugia's message of "Wed, 14 Nov 2018 20:20:05 +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 Hi, swedebugia skribis: > On 2018-11-14 12:23, Ludovic Court=C3=A8s wrote: >> Hello, >> >> swedebugia skribis: >> >>> "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 4 01:24 current -> /root/.config/guix/cu= rrent-1-link >>> ... >>> Then your faulty guix is in current-1-link, and your former probably we= ll 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? >> >> 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 h= opefully no >> longer relevant; I think it would clutter the manual. > > What makes you think it is behind us? I think commit aa227b3be3d7728331a08dbd139c47c9b271dc23 fixes it. No matter how old the Guix you=E2=80=99re updating from is, you shouldn=E2=80= =99t have this symlink problem. > 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 > deal with it when they try to "pull". Maybe the manual is not the best > place for this. > > We could start by putting a big WARNING to users somewhere noticeable > when the guix they run is deprecated beyond repair. No, I think that=E2=80=99s a misunderstanding of the problem. If you run =E2=80=98guix pull=E2=80=99 from 0.15.0, say, it will complete f= ine. Next time you run =E2=80=98guix pull=E2=80=99 or =E2=80=98guix pull -l=E2=80=99,= it will automatically move ~/.config/guix/current-*-link to /var/guix/profiles/per-user/$USER. The bug was that this automatic migration was buggy prior to aa227b3be3d7728331a08dbd139c47c9b271dc23, which could leave you with broken symlinks. I hope this clarifies the situation! Thanks, Ludo=E2=80=99.