Below are two tables showing the two problem classes that prevent cross compilation on the dependency level. This example tries to satisfy the crossbuild dependencies of all source packages on amd64 as the build architecture for a dummy architecture generated from amd64 (called armhf here) as the host architecture in current Debian sid.

A machine parsable version can be retrieved in dose yaml format

Bugs are associated with packages on this page if they carry the usertag "cross-satisfiability" of the user "debian-cross@lists.debian.org".

You can get an overview of all bugs tagged like that in the Debian bts

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:varnish-agent

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
54python-docutils:armhf
23libwww-perl:armhf
1python-demjson:armhf

Conflict

# of packages per conflictConflict
1cpp-6:armhf
1cpp:armhf
1elf-binutils:amd64
1gcc-6:amd64
1gcc:armhf

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
54 54src:abstract-rendering src:angband src:apcupsd (O: #866835) src:bcolz src:bzr src:c-blosc src:chemps2 src:coz-profiler src:dballe src:diet src:ecasound src:gamera src:geany-plugins src:ibniz src:infiniband-diags src:intel-gpu-tools src:kineticstools src:kxd src:libfiu src:libtorrent-rasterbar src:logservice src:m2crypto src:massif-visualizer src:mercurial src:mpv src:mydumper src:opencolorio src:postgresql-multicorn src:prads src:pycares src:pycurl src:pygresql (O: #623685) src:pypy src:pystemmer src:python-afl src:python-bitarray src:python-blosc src:python-coverage src:python-escript src:python-getdns src:python-jellyfish src:python-maxminddb src:python-pyaudio src:python-regex src:sagemath src:sddm src:subvertpy src:syncevolution src:tlsh src:uhd src:varnish src:varnish-agent src:wreport src:xss-lock(*) → python-docutils:armhf
23 23src:devscripts (RFH: #800413) src:flexml src:fusioninventory-agent src:gbrowse src:gdnsd src:gnuift (O: #471251) src:ikvm src:libapache2-mod-perl2 src:libatteanx-store-sparql-perl src:libebook-tools-perl src:libembperl-perl src:libmoose-perl src:libmouse-perl src:libtfbs-perl src:libxml-parser-perl src:mod-gnutls src:ndpmon src:pcp src:pwget src:sx src:varnish-agent src:webauth src:zoneminder(*) → libwww-perl:armhf
1 1src:varnish-agent(*) → python-demjson:armhf

conflict

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.

# of packages per conflict# of packages per depchainpackages with (possibly transitive) conflicting dependenciesDepchain 1Depchain2Conflict
1 1src:varnish-agent(*) → varnish → gcc → cpp → cpp-6 → (*) → build-essential → gcc → gcc-6 → cpp-6 cpp-6:armhf
1 1src:varnish-agent(*) → varnish → gcc → cpp → (*) → build-essential → gcc → cpp cpp:armhf
1 1src:varnish-agent(*) → varnish → gcc → gcc-6 → binutils → (*) → debhelper → binutils elf-binutils:amd64
1 1src:varnish-agent(*) → build-essential → gcc → gcc-6 → (*) → varnish → gcc → gcc-6 gcc-6:amd64
1 1src:varnish-agent(*) → varnish → gcc → (*) → build-essential → gcc gcc:armhf

generated: 20170717T000000Z

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.