From: swedebugia <swedebugia@riseup.net>
To: guix-devel <guix-devel@gnu.org>
Subject: doc: Proposed note about symlinks in section "invoking guix pull"
Date: Tue, 13 Nov 2018 00:05:31 +0100 [thread overview]
Message-ID: <aa8f72c8-4883-8e89-cd49-8d798a8a76e7@riseup.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Hi
The manual reads:
"This |~/.config/guix/current| profile works like any other profile
created by |guix package| (see Invoking guix package
<https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-package.html#Invoking-guix-package>).
That is, you can list generations, roll back to the previous
generation—i.e., the previous Guix—and so on:
$ guix package -p ~/.config/guix/current --roll-back
switched from generation 3 to 2
$ guix package -p ~/.config/guix/current --delete-generations=1
deleting /home/charlie/.config/guix/current-1-link"
Users without a working guix is not helped by this.
Ie they get errors when trying to run guix package -p ...:
"Missing guile-gcrypt bla bla"
I suggest a note below this saying:
"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?
--
Cheers Swedebugia
[-- Attachment #2: Type: text/html, Size: 2113 bytes --]
next reply other threads:[~2018-11-12 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 23:05 swedebugia [this message]
2018-11-14 11:23 ` doc: Proposed note about symlinks in section "invoking guix pull" Ludovic Courtès
2018-11-14 19:20 ` swedebugia
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=aa8f72c8-4883-8e89-cd49-8d798a8a76e7@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@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.