Below are two tables showing the two problem classes that prevent co-installation of Multi-Arch:same binaries
For every M-A:same package we create a dummy package with the -pseudo prefix which depends on that package for amd64 and a dummy architecture generated from amd64 (called armhf here).
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 missing | Unsatisfied dependency |
|---|---|
| 4 | python3-ffcx:armhf (< 1:0.10.0) |
| 4 | python3-ffcx:armhf (>= 1:0.9.0~) |
| 4 | python3-sphinx:armhf |
| 2 | catch2:armhf (>= 3.0.0) |
| 2 | python3-cffi:armhf |
| 2 | python3-nanobind:armhf (< 3) |
| 2 | python3-nanobind:armhf (>= 2.4) |
| 2 | python3-petsc4py:armhf |
| 2 | python3-pusimp:armhf (>= 0.1.1~) |
| 2 | python3-slepc4py:armhf |
| # of packages per conflict | Conflict |
|---|---|
| 6 | libamdhip64-5:amd64 |
| 6 | libpsm-infinipath1:armhf |
| 6 | libpsm2-2:armhf |
| 6 | mpi-default-bin:amd64 |
| 4 | binutils-x86-64-linux-gnu:armhf |
| 4 | binutils:armhf |
| 4 | cpp-14:armhf |
| 4 | cpp:armhf |
| 4 | gcc-14:armhf |
| 4 | gcc:amd64 |
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.
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: 20241216T000000Z
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.