Re: Bug#1132656: debian-policy: [multiarch] Please document dependency architecture qualifiers: foo:any, bar:native, baz:i386

Johannes Schauer Marin Rodrigues <[email protected]> Sat, 04 Apr 2026 13:12:10 +0200
Newsgroups gmane.linux.debian.apt.devel,gmane.linux.debian.devel.dpkg.general
Message-ID <177530113032.6415.15273007144684914094@localhost>
--===============7393925376652430742==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Hi,

Quoting Simon McVittie (2026-04-04 12:08:54)
> dpkg documents architecture qualifiers in its man pages, which could be=20
> used as a basis for this.
>=20
> deb-control(5) documents this for binary packages' dependency fields=20
> (Depends, Recommends etc.): a "real Debian architecture name" can appear =

> after the colon, and as a special case, foo:any is also allowed. I'm not =

> 100% sure what "real" means in this context: probably the intention is=20
> that a specific, concrete architecture name like foo:i386 is considered=20
> to be "real", but a wildcard like foo:any-i386 or foo:linux-any is not?
>=20
> deb-src-control(5) documents the same architecture qualifiers for=20
> Build-Depends etc. as for Depends, plus a second special case,=20
> foo:native, which is described as "will match the current build=20
> architecture if the package is not marked with Multi-Arch: foreign." I'm =

> not 100% sure whether this means that a B-D on something like=20
> bash:native will be treated as an unsatisfiable build-dependency in the=20
> case where bash *is* M-A: foreign (as in fact it is), or whether a B-D=20
> on bash:native is merely equivalent to a B-D on bash in that case. I=20
> would hope it's the latter - that seems like it would have more useful=20
> semantics, especially when packages were not initially marked=20
> Multi-Arch: foreign but could/should have been.

another source of existing documentation of this can be found here:

https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/tree/doc/spec/multiarch.t=
xt?h=3Dpu/doc-multiarch-spec

Especially the tables have been useful references for me in the past and th=
ey
essentially mirror the original Ubuntu documentation of this:

https://wiki.ubuntu.com/MultiarchCross#Build_Dependencies

Thanks!

cheers, josch
--===============7393925376652430742==
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Description: signature
Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

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

iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmnQ8gQACgkQ8sulx4+9
g+F5QRAAinsxBcdAqF02vfNQTmkDyC1UOXF/eUWBAdd88x6ElcKXu9uUCsScS9zB
fBspRzCLHd13I+JwGbGi+Ye4RYEQjYRUnKgwZtxdY8OsfW/t7EZywfHCf+KpkgeJ
hQWBzvp76tLcaatKZTdvBTnqbQtr9cVa8Oho01O3W+ZcvzocUzYeiUwmO+frgFHG
jgrxtnJR7GJu5nTNtpRkqsgBxuYlMLBqrK55ch8Ry9yVGbCqlcWI0+VujxABGRmP
N/Hj6YXTkCXORHCrSQidOV6/6PO0rZJE4JzwZrw9Sm9IBEceTDqunlAu/l6PVWF5
85XPe8rlKriouIZB+OQ48lw/pS4RXmfTubPP7QDJoBK6+g6CN+xo4biDLbU1sdhh
ObojjMtyxCy14e3o654ZvjDkZrqjIClzgcNvDrYTjcr1tC79xPxvoDOOPqPwEhAI
DeMhsJaOuQYnB+S7fr1B8zjLyofXF4lzgsBa1st7TN2HIEybxX4NOLSuGFYWmdYB
1RGPKeLhwgIWwpMaDe4YJQhi9APyOVVZDJxgXWHNQndLKNyz23USb7xsdRacEHwS
jLV6ol+PWOyl5/weWkhZDaZ8a6ZjPE0Skwu6gC/eKxi/DA6IjyxX9KrEJdob+AZ9
I5ovCU3rWNAKXlPwaLroHDx2IfiqDqCjgwFI3Jk575ZpdUm7ghY=
=ML6/
-----END PGP SIGNATURE-----

--===============7393925376652430742==--