If preferred, a variant of the proposed changes with a default of "no" would
also be possible

I think the default (for bin packages) should be not to generate a multi-arch:
field at all.

This is behaviorally equivalent to multi-arch: no, but it IMO has different
implications, it implies "noone has thought about multi-arch for this package"
rather than "sometime has thought about multi-arch for this package and
rejected it"

Reply via email to