From: Pierre Neidhardt <mail@ambrevar.xyz>
To: vapnik spaknik <vapniks@yahoo.com>, help-guix@gnu.org
Subject: Re: profile symlink structure
Date: Mon, 25 May 2020 10:03:39 +0200 [thread overview]
Message-ID: <87lflgphk4.fsf@ambrevar.xyz> (raw)
In-Reply-To: <981904032.4122292.1590333823170@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
vapnik spaknik <vapniks@yahoo.com> writes:
> Could this be due to running "sudo guix pull" or "sudo -i guix pull"?
Did you run `sudo guix pull`? If so, you should probably not! :)
> Also, what determines which profile symlinks are placed in /var/guix/gcroots/auto? I read elsewhere that these symlinks will be automatically removed as soon as any of them are broken.
See my other email. `guix package --profile=...` is one of the
commands that creates auto GC roots.
> In my case that directory only contains symlinks to /var/guix/profiles/per-user/*/current-guix* symlinks, one of which is missing (/var/guix/profiles/per-user/root/current-guix-1-link), and there is another link to ~/.config/guix/current-1-link which itself links directly to a profile in /gnu/store
>
> I suspect that the previously mentioned anomalies are the reason why "guix pull" fails for me with the following error when run as <USR>:
>
>> guix pull: error: symlink: File exists: "/var/guix/profiles/per-user/<USR>/current-guix-1-link"
>
> and which may have been caused by interrupting a "guix pull".
The symlinking operations should be atomic, thus this can not happen.
I suspect that your error is due to calling `sudo guix pull`.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-25 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <981904032.4122292.1590333823170.ref@mail.yahoo.com>
2020-05-24 15:23 ` profile symlink structure vapnik spaknik
2020-05-25 8:03 ` Pierre Neidhardt [this message]
2020-05-25 17:14 ` vapnik spaknik via
2020-05-26 7:22 ` Pierre Neidhardt
2020-05-25 22:04 ` vapnik spaknik via
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=87lflgphk4.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=vapniks@yahoo.com \
/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).