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.
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.
| # of packages per conflict | Conflict |
|---|---|
| 38 | libpsm2-2:armhf |
| 19 | libpsm-infinipath1:amd64 |
| 17 | mpi-default-bin:armhf |
| 13 | libhdf5-mpi-dev:amd64 |
| 13 | libhdf5-openmpi-dev:amd64 |
| 12 | binutils-x86-64-linux-gnu:amd64 |
| 12 | libevent-dev:amd64 |
| 12 | mpi-default-dev:amd64 |
| 10 | libpsm-infinipath1:armhf |
| 1 | python3-minimal:armhf |
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.
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.
| # of packages per conflict | Conflict |
|---|---|
| 8 | libpsm2-2:armhf |
| 4 | binutils-x86-64-linux-gnu:amd64 |
| 4 | libevent-dev:amd64 |
| 4 | libhdf5-mpi-dev:amd64 |
| 4 | libhdf5-openmpi-dev:amd64 |
| 4 | libpsm-infinipath1:amd64 |
| 4 | libpsm-infinipath1:armhf |
| 4 | mpi-default-bin:armhf |
| 4 | mpi-default-dev:amd64 |
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.
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.