News for hackers. Stuff that matters.
Re:Apt: please make the moo reproducible by simias on Saturday December 31, 2016 @07:49AM (#13290808)
I don't really understand what in this feature makes the build non-reproducible. Judging by the patch it's the call to time(NULL) that seems to be problematic, but I don't understand why.
Re:Apt: please make the moo reproducible by kr7 on Saturday December 31, 2016 @08:41AM (#13290959)
The output of "apt-get moo" changes on special days (4/1, 12/25, 8/16, 11/7, 2/18). So if another program was using "apt-get moo" in its build script, the build would not be reproducible. With the patch, the SOURCE_DATE_EPOCH environment variable can be set to make "apt-get moo" deterministic.

I don't think anything actually uses "apt-get moo" in its build script.

This kind of patch makes more sense for build tools like "ar" (static library creator). By default, "ar" injects a timestamp into the output file, so the binary is different each build. But, use the "D" flag and "ar" becomes deterministic.

Re:Apt: please make the moo reproducible by rzzzt on Saturday December 31, 2016 @08:44AM (#13290969)
The time-dependent part can be seen here: https://github.com/Debian/apt/blob/master/apt-private/privat...
Re:Apt: please make the moo reproducible by kr7 on Saturday December 31, 2016 @08:45AM (#13290977)
Re:Apt: please make the moo reproducible by smcl on Saturday December 31, 2016 @08:16AM (#13290887)
Yeh I only skimmed the patch but I presumed "reproducable build" referred to the actual binary, and the patch addresses runtime behaviour. Guess I'm missing something.
Re:Apt: please make the moo reproducible by lamby on Saturday December 31, 2016 @07:57AM (#13290831)
It doesn't; it makes anyone using the output...
Re:Apt: please make the moo reproducible by karrotwaltz on Saturday December 31, 2016 @08:31AM (#13290932)
From what I can read in patch file, it seems to be doing something different on April fools day.