On 2020-12-31, Debian Bug Tracking System wrote: > fop (1:2.5-3) unstable; urgency=medium > . > * Team upload > * Update SOURCE_DATE_EPOCH patch (Closes: #978499) > - Conditionally use SOURCE_DATA_EPOCH in PDFInfo, PDFMetadata, > PDFRenderingUtil, and FileIDGenerator classes. > - Add try/catch logic for unparsable SOURCE_DATE_EPOCH
Thanks for the follow-up! It seems so very, very close, xorg-docs now is only varying on the timezone, but otherwise respecting SOURCE_DATE_EPOCH: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/xorg-docs.html But what really confuses me is that "treeview" is still ignoring SOURCE_DATE_EPOCH entirely (e.g. timestamps showing up from 2022): https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/treeview.html From the output, it looks like both packages are embedding the same type of values... I confirmed that both builds actually were using fop version 2.5-3, according to the build logs. Almost makes me wonder if treeview somehow has an invalid date in the changelog entry... live well, vagrant
signature.asc
Description: PGP signature
