Hi! On Thu, 2026-05-14 at 18:18:36 +0530, Nilesh Patra wrote: > On 14/05/26 9:13 am, Guillem Jover wrote: > > On Wed, 2026-05-13 at 17:49:29 +0530, Nilesh Patra wrote: > >> On 10/05/26 8:46 pm, Helmut Grohne wrote: > > (Also just in case, and to clarify, > > neither Standards-Version nor Multi-Arch fields get inherited.) > > That makes sense, since S-V is not a binary package stanza field, I suppose > nothing to "inherit" here. I was clear about M-A, though. > I did not think clearly before saying otherwise - apologies.
No worries, and nothing to apologize for! > >> 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»)? > > I've tried to re-word it with something else, then :) > Please take a look and see if this is more sensible. > diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst > index 69467c4..0f5933c 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. > +The ``Multi-Arch`` field does not affect udebs. > +The permitted field values are ``no`` (default), ``foreign``, ``same`` and > ``allowed``. Their semantics are described in the following sections. > > .. _s-f-Multi-Arch-no: I think this is better than the previous iterations, but it feels a bit vague, because it describes the effect that Multi-Arch has, which then makes not using them implied. Perhaps better to be more explicit about it? What about something along the lines of? "The Multi-Arch field is not relevant for udebs, and should thus not be used on them." Although I feel there's something cumbersome about that phrasing, so probably a better wording can be found. Thanks, Guillem
