On Monday, 27 March 2017 19:07:06 CEST Guido Günther wrote: > So either the builder > is messing things up here or something else (package import or copy to a > temporary build place) is messing things up in the source resulting in > bad timestamps in the binary package.
Yes. You're right, Turns out that pristine-tar is setting the timestamp of all files [1] when creating a tarball. The code that tweak timestamp has been present since 2007. I'm beginning to wonder if that's should be considered as a bug or a feature. I'll check with Perl6 upstream what can be done to avoid relying on timestamp to trigger module rebuild. I'll close this bug. Thanks the the help All the best [1] see all calls to utime around there: https://anonscm.debian.org/git/collab-maint/pristine-tar.git/tree/pristine-tar#n368 -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
