SOURCE_DATE_EPOCH and timezone with FAT images

Bernhard M. Wiedemann bernhardout at
Wed Feb 23 16:35:25 UTC 2022

On 23/02/2022 11.53, Thomas Schmitt wrote:

> When trying to convince programmers of the additional complexity it does
> not really help that
> says:
>   "At present, we do not have a proposal that includes anything
>    resembling a "time zone"."
> Although i agree that time representations are tricky, i think it is
> necessary to specify a rule for the special case where the timezone
> unavoidably influences the storage bytes of the reproducible software.

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.

What is that "additional complexity" you speak of?

Bernhard M.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the rb-general mailing list