Source: rakudo Version: 2024.09-4 Severity: normal Tags: patch X-Debbugs-Cc: [email protected] User: [email protected] Usertags: randomness
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
0001-Use-SOURCE_DATE_EPOCH-fore-metadata-to-make-it-repro.patch
Description: application/mbox
