Package: reprotest Followup-For: Bug #1093412 X-Debbugs-Cc: ijack...@chiark.greenend.org.uk
On Sun, 19 Jan 2025 16:26:27 +0000, I wrote: > The timestamps on files that are simply copied from the src package > into the binary package appear to have 331 hours _subtracted_ from > their original mtime values. My mistake; in fact they have had 662 (331*2) hours subtracted. Furthermore: performing a copy operation on a file from the source when using faketime in debian:unstable appears to reduce the mtime of the file by the delta duration each time a copy operation occurs: $ stat -c '%y' reprotest-0.7.29/reprotest/utils.py 2023-02-26 22:10:37.000000000 +0000 $ NO_FAKE_STAT=1 faketime '+331hours' cp -a reprotest-0.7.29/reprotest/utils.py . $ stat -c '%y' utils.py 2023-02-13 03:10:37.000000000 +0000 $ NO_FAKE_STAT=1 faketime '+331hours' cp -a utils.py utils2.py $ stat -c '%y' utils2.py 2023-01-30 08:10:37.000000000 +0000 That does _not_ occur in Debian testing; the file retains the original mtime: $ stat -c '%y' reprotest-0.7.29/reprotest/utils.py 2023-02-26 22:10:37.000000000 +0000 $ NO_FAKE_STAT=1 faketime '+331hours' cp -a reprotest-0.7.29/reprotest/utils.py . $ stat -c '%y' utils.py 2023-02-26 22:10:37.000000000 +0000 $ NO_FAKE_STAT=1 faketime '+331hours' cp -a utils.py utils2.py $ stat -c '%y' utils2.py 2023-02-26 22:10:37.000000000 +0000
