From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org
Subject: Overview of Guix pull symlinks and thoroughly test it
Date: Wed, 7 Nov 2018 13:15:13 +0100 [thread overview]
Message-ID: <90787542-4e51-ac0e-5c8c-bef10e61ab3c@riseup.net> (raw)
In-Reply-To: <ca83b53a-b2fe-bde8-46e6-ffbf6c55f094@freenet.de>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
Hi
Reading (again) about somebody being bit by the pull-bull ;-) (below)
Is there an overview of guix directories and symlinks?
Anyone got any ideas of how to thoroughly test this pull-beast to make
it less brittle and erroneous?
Cheers
swedebugia
-------- Forwarded Message --------
Subject: Re: guix pull fails while Migrating profile generations
Date: Tue, 6 Nov 2018 20:33:54 +0100
From: Thorsten Wilms <t_w_@freenet.de>
Reply-To: t_w_@freenet.de
To: help-guix@gnu.org
Hi!
On Ubuntu, starting from
"guix pull: error: symlink: File exists: ..."
I manually removed/changed/created symlinks and had guix working again.
A few `guix pull` and `sudo guix pull` later:
---
~: guix pull
guile: warning: failed to install locale
hint: Consider installing the `glibc-utf8-locales' or `glibc-locales'
package and defining `GUIX_LOCPATH', along these lines:
guix package -i glibc-utf8-locales
export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
See the "Application Setup" section in the manual, for more info.
Migrating profile generations to '/var/guix/profiles/per-user/thorwil'...
guix pull: error: symlink: File exists:
"/var/guix/profiles/per-user/thorwil/current-guix"
---
(glibc-utf8-locales is installed and
GUIX_LOCPATH=/home/thorwil/.guix-profile/lib/locale is set, but that's
another topic)
Now:
---
~: readlink ~/.config/guix/current
current-1-link
---
current-1-link doesn't exist!
I'm breathing manually now. I would appreciate an overview of what is
supposed to sit where and where it is supposed to point to. I may have
gotten something wrong ... but then again, guix working and failing
again shortly after isn't exactly the outcome I'd expect in that case.
Sidenote: I wanted to try pulling as root and then choosing the same
commit as user, as recently suggested:
---
~: sudo guix describe
(...)
guix: describe: command not found
---
Plain `guix describe` did work, until this linking business went wrong
again.
---
~: sudo guix --version
=> 0.15.0-2.8bbb79c
---
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
[-- Attachment #2: Type: text/html, Size: 4326 bytes --]
next prev parent reply other threads:[~2018-11-07 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 16:39 guix pull fails while Migrating profile generations Henk Katerberg
2018-11-06 10:29 ` Ludovic Courtès
2018-11-06 12:24 ` Henk Katerberg
2018-11-06 19:33 ` Thorsten Wilms
2018-11-07 12:15 ` swedebugia [this message]
2018-11-07 15:04 ` Thorsten Wilms
2018-11-07 17:40 ` Thorsten Wilms
2018-11-09 16:37 ` Ludovic Courtès
2018-11-09 18:27 ` Thorsten Wilms
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=90787542-4e51-ac0e-5c8c-bef10e61ab3c@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.