Guillem Jover writes ("Re: misleading timestamps in binnmus"):
> I think this should be fine. There's also SOURCE_DATE_EPOCH, that
> dpkg-buildpackage honors and otherwise sets now, which can be also
> retrieved with «dpkg-parsechangelog -STimestamp», but that should not
> be needed here anyway, because…
>
> > AIUI a buildd doing a binnmu will not
> > modify the debian/changelog file.
>
> … the changelogs do get a new entry, otherwise everything would fall
> apart. Something like this:
I found in the relevant python package that there was a separate
changelog.amd64. But indeed:
> So the actual problem is that the last timestamp gets reused for the
> binNMUs, which seems totally bogus to me. This needs to be fixed in
> whatever is injecting the binNMU entries on the buildds.
The same is true for libpython2.7-stdlib.
I've dropped the reproducible-builds list and added
debian-wb-team@l.d.o in the hope that they may be able to point us in
the right direction.
Thanks,
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
