Bug#1136160: debian-policy: Clarify that Multi-Arch is not applicable for udebs

--Z8hMZBL2kxu0RiFH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, May 23, 2026 at 04:29:50PM +0530, Nilesh Patra wrote:
> I have attached 2 patches, please choose the one that sounds best :)
>=20
> Please take a look and let me know if this work. Otherwise please
> also tell me if further changes are required.

The perfect is the enemy of the good and both versions really are
sensible to me. I see there are different preferences, but both are
strictly better than the status quo.

> diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
> index 69467c4..03b1c29 100644
> --- a/policy/ch-controlfields.rst
> +++ b/policy/ch-controlfields.rst
> @@ -1381,8 +1381,10 @@ A Debian installation can combine packages from mu=
ltiple 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 should not be added to the binary package
> +sections for udebs because it does not apply to them.
> +The permitted field values are ``no`` (default), ``foreign``, ``same`` a=
nd
>  ``allowed``. Their semantics are described in the following sections.
> =20
>  .. _s-f-Multi-Arch-no:

I second this version. I recognize Guillem's concern, but that does not
lead me to rejecting this version.

> diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
> index 69467c4..124ea96 100644
> --- a/policy/ch-controlfields.rst
> +++ b/policy/ch-controlfields.rst
> @@ -1381,8 +1381,9 @@ A Debian installation can combine packages from mul=
tiple 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 apply to udebs and should be omitted.
> +The permitted field values are ``no`` (default), ``foreign``, ``same`` a=
nd
>  ``allowed``. Their semantics are described in the following sections.
> =20
>  .. _s-f-Multi-Arch-no:

I also second this version. I suggest s/ Multi-Arch / ``Multi-Arch`` /,
but that is a formatting-only change and does not affect seconds.

Helmut

--Z8hMZBL2kxu0RiFH
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

wsG7BAABCgBvBYJqOrx0CRAtGqrPJEREQkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmcP+8ZXIWe4vAQzTRJNfJesGO1a+nXTmTZzl0io98FI
TRYhBEzC0tkKjRZU2/hzqi0aqs8kRERCAADIXA/9FLs7Clb7GO+QNpTSEvULEGli
ngyGPDFgr4LPHtIUVk6dN/aKWN3Rbt+hBkzkdcPTkCWLKgdTgNGb3jl3Ezs1hNH3
AWQ/zTJQoh8kx9N3tETtmO1OS8xdVjBD6aosfeZCik4waG9y9AkLoffVsolgZI2O
0QLUkSTXd99/CE0c0WhAMhcZlBo9n4xcwFZ5YxipZ6pSqNxAllVgLKwEnBh3boxM
+58ECZ7n6ycjJUK5KhuDDIW554I9GY8SHxmnvw+Qmu76+DBXioakwS6HPCcBDpZa
SQYn+HEMvxOcHqgu6ppX+rIvcOs6jmVmBIQep92pMbfXxi/ta7SUmGhyoTmDPRmX
fHP69OmiOdg8YGOLfg0KqB6uZRRlvr9/aBZmVFtzuJ566EAW4TLukocVJa0zc+ZM
AYQvPn5pZxJIteqxguumsmnKJrPkXptMsOanDrKCxRmP9/3m7LjwZhpbHz5PkcON
MH+26g3CfP1D3rGpOR1yTvl5UXUqW4YA9MT6Y/BeC5O5Vuy2EtwUjrylw9D9rAve
PYuRs0IzzggIIMUGdHyXgyhPHqCb58B6KoC1sV+ZYIQ8zYkADZ9Xlotiacb/gJLI
M29RP8kHO9o9yVpZWSFqZddC/R5DtMbzpZh+1mU6ZQF7iBSae1XkVBW4HdGzIbuB
jE8+Z1Pa05V1w+6nFIk=
=WQJ7
-----END PGP SIGNATURE-----

--Z8hMZBL2kxu0RiFH--