From: Phil Blundell <pb@pbcl.net>
To: Patrick Ohly <patrick.ohly@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] rootfs-postcommands.bbclass: sort passwd entries
Date: Fri, 06 Jan 2017 21:17:27 +0000 [thread overview]
Message-ID: <1483737447.4360.180.camel@pbcl.net> (raw)
In-Reply-To: <1483630732-3560-1-git-send-email-patrick.ohly@intel.com>
On Thu, 2017-01-05 at 16:38 +0100, Patrick Ohly wrote:
> The /etc passwd files in a rootfs consist of the default entries from
> base-passwd plus anything that gets added by preinst scripts or
> extrausers.bbclass.
>
> The execution order of preinst scripts is not perfectly
> deterministic,
> or at least unrelated changes caused it to change in a
> non-deterministic way, resulting in irrelevant changes in the order
> of
> passwd entries.
>
> Such re-ordering is bad for reproducible builds and file-based update
> mechanisms like swupd which work best if changes are as minimal as
> possible.
>
> To achieve that, the files get sorted in a post-processing command,
> enabled by default.
Won't the numeric UIDs still be non-deterministic, though? If the goal
is reproducible builds then it doesn't sound as though this quite fixes
the problem.
p.
next prev parent reply other threads:[~2017-01-06 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 15:38 [PATCH 1/1] rootfs-postcommands.bbclass: sort passwd entries Patrick Ohly
2017-01-06 21:17 ` Phil Blundell [this message]
2017-01-07 8:06 ` Patrick Ohly
2017-01-07 9:59 ` Phil Blundell
2017-01-07 19:00 ` Patrick Ohly
2017-01-07 22:52 ` Richard Purdie
2017-01-08 9:36 ` Phil Blundell
2017-01-08 14:04 ` Patrick Ohly
2017-01-09 10:09 ` [PATCH V2 " Patrick Ohly
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1483737447.4360.180.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.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