On 2022-02-12, Felix Zielcke wrote: > Am Freitag, dem 11.02.2022 um 22:46 +0100 schrieb Thomas Schmitt: >> Chris Lamb wrote: >> > Did you try the --invariant flag? >> >> Well, i step aside and let this question reach Felix. :)) >> >> https://manpages.debian.org/unstable/dosfstools/mkdosfs.8.en.html >> says that this is what we need if my theory about the second >> difference >> is correct: >> >> --invariant >> Use constants for normally randomly generated or time based data >> such as volume ID and creation time. Multiple runs of mkfs.fat on >> the same device create identical results with this option. >> >> >> So the options to be added to the mkdosfs runs in the hope for a >> fully >> reproducible ISO are: >> >> -i 12345678 --invariant >> >> If a more more individual -i number is desired, one could use >> something >> like >> >> -i $(printf '%8.8x' "$SOURCE_DATE_EPOCH" | head -c 8) >> >> > > Wow. Thanks very much to you both. > This is the solution. I would never come up that fast with it.
I noticed 1.5-3 is still affected by timezone differences, but is very
nearly there!
Figured out using:
reprotest --auto-build --store-dir=$(mktemp -d ${HOME}/rb-test-XXXXXX)
--min-cpus=1 --vary=-user_group,-domain_host,-fileordering auto -- null
Which does a build for each different tested variation. Some variations
are trickier to set up with the null backend, so I just disable
them. The store-dir argument allows you to see all the various
diffoscope outputs and build artifacts.
If I come up with an updated patch, I'll maybe submit a new bug...
live well,
vagrant
signature.asc
Description: PGP signature
