Hi,

Rakudo captures the file timestamp into the metadata when compiling
modules. This is normally fine except fore files that are touched by
debian/patches. Examples:

https://reproduce.debian.net/all/api/v1/builds/176802/artifacts/336780/diffoscope
https://reproduce.debian.net/all/api/v1/builds/180915/artifacts/344761/diffoscope
https://reproduce.debian.net/all/api/v1/builds/180660/artifacts/344452/diffoscope
https://reproduce.debian.net/all/api/v1/builds/177031/artifacts/337508/diffoscope


dpkg can't clamp the timestamp to a specific date as that could break
make, so instead I propose to use $SOURCE_DATE_EPOCH in the metadata
instead. The attached patch implements this.

Once this or an equivalent patch is applied, these packages need at
least a no change upload to get fixed as they are arch:all and can't be
binNMUed:  raku-readline, raku-license-spdx, raku-hash-merge, raku-log.

Note that there is already #1002496 discussing broader changes. As this
seems to be the only problem affecting reproduce.debian.net I opened a
new bug.

Cheers Jochen

* Jochen Sprickerhof <jspricke@debian.org> [2026-07-13 17:22]:

Guillem proposed to only clamp newer timestamps, alternative patch
attached.

Obviously there is a third option to drop the time entry as it seems to
be optionsl. I don't know how it is used, so I leave the decision to the
maintainer.

Cheers Jochen