Bug#749826: Documenting `Multi-Arch: foreign`

Sean Whitton <[email protected]> Sun, 29 Mar 2026 11:01:51 +0100

Newsgroups	gmane.linux.debian.devel.policy
Message-ID	<87y0jb3qeo.fsf__7141.08270346827$1774778619$gmane$org@melete.silentflame.com>

Guillem Jover <[email protected]> [26/Mar  6:19pm +01] wrote:
> Hi!
>
> On Tue, 2026-03-24 at 14:12:45 +0100, Helmut Grohne wrote:
>> diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
>> --- a/policy/ch-controlfields.rst
>> +++ b/policy/ch-controlfields.rst
>> @@ -1307,6 +1307,166 @@ This list is intentionally incomplete. You should consult the
>>  documentation of the tool or package in question for which keywords it
>>  defines and when they are needed.
>>
>> +.. _s-f-Multi-Arch:
>> +
>> +``Multi-Arch``
>> +~~~~~~~~~~~~~~
>> +
>> +A Debian installation can combine packages from multiple architectures.
>> +The ``Multi-Arch`` header 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 header values are ``no`` (default), ``foreign``, ``same`` and
>> +``allowed``. Their semantics are described in the following sections.
>
> This uses "header" instead of "field", which is a term that we do not
> use at all in the context of the deb822 format.

Fixed, thanks.

-- 
Sean Whitton

signature.asc (application/pgp-signature, 869 B)