Hi! On Wed, 2026-05-13 at 17:49:29 +0530, Nilesh Patra wrote: > On 10/05/26 8:46 pm, Helmut Grohne wrote: > > I am hesitant to second the "must not" precisely for those font > > packages. > > Attached another patch, with wording changed a bit; as M-A is relevant only > for binary package > stanza (and S-V makes it to only source package stanza which would be sort of > inherited). > Please see if this is good enough.
While the change does not look wrong, I'm not sure there's a need to mention that this applies to binary package stanzas, as that should be clear from the previous sentence? (Also just in case, and to clarify, neither Standards-Version nor Multi-Arch fields get inherited.) > diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst > index 69467c4..92d4dbe 100644 > --- a/policy/ch-controlfields.rst > +++ b/policy/ch-controlfields.rst > @@ -1381,8 +1381,9 @@ A Debian installation can combine packages from > multiple architectures. > The ``Multi-Arch`` field enables individual packages to declare their > support for this feature, and influences the way dependencies are > handled. It can be declared in binary package sections of a source > -package template control file and in binary package control files. The > -permitted field values are ``no`` (default), ``foreign``, ``same`` and > +package template control file and in binary package control files. > +Binary package stanzas for udebs do not make use of ``Multi-Arch``. > +The permitted field values are ``no`` (default), ``foreign``, ``same`` and > ``allowed``. Their semantics are described in the following sections. > > .. _s-f-Multi-Arch-no: Maybe just say that for udeb packages the field is not useful/used/taken-into-account/in-scope? Which should cover not only debian/control but also DEBIAN/control (for example via «dpkg-gencontrol -DMulti-Arch»)? Thanks, Guillem
