On Friday, 31 March 2017 20:44:57 CEST Tomasz Buchert wrote: > I fail to see that pristine-tar is (or even can be) at fault here. > Pristine-tar knows nothing about debian/changelog file so it cannot > set modification times to last changelog entry. In fact, the only > thing that pristine-tar cares about is recreating tarballs that were > fed into it.
Sorry, I got confused while comparing time stamps between repos and tarballs. I've checked with rakudo 2017.03 that the timestamps of the pristine tarball do match the timestamp of uptream tarball (freshly downloaded from upstream). Sorry for the noise -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
