Below are two tables showing the two problem classes that prevent cross compilation on the dependency level. This example tries to satisfy the crossbuild dependencies of all source packages on amd64 as the build architecture for a dummy architecture generated from amd64 (called armhf here) as the host architecture in current Debian sid.

A machine parsable version can be retrieved in dose yaml format

Bugs are associated with packages on this page if they carry the usertag "cross-satisfiability" of the user "debian-cross@lists.debian.org".

You can get an overview of all bugs tagged like that in the Debian bts

Hover over a package name with your cursor for architecture and version information. Hovering over the arrows in the depchain columns will show the dependency that led from one package in the chain to the next.

src:mariadb-connector-python

Top 10 summary

The following is a summary of the full "missing" and "conflict" tables below. It only shows the first and last columns of the full tables and only displays the top 10 rows.

Missing

# of packages per missing	Unsatisfied dependency
70	python3-setuptools-scm:armhf
1	perl-base:armhf (= 5.40.0-7)
1	perlapi-5.40.0:armhf

Conflict

# of packages per conflict	Conflict
1	perl:amd64

missing

The packages in the third column cannot satisfy their (possibly transitive) dependencies because of the unsatisfied dependency in the last column. This is mostly because the binary package providing the dependency in the last column is Multi-Arch:no. Some of these packages need to be Multi-Arch:foreign instead. In some other cases, Build-Depends can be annotated with :native. The depchains column shows the dependency chain(s) from the packages in the third column to the unsatisfied dependency in the last column. The "(*)" placeholder in the depchains column represents any package in the third column. Hovering over the arrows in the depchains column with your cursor will show the dependency that led from one package in the chain to the next.

The output is first grouped by the shared unsatisfied dependency (last column) and then by shared dependency chain (fourth column). The groups are sorted by the number of packages missing the dependency in the last column. Within each group, the output is sorted by the number of packages sharing the same dependency chain.

# of packages per missing	# of packages per depchain	packages with missing (possibly transitive) dependencies	Depchains	Unsatisfied dependency
70	70	src:afdko src:astropy src:astropy-healpix src:astropy-regions src:astroscrappy src:atropos src:black src:blurhash-python src:borgbackup src:borgbackup2 src:brian src:casa-formats-io src:compreffor src:cumin src:device-tree-compiler src:duplicity src:extension-helpers src:fast-histogram src:gammapy src:healpy src:imexam src:kiwisolver src:mariadb-connector-python src:matplotlib src:numcodecs src:opm-common src:photutils src:pikepdf src:psautohint src:pybdsf src:pyclipper src:pyerfa src:pylibtiff src:pymad src:pymssql src:pyraf src:pyregion src:pysolid src:pysynphot src:python-bcj src:python-cartopy src:python-drizzle src:python-hmmlearn src:python-inflate64 src:python-leidenalg src:python-libcst src:python-lz4 src:python-maxminddb src:python-openstep-plist src:python-pkcs11 src:python-pyepics src:python-pyppmd src:python-schema-salad src:python-soxr src:python-tinyalign src:python-vispy src:python-wordcloud src:python-xmlsec src:rdiff-backup src:reproject src:scalene src:segyio src:specutils src:spglib src:synphot src:tpm2-pytss src:ujson src:urwid src:whipper src:xraylarch	(*) →	python3-setuptools-scm:armhf
1	1	src:mariadb-connector-python	(*) → mariadb-server → perl →	perl-base:armhf (= 5.40.0-7)
1	1	src:mariadb-connector-python	(*) → mariadb-server → libdbi-perl →	perlapi-5.40.0:armhf

conflict

The packages in the third column cannot satisfy their (possibly transitive) dependencies because the last package(s) in the first depchain have an unsatisfied conflict which is shown in the last column. The second depchain column shows the dependency chain(s) to the package which the last package(s) in the first depchain conflict with. Sometimes, multiple dependency chains sharing the same conflict exist. Hovering over the arrows in the depchains column with your cursor will show the dependency that led from one package in the chain to the next.

The output is first grouped by the shared conflicting dependency (last column) and then by the shared dependency chains (fourth and fifth column). The groups are sorted by the number of packages sharing the conflict in the last column. Within each group, the output is sorted by the number of packages sharing the same dependency chains.

# of packages per conflict	# of packages per depchain	packages with (possibly transitive) conflicting dependencies	Depchain 1	Depchain2	Conflict
1	1	src:mariadb-connector-python	(*) → debhelper → po-debconf (ITA: #986937) → perl →	(*) → mariadb-server → perl	perl:amd64

generated: 20241118T000000Z

The JSON data used to generate these pages was computed using botch, the bootstrap/build ordering tool chain. The source code of botch can be redistributed under the terms of the LGPL3+ with an OCaml linking exception. The source code can be retrieved from https://salsa.debian.org/debian-bootstrap-team/botch

The html pages were generated by code which can be retrieved from https://salsa.debian.org/debian-bootstrap-team/boott and which can be redistributed under the terms of the AGPL3+

For questions and bugreports please contact j [dot] schauer [at] email [dot] de.