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

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
37libokteta-l10n:armhf (>= 5:0.26.2-2)

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
37 7libkasten4controllers0 libkasten4gui0 libkasten4okteta2controllers0 libkasten4okteta2core0 libkasten4okteta2gui0 okteta okteta-dev(*)libkasten4core0 libokteta-l10n:armhf (>= 5:0.26.2-2)
5libkasten4okteta2controllers0 libkasten4okteta2core0 libkasten4okteta2gui0 libokteta3gui0 okteta-dev(*)libokteta3core0
4libkasten4core0 libkasten4okteta2core0 libokteta3core0 libokteta3gui0(*)
4libkasten4okteta2controllers0 libkasten4okteta2gui0 okteta okteta-dev(*)libkasten4okteta2core0
3libkasten4okteta2controllers0 libkasten4okteta2gui0 okteta-dev(*)libokteta3gui0
1kdesdk(*)oktetalibkasten4core0
1kdesdk(*)oktetalibkasten4okteta2controllers0libokteta3gui0
1kdesdk(*)oktetalibkasten4okteta2core0
1kdesdk(*)oktetalibkasten4okteta2core0libokteta3core0
1kdevelop(*)libkasten4core0
1kdevelop(*)libkasten4okteta2core0
1kdevelop(*)libokteta3core0
1kdevelop(*)libokteta3gui0
1okteta(*)libkasten4okteta2controllers0libokteta3gui0
1okteta(*)libkasten4okteta2core0libokteta3core0
1plasma-kdevelop(*)kdeveloplibkasten4core0
1plasma-kdevelop(*)kdeveloplibkasten4okteta2core0
1plasma-kdevelop(*)kdeveloplibokteta3core0
1plasma-kdevelop(*)kdeveloplibokteta3gui0

generated: 20200203T000000Z


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://gitlab.mister-muffin.de/debian-bootstrap/botch

The html pages were generated by code which can be retrieved from https://gitlab.mister-muffin.de/debian-bootstrap/bootstrap_debian_net and which can be redistributed under the terms of the AGPL3+

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