Hi, I highly suspect this stems from packages' rules files supporting reproducible builds. The only way I see to solve this would be for the "reproducible builds" infrastructure to hard-wire new timestamps at release-time of a new package version. Also: this is not limited to rsync. Basically any tool relying on (mtime/file size) as a changed indicator is affected by this. Even if the tool in question relied on (mtime/file size/inode number), "changed checks" could be subverted in situations where changes are made to the file directly instead of writing a new file and moving it into place (thus retaining the inode number). Cheers Daniel
Attachment:
signature.asc
Description: OpenPGP digital signature