Proposal for making Multi-Arch:same binNMU-safe
Johannes Schauer Marin Rodrigues
josch at debian.org
Wed Apr 15 12:08:20 BST 2026
Quoting Helmut Grohne (2026-04-15 11:49:42)
> From here we leave the wanna-build source code and continue in sbuild. It
> already has --binNMU-timestamp and all that the buildd code would have to do
> here is check for the newly added field and pass it along using the new
> option. When the field is not provided, the option is skipped. Thus, this
> change would also be backwards compatible.
>
> [snip]
>
> sbuild team:
> * Would you be ok with the projected changes?
I do not see what change in sbuild would be required. As you pointed out, you
can already pass it the timestamp. What else would be needed? There is also
--binNMU-changelog which can be passed to completely control the changelog
entry without sbuild messing up anything.
We talked about this topic in the context of https://bugs.debian.org/843773
which also triggered the addition to --binNMU-changelog in sbuild.
Thanks!
cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20260415/0b68e271/attachment.sig>
More information about the Reproducible-builds
mailing list