From: ludo@gnu.org (Ludovic Courtès)
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: doc: Proposed note about symlinks in section "invoking guix pull"
Date: Fri, 16 Nov 2018 19:15:47 +0100 [thread overview]
Message-ID: <878t1svqgc.fsf@gnu.org> (raw)
In-Reply-To: <67874006-9c7d-a3ae-bc7a-18c3d337c959@riseup.net> (swedebugia's message of "Wed, 14 Nov 2018 20:20:05 +0100")
Hi,
swedebugia <swedebugia@riseup.net> skribis:
> On 2018-11-14 12:23, Ludovic Courtès wrote:
>> Hello,
>>
>> swedebugia <swedebugia@riseup.net> 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/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?
>>
>> I think you’re describing a terrible bug, but a bug that’s behind us
>> AFAIK. I’m reluctant to documenting an old bug that’s hopefully 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’re updating from is, you shouldn’t 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’s a misunderstanding of the problem.
If you run ‘guix pull’ from 0.15.0, say, it will complete fine. Next
time you run ‘guix pull’ or ‘guix pull -l’, 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’.
next prev parent reply other threads:[~2018-11-16 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 23:05 doc: Proposed note about symlinks in section "invoking guix pull" swedebugia
2018-11-14 11:23 ` Ludovic Courtès
2018-11-14 19:20 ` swedebugia
2018-11-16 18:15 ` Ludovic Courtès [this message]
2018-11-16 22:58 ` swedebugia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t1svqgc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.