From: "Ludovic Courtès" <ludo@gnu.org>
To: Felix Lechner <felix.lechner@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: A corner case of broken reproducibility
Date: Mon, 30 May 2022 17:58:06 +0200 [thread overview]
Message-ID: <87leuj108h.fsf@gnu.org> (raw)
In-Reply-To: <CAFHYt56+2DKg8oJ75LmEu+eBTXsuRbt1LpFmZfT6uex-5U+XCA@mail.gmail.com> (Felix Lechner's message of "Wed, 25 May 2022 04:35:00 -0700")
Hi,
Felix Lechner <felix.lechner@gmail.com> skribis:
> On Tue, May 24, 2022 at 11:42 PM Blake Shaw <blake@sweatshoppe.org> wrote:
>>
>> I changed my user name in my config without adding a new user
>
> I did that once in a new installation. In the second generation of my
> configuration I changed the example user 'bob' to my own username. It
> did not work well.
>
> Due to precautions I was able to go back in as the root user and
> adjust the permissions. The only unexpected part was that the symbolic
> links for per-user profiles encode the relationship between user name
> and uid.
Yes, this part is inherently stateful: Guix will not meddle with your
home directories and such.
Perhaps it should forcefully “chown -R” home directories at boot time,
so they have the right UID? This has been discussed a few times,
especially in the context of system accounts; systemd-homed appears to
be doing exactly that.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-05-30 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 6:10 A corner case of broken reproducibility Blake Shaw
2022-05-25 11:35 ` Felix Lechner
2022-05-30 15:58 ` Ludovic Courtès [this message]
2022-05-30 20:50 ` Maxime Devos
2022-06-01 16:38 ` Ludovic Courtès
2022-06-01 19:59 ` Maxime Devos
2022-06-02 14:13 ` Ludovic Courtès
2022-06-02 14:43 ` Maxime Devos
2022-06-01 20:09 ` Maxime Devos
2022-06-01 20:41 ` raingloom
2022-06-01 21:50 ` Maxime Devos
2022-06-02 14:08 ` Ludovic Courtès
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=87leuj108h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=felix.lechner@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).