SOURCE_DATE_EPOCH and timezone with FAT images

Daniel Shahaf danielsh at
Wed Feb 23 17:09:07 UTC 2022

Bernhard M. Wiedemann wrote on Wed, 23 Feb 2022 16:35 +00:00:
> The most practical approach is to add to the build scripts
> export TZ=UTC
> (or UTC0)
> If it is a regional project, hardcoding that local timezone would also
> yield reproducible results.

Note that if you go down this road, you need to ensure the builder and
rebuilder have the same idea of when DST starts/ends, how many leap
seconds there have been, etc., otherwise there could be off-by-one
differences when trying to reproduce the timestamps.

I was going to say that's not very likely to happen in practice, but
according to tzdata 2021d Fiji cancelled DST entirely for 2021/2022,
so there have been around six months during which treating tzdata as
an implicit dependency could cause differences.

At any rate, +1 to using UTC if possible.



> What is that "additional complexity" you speak of?
> Ciao
> Bernhard M.
> Attachments:
> * OpenPGP_signature

More information about the rb-general mailing list