From: vapnik spaknik via <help-guix@gnu.org>
To: help-guix@gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: Re: profile symlink structure
Date: Mon, 25 May 2020 22:04:34 +0000 (UTC) [thread overview]
Message-ID: <954956541.4643876.1590444274695@mail.yahoo.com> (raw)
In-Reply-To: <87lflgphk4.fsf@ambrevar.xyz>
> On Monday, May 25, 2020, 09:03:44 AM GMT+1, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> The symlinking operations should be atomic, thus this can not happen.
> I suspect that your error is due to calling `sudo guix pull`.
> Cheers!
Another question; what is the purpose of the *.lock files in the symlink directories exactly, and how are they used?
I guess it has something to do with atomic transactions, but the .lock files appear to be untouched after several updates as the modification times are unchanged.
--
prev parent reply other threads:[~2020-05-25 22:04 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
2020-05-25 17:14 ` vapnik spaknik via
2020-05-26 7:22 ` Pierre Neidhardt
2020-05-25 22:04 ` vapnik spaknik via [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=954956541.4643876.1590444274695@mail.yahoo.com \
--to=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
--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).