On Fri, 16 Aug 2013, Guillem Jover wrote:
The same will apply when building that deb package multiple times, the
timestamps will change for the ar headers. And I don't really want to
lose that data, because currently is the only place were the build time
information is recorded. Do you only care that the members themselves
are deterministic or the whole deb package?
I think I'd be fine with not storing the timestamps in the compressed
members themselves, but not about the ar container.
Thanks for the speedy replies! I'm excited and pleased by your
responsiveness to the general ideas and specific issues.
I would prefer to keep even the 'ar' container free of those timestamps,
but there are some workarounds I can imagine if you don't want to do that
for now.
We could perhaps let 'dpkg' accept an argument to set that timestamp,
and/or we could use 'faketime' when trying to reproduce a build, if we
know what timestamp to reproduce. (My notion here is that it should be
easy for someone to create the same bits that we publish in Debian, even
if that reproducing effort is slightly different than just doing a fresh
build.)
Another way that we could do it is to store the last debian/changelog
timestamp in the ar header. That would be my favorite approach.
-- Asheesh.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
