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
35 33cduce hol-light libatdgen-ocaml-dev libcore-extended-ocaml-dev libcore-kernel-ocaml-dev libcore-ocaml-dev libctypes-ocaml-dev libcurl-ocaml-dev libeliom-ocaml-dev libipaddr-ocaml-dev libjs-of-ocaml-dev liblablgtkmathview-ocaml-dev liblambda-term-ocaml-dev libllvm-3.8-ocaml-dev libnproc-ocaml-dev libobus-ocaml-dev libocamlbricks-ocaml-dev libocsigenserver-ocaml-dev libpa-structural-sexp-camlp4-dev libppx-core-ocaml-dev libppx-deriving-ocaml-dev libppx-driver-ocaml-dev libppx-optcomp-ocaml-dev libppx-sexp-conv-ocaml-dev libppx-type-conv-ocaml-dev libppx-visitors-ocaml-dev libre2-ocaml-dev libsexplib-ocaml-dev libsqlexpr-ocaml-dev libtextutils-ocaml-dev libtyperep-camlp4-dev libusb-ocaml-dev libutop-ocaml-dev(*) ocaml-nox-4.02.3:armhf
30 27libatdgen-ocaml libcore-extended-ocaml libcore-kernel-ocaml libcore-ocaml libctypes-ocaml libcurl-ocaml libipaddr-ocaml libjs-of-ocaml liblablgtkmathview-ocaml liblambda-term-ocaml libobus-ocaml libocsigenserver-ocaml libppx-core-ocaml libppx-deriving-ocaml libppx-driver-ocaml libppx-optcomp-ocaml libppx-sexp-conv-ocaml libppx-type-conv-ocaml libre2-ocaml libsexplib-ocaml libsqlexpr-ocaml libtextutils-ocaml libusb-ocaml libutop-ocaml nurpawiki ocsigenserver utop(*) ocaml-base-nox-4.02.3:armhf

generated: 20171016T000000Z

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.