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.


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.


# of packages per missingUnsatisfied dependency


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
30 9libjs-of-ocaml liblambda-term-ocaml liblwt-ocaml libmew-vi-ocaml libobus-ocaml libreactivedata-ocaml libutop-ocaml libzed-ocaml utop(*) libreact-ocaml-rslm7:armhf
3liblambda-term-ocaml libmew-vi-ocaml-dev utop(*)libmew-vi-ocaml
3liblambda-term-ocaml libzed-ocaml-dev utop(*)libzed-ocaml
3liblambda-term-ocaml-dev libutop-ocaml utop(*)liblambda-term-ocaml
2libjs-of-ocaml liblambda-term-ocaml(*)liblwt-log-ocamlliblwt-ocaml
2liblambda-term-ocaml-dev libutop-ocaml(*)liblambda-term-ocamlliblwt-log-ocamlliblwt-ocaml
2liblambda-term-ocaml-dev libutop-ocaml(*)liblambda-term-ocamllibmew-vi-ocaml
2liblambda-term-ocaml-dev libutop-ocaml(*)liblambda-term-ocamllibzed-ocaml
25 11libcstruct-ocaml-dev libcurl-ocaml-dev libinotify-ocaml-dev (RFA: #784037) libjs-of-ocaml-dev liblambda-term-ocaml-dev liblwt-log-ocaml-dev liblwt-ssl-ocaml-dev libnproc-ocaml-dev libocsipersist-lib-ocaml-dev libocsipersist-ocaml-dev libusb-ocaml-dev(*)liblwt-ocaml-dev libreact-ocaml-dev-rslm7:armhf
8libjs-of-ocaml-dev liblambda-term-ocaml-dev liblwt-ocaml-dev libmew-vi-ocaml-dev libobus-ocaml-dev libreactivedata-ocaml-dev libutop-ocaml-dev libzed-ocaml-dev(*)
2liblambda-term-ocaml-dev libutop-ocaml-dev(*)libmew-vi-ocaml-dev
2liblambda-term-ocaml-dev libutop-ocaml-dev(*)libzed-ocaml-dev

generated: 20220221T000000Z

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

The html pages were generated by code which can be retrieved from and which can be redistributed under the terms of the AGPL3+

For questions and bugreports please contact j [dot] schauer [at] email [dot] de.