Hi Helmut, > dh_strip_nondeterminism -a > Using 1579457206 as canonical time […] > dh_strip_nondeterminism -a > Using 1579456117 as canonical time […] > This could affect any Multi-Arch: same package that is being binNMUed.
I can't seem to summon enough braincells this second to work out the right solution but whilst I see this I *think* this has been discussed a little before (likely with no resolution). Ah yes, here we go perhaps: https://bugs.debian.org/894441 Again, just linking whilst I remember it so we are aware of past thoughts. > I think the only sane solution to this problem is having > dh_strip_nondeterminism skip binNMU changelog entries when generating > the timestamp. (This seems... suboptimal? I mean, not just because it's kinda ugly but other parts of a Debian build could be using a different SOURCE_DATE_EPOCH they obtained via some other means...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-