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:btrfs-progs

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
81	python3-sphinx-rtd-theme:armhf
12	sphinx:armhf

Conflict

# of packages per conflict	Conflict
1	libreiserfscore0t64: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
81	81	src:bioxtasraw src:btrfs-progs src:cglm src:charliecloud src:condor src:coreboot (ITA: #1055811) src:cumin src:dbus-fast src:dm-tree src:enlighten src:fastchunking (1022959) src:fastd src:gdspy (1023190) src:gnunet (O: #1070305) src:grpc src:h5z-zfp src:harp src:intake src:isc-kea (1080444) src:kiwi src:knot-resolver src:libcifpp src:libiio src:libxeddsa src:luma.core src:m2crypto src:macsyfinder src:mupdf src:ntopng src:numba src:opendrop src:openmpi src:peewee src:pgloader src:pikepdf src:pmix src:poezio src:powerline src:psd-tools src:py-stringmatching src:pycairo (1087293) src:pycares (O: #1074758) src:pycryptodome src:pyepr src:pyftdi src:pyogrio src:pyotherside src:pypy3 src:pyregion src:pyresample src:pyside2 src:pysph src:pytables src:python-biopython src:python-btrees src:python-coverage src:python-evdev src:python-freesasa src:python-gmpy2 src:python-levenshtein (ITA: #1065327) src:python-nh3 src:python-persistent src:python-pkcs11 src:python-sdbus src:python-tornado src:python-wrapt src:pyvkfft src:pywayland src:renpy src:restic src:salmon src:sfepy src:splash src:tombo src:toulbar2 src:tpm2-pytss src:ufo-core src:verilator src:wireplumber src:xrayutilities src:xsimd	(*) →	python3-sphinx-rtd-theme:armhf
12	12	src:btrfs-progs src:eln src:fio src:gappa src:libecpint src:luma.emulator src:numba src:py-stringmatching src:pygrib src:receptor src:smbus2 src:tiff (1086689)	(*) →	sphinx: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:libguestfs	(*) → btrfs-progs → libreiserfscore0t64 →	(*) → reiserfsprogs → libreiserfscore0t64	libreiserfscore0t64: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.