From: swedebugia <swedebugia@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: doc: Proposed note about symlinks in section "invoking guix pull"
Date: Wed, 14 Nov 2018 20:20:05 +0100 [thread overview]
Message-ID: <67874006-9c7d-a3ae-bc7a-18c3d337c959@riseup.net> (raw)
In-Reply-To: <87wopfhpi1.fsf@gnu.org>
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?
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.
E.g. before 1.0 implement something that we can trigger to make older
guix signal to the user that they should reinstall instead of running
"guix pull" to no avail.
E.g.
"*** Warning: Your guix is so outdated that guix pull is not supported.
Please reinstall or otherwise obtain a newer guix binary e.g. by guix
copy from another machine.***
Thoughts?
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-11-14 19:20 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 [this message]
2018-11-16 18:15 ` Ludovic Courtès
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=67874006-9c7d-a3ae-bc7a-18c3d337c959@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.