On 28/01/17 20:42, Carsten Schoenert wrote: > then I don't understand your first email.
Do I need to clarify more or did my follow-up mail already do that? > So I have currently no clue where the timestamps with *.000000000 are > coming from. Maybe I'm nitpicking, maybe I'm pointing out something relevant. I think all files in a .deb binary package have a 0 fractional seconds part. I think they are stored with one second resolution. But the problematic files have a fake mtime of 2010-01-01 0:00 UTC that is the same over different .deb binary packages. > But this looks like something that could be come from the > tools the reproducibly team is using and creating. That does sound like a clue! > Next we need to clarify with which package version such timestamps are > shipped for the first time. Done! Using my backups, I could trivially deduce which stable package introduced the change. In 38.8.0-1~deb8u1, the times are still recent. In 1:45.1.0-1~deb8u1, the 2010-01-01 times show up. Next using snapshot.debian.org[1], using a manual binary search through the .deb files, I could pinpoint that 41.0~b2-1 is the first version where the 2010-01-01 times show up. The one before that, 40.0~b1-1, still has recent mtimes. HTH, Peter. [1] http://snapshot.debian.org/package/icedove/ -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>
