Proposal for making Multi-Arch:same binNMU-safe

[Adrian Bunk]

On Wed, Apr 15, 2026 at 04:34:19PM +0200, Helmut Grohne wrote:
>...
> On Wed, Apr 15, 2026 at 04:05:27PM +0200, Simon Josefsson wrote:
> > Couldn't we use the timestamp of the last source upload instead?
> >
> > That is, whatever code set SOURCE_DATE_EPOCH based on debian/changelog
> > timestamps has to be modified.  Instead of using the timestamp of the
> > most recent entry, have it skip over all binNMU entries to find the
> > timestamp of the most recent non-binNMU entry.
> 
> That's an earlier solution. It was discarded, because it broke Ian's
> backup system. With that scheme, a binNMU could change a file and retain
> is modification time. This breaks the principle of least surprise.
>...

AFAIR I already suggested somewhere in these discussions that the date 
of a binNMU could be the date of the source upload plus the binNMU 
number added in seconds (e.g. +b5 is 5 seconds after the source upload).

> Helmut

cu
Adrian