Proposal for making Multi-Arch:same binNMU-safe

[Simon Josefsson]

Helmut Grohne <helmut at subdivi.de> writes:

> Proposed solution
> =================
>
> Use the timestamp of when the binNMU was requested in the binNMU
> changelog.

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.

Setting SOURCE_DATE_EPOCH to the binary build date seems strange to me,
even if you were to force it to be identical for all binNMU archs.

This approach also solves partial binNMU: sometimes there is no point in
scheduling a binNMU for all architectures, but only for a particular
one.  With my approach, the SOURCE_DATE_EPOCH value will be the same for
these partiaul binNMU's, but with your approach it will differ from the
earlier non-binNMU SOURCE_DATE_EPOCH value.

/Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1251 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20260415/757dfaf8/attachment.sig>