News for hackers. Stuff that matters.
Re:Debian bookworm live images now reproducible by fmbb on Wednesday March 26, 2025 @03:03PM (#43485670)
Toolchains for reproducible software likely let you set these values, or ensure they are 1970-01-01 00:00:00
Re:Debian bookworm live images now reproducible by mikepurvis on Wednesday March 26, 2025 @03:34PM (#43486128)
Nix sets everything to the epoch, although I believe Debian's approach is to just use the date of the newest file in the dsc tarballs.
Re:Debian bookworm live images now reproducible by yjftsjthsd-h on Wednesday March 26, 2025 @06:28PM (#43488193)
Nix can also set it to things other than 0; I think my favorite is to set it by the time of the commit from which you're building.
Re:Debian bookworm live images now reproducible by terinjokes on Thursday March 27, 2025 @07:27AM (#43492466)
Which is also used when the contents of a derivation will be included in a zip file. The Unix epoch is about a decade older than the zip epoch.
Re:Debian bookworm live images now reproducible by lamby on Thursday March 27, 2025 @06:56AM (#43492243)
Debian's approach is actually to use the date specified in the top entry in the debian/changelog file. That's more transparent and resilient than any mtime.
Re:Debian bookworm live images now reproducible by lamby on Thursday March 27, 2025 @06:58AM (#43492261)
Strangely enough, sometimes using the epoch can expose bugs in libraries (etc.) when running or building in a timezone west of Greenwich due to the negative time offset taking time "below" zero.