From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Felix Lechner <felix.lechner@gmail.com>, Guix Devel <guix-devel@gnu.org>
Subject: Re: A corner case of broken reproducibility
Date: Thu, 02 Jun 2022 16:43:26 +0200 [thread overview]
Message-ID: <e920a323c69036fe6f3d937bcd2a2a284e704f34.camel@telenet.be> (raw)
In-Reply-To: <87ilpjnofu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Ludovic Courtès schreef op do 02-06-2022 om 16:13 [+0200]:
> I’m not sure what the conclusion of those bug reports were, but (gnu
> build accounts) doesn’t reuse UIDs: you can see that in
> ‘user+group-databases’, which reads the initial /etc/{passwd,group}, and
> passes them to ‘allocate-passwd’ and ‘allocate-group’, which “reserve”
> those initial UIDs/GIDs.
>
> This is exercised in tests/accounts.scm (search for “no reuse”).
Right, I guess I misremembered or misinterpreted the bug reports.
Or someone added and removed an account 900 times.
> There could be bugs of course, but in that case we should fix them. :-)
So in theory there might still be a bug (or at least a limitation), albeit
unlikely to encounter in practice.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-02 14:44 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
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 [this message]
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=e920a323c69036fe6f3d937bcd2a2a284e704f34.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=felix.lechner@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).