Below are two tables showing the two problem classes that prevent installation of foreign architecture binaries

We try to install all binary packages from a dummy architecture generated from amd64 (called armhf here) on amd64.

A machine parsable version can be retrieved in dose yaml format

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

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
32python3-packaging:armhf
31python3-pandas:armhf
11python3-networkx:armhf
9python3-certifi:armhf
2python3-colorama:armhf
2python3-colorlog:armhf

Conflict

# of packages per conflictConflict
1python3-minimal:armhf
1python3.11-minimal:armhf
1python3.11:amd64
1python3: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 depchainpackages with missing (possibly transitive) dependenciesDepchainsUnsatisfied dependency
32 32borgbackup borgbackup2 iva macsyfinder mayavi2 mininet ont-fast5-api python3-astropy python3-cartopy python3-clevercsv python3-fastparquet python3-galpy python3-hug python3-hyperspy python3-intake python3-jpype python3-matplotlib python3-mdanalysis python3-numexpr python3-pikepdf python3-presto python3-pygac python3-qutip python3-sunpy python3-tango python3-thinc python3-tpm2-pytss python3-vispy python3-xraylarch python3-yt reprozip spades(*) python3-packaging:armhf
31 31busco cnvkit epigrass jitterdebugger-utils macsyfinder python3-biom-format python3-bmtk python3-cfgrib python3-clevercsv python3-cobra python3-cogent3 python3-dials python3-fastparquet python3-feather-format python3-geotiepoints python3-iow python3-loompy python3-mdtraj python3-metview python3-mlpack python3-orange3 (ITP: #911106) python3-pairtools python3-presto python3-pyani python3-pyreadstat python3-pyrle python3-skbio python3-xraylarch q2-cutadapt q2-metadata umis(*) python3-pandas:armhf
11 11epigrass hinge iva macsyfinder psi4 python3-mdtraj python3-orange3 (ITP: #911106) python3-pomegranate python3-setools python3-torch ragout(*) python3-networkx:armhf
9 9displaycal macsyfinder python3-aioquic python3-fiona python3-geventhttpclient python3-netcdf4 python3-pyproj python3-rasterio python3-uamqp(*) python3-certifi:armhf
2 2macsyfinder python3-ansimarkup(*) python3-colorama:armhf
2 2liquidctl macsyfinder(*) python3-colorlog: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 1macsyfinder(*)python3-yamlpython3python3-minimal(*)ncbi-blast+python3python3-minimal python3-minimal:armhf
1 1macsyfinder(*)python3-yamlpython3python3-minimalpython3.11-minimal(*)ncbi-blast+python3python3.11python3.11-minimal python3.11-minimal:armhf
1 1macsyfinder(*)ncbi-blast+python3python3.11(*)python3-yamlpython3python3.11 python3.11:amd64
1 1macsyfinder(*)ncbi-blast+python3(*)python3-yamlpython3 python3:amd64

generated: 20240226T000000Z


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.