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:colorcet

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 missingUnsatisfied dependency
178python3-pytest:armhf
9python3-mock:armhf
2python3-pyct:armhf

Conflict

# of packages per conflictConflict
1python3-minimal:amd64
1python3.11-minimal:amd64
1python3.11:amd64
1python3:armhf

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 depchainpackages with missing (possibly transitive) dependenciesDepchainsUnsatisfied dependency
178 178src:ariba src:astropy-healpix src:astropy-regions src:aubio src:baler src:bcachefs-tools src:bup src:clamav src:codetiming src:colorcet src:cumin src:cvc5 src:cyvcf2 src:dart src:deap src:dm-tree src:dolfinx-mpc src:dumb-init src:dupeguru src:duplicity src:extension-helpers src:fast-histogram src:fenics-basix src:fpylll src:frozenlist src:gammapy src:gau2grid src:genx src:gfapy src:gpaw src:gpiozero src:gromacs src:gudhi src:healpy src:herbstluftwm src:hyperspy src:imexam src:intake src:iva src:khmer src:kiwi src:libei src:libpillowfight src:libsass-python src:lru-dict src:luma.core src:luma.emulator src:luma.lcd src:luma.led-matrix src:luma.oled src:lz4tools src:macs src:matplotlib src:metomi-isodatetime src:milksnake src:mwparserfromhell src:netgen src:nipy src:nmodl src:notmuch src:numpy-stl src:opendrop src:openslide-python src:opentsne src:pcpp src:peewee src:pglast src:photutils src:pillow src:plotpy src:plyvel src:poezio src:poolcounter src:psd-tools src:psi4 src:pycorrfit src:pyftdi src:pyfuse3 src:pyicu src:pykwalify src:pymatgen src:pymbolic src:pynauty src:pyreflink src:pyregion src:pyrle src:pyrsistent src:pysmbc src:python-acora src:python-aiohttp src:python-argon2 src:python-awkward src:python-bonsai src:python-bumps src:python-cartopy src:python-cmarkgfm src:python-confluent-kafka src:python-cramjam src:python-cymem src:python-datrie src:python-drizzle src:python-evdev src:python-falcon src:python-fitsio src:python-freesasa src:python-hdmedians src:python-hiredis src:python-httptools src:python-hug src:python-intbitset src:python-levenshtein (ITA: #1065327) src:python-libcst src:python-libdiscid src:python-libzim src:python-llfuse src:python-lzo src:python-msgpack src:python-multidict src:python-mutf8 src:python-nacl src:python-preshed src:python-psycopg2cffi src:python-pybedtools src:python-pyeclib src:python-pyo src:python-pyppmd src:python-pyproj src:python-pyscss src:python-pyspike src:python-rapidjson src:python-ratelimiter src:python-rcssmin src:python-rjsmin src:python-rocksdb src:python-rosettasciio src:python-rtmidi src:python-setproctitle src:python-shapely src:python-suitesparse-graphblas src:python-thinc src:python-time-machine src:python-tinyalign src:python-wrapt src:python-wsaccel src:python-xeddsa src:python-xmlsec src:python-xypattern src:python-yappi src:pytorch-text src:pywavelets src:qiskit-aer (RFH: #1008626) src:qiskit-terra (RFH: #1008625) src:rasterio src:receptor src:remctl src:reproject src:ros2-ament-index src:rpds-py src:rpy2 src:s3ql src:sasmodels src:scikit-learn src:scipy src:segyio src:siconos src:skimage src:smbus2 src:sqlalchemy src:sshfs-fuse src:suricata-update src:synphot src:tiktoken src:tinyarray src:votca src:websockify src:wxpython4.0 src:xrayutilities src:zope.interface(*) → python3-pytest:armhf
9 9src:colorcet src:duplicity src:genx src:gpiozero src:hyperspy src:kiwi src:python-pyo src:python-thinc src:pyxrd(*) → python3-mock:armhf
2 2src:colorcet src:genx(*) → python3-pyct: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 depchainpackages with (possibly transitive) conflicting dependenciesDepchain 1Depchain2Conflict
1 1src:colorcet(*) → python3-pytest-mpl → python3-pil → python3 → python3-minimal → (*) → python3-all → python3 → python3-minimal python3-minimal:amd64
1 1src:colorcet(*) → python3-pytest-mpl → python3-pil → python3 → python3-minimal → python3.11-minimal → (*) → python3-all → python3.11 → python3.11-minimal python3.11-minimal:amd64
1 1src:colorcet(*) → python3-pytest-mpl → python3-pil → python3 → python3.11 → (*) → python3-all → python3.11 python3.11:amd64
1 1src:colorcet(*) → python3-all → python3 → (*) → python3-pytest-mpl → python3-pil → python3 python3:armhf

generated: 20240624T000000Z

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.