From: Gabriel Wicki <gabriel@erlikon.ch>
To: help-guix@gnu.org
Subject: Re: `guix pull` fails after fresh install
Date: Fri, 20 Aug 2021 01:00:56 +0200 [thread overview]
Message-ID: <20210819230056.qxvniv7vmg4lgb3u@silvi> (raw)
In-Reply-To: <20210819225650.c7oswgzt7uov7kmv@silvi>
Please ignore my previous message in this thread, i sent the wrong
version... Here's the right one:
I was able to fix it! Yay
Because this mailing list is a resource for people seeking help I'll
hereby take the liberty to document how I tracked the issue down and
fixed it.
I added a new user to find out if the problem was reproducible and
whether the system was to blame. This was luckily not the case.
`guix pull` worked for the freshly added user 'test'. But I found
the following differences: both
/var/guix/profiles/per-user/user/current-guix
and
/home/user/.config/guix/current
were real directories, whereas for the new 'test' user at the
corresponding paths there were symlinks: the former pointing to
current-guix-1-link in the same directory while the latter pointed to
the former. Also, there is no file called `current-guix-0-link` in
/var/guix/profiles/per-user/user/, but `current-guix` in the same
directory points to that. I guessed this was most probably causing
the issue.
If I understand correctly guix stores two kinds of of symlinks in
user-profiles (which live in /var/guix/profiles/per-user/):
1. current-guix-N-link: links to guix profiles (which contain guix
and guix-daemon executables and info files),
2. guix-profile-N-link: links to package profile generations
(which contain all installed programs including libraries,
executables and documentation)
and for each of those link-types one special link (current-guix and
guix-profile) pointing to the currently active one of their kind.
My guix-profile links seemed to be fine, but my suspicion grew that
I'd have to replace the aforementioned directories with symlinks to
the right places. Only problem: I did't know which is the "right"
current-guix profile to link to. But since my installation is just
some days old I figured there shouldn't be too much of a difference
between the different guix versions on my machine and just linked to
the one which
/var/guix/profiles/per-user/test/current-guix-0-link
pointed to.
I tested with `guix pull` which worked just fine. Pleased with the
outcome I happily `guix package upgrade`d my profile.
prev parent reply other threads:[~2021-08-19 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 21:13 `guix pull` fails after fresh install Gabriel Wicki
2021-08-19 22:56 ` Gabriel Wicki
2021-08-19 23:00 ` Gabriel Wicki [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210819230056.qxvniv7vmg4lgb3u@silvi \
--to=gabriel@erlikon.ch \
--cc=help-guix@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).