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

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
102python3-sphinx:armhf

Conflict

# of packages per conflictConflict
31libpsm-infinipath1:armhf
31libpsm2-2:amd64
29libamdhip64-5:amd64

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
102 102src:abinit src:adios src:aevol src:ampliconnoise src:apbs src:armci-mpi src:arpack src:boost1.83 src:cctools src:cp2k src:dbcsr src:dune-common src:dune-functions src:dune-geometry src:dune-grid src:dune-grid-glue src:dune-istl src:dune-localfunctions src:dune-typetree src:dune-uggrid src:eckit src:ectrans src:elkcode src:elpa src:espresso src:esys-particle src:examl src:eztrace src:fenics-dolfinx src:ffindex src:fftw src:fftw3 src:fiat-ecmwf src:form src:ga src:garli src:genomicsdb src:gerris src:gfsview src:gloo src:gpaw src:gretl src:gridtools src:gromacs src:gtg-trace src:gyoto src:hdf5 src:hpcc src:hyphy src:iqtree src:libmbd src:liggghts src:lrslib src:mathgl src:mfem src:molds src:mpgrafic src:mpi4py src:mpi4py-fft src:mpqc src:mrbayes src:mrmpi src:mumps src:murasaki src:netgen src:neuron src:nwchem src:oasis3 src:open-coarrays src:openfoam src:opm-common src:opm-grid src:opm-upscaling src:otf src:p4est src:palabos (ITA: #944878) src:papi src:phyml src:pnetcdf src:pysph src:python-escript src:pytorch src:pyzoltan src:ray src:relion src:rmpi src:rocalution src:ruby-mpi src:scilab src:silo-llnl src:slepc4py src:sopt src:spfft src:spooles src:starpu src:stopt src:sundials src:superlu-dist src:tachyon src:tree-puzzle src:valgrind src:vtk9(*) → mpi-default-dev → libopenmpi-dev → libpmix-dev → python3-sphinx: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
31 31src:armci-mpi src:dbcsr src:dune-common src:dune-geometry src:dune-istl src:dune-localfunctions src:dune-typetree src:dune-uggrid src:elkcode src:esys-particle src:ffindex src:form src:gretl src:hpcc src:lammps src:liggghts src:med-fichier src:meep-mpi-default src:molds src:mpgrafic src:mpi4py src:mpqc src:nwchem src:opm-common src:opm-simulators src:opm-upscaling src:otf src:p4est src:rmpi src:ruby-mpi src:superlu-dist(*) → mpi-default-dev → libopenmpi-dev → libopenmpi40 → libfabric1 → libpsm-infinipath1 → (*) → mpi-default-bin → openmpi-bin → libopenmpi40 → libfabric1 → libpsm-infinipath1 libpsm-infinipath1:armhf
31 31src:armci-mpi src:dbcsr src:dune-common src:dune-geometry src:dune-istl src:dune-localfunctions src:dune-typetree src:dune-uggrid src:elkcode src:esys-particle src:ffindex src:form src:gretl src:hpcc src:lammps src:liggghts src:med-fichier src:meep-mpi-default src:molds src:mpgrafic src:mpi4py src:mpqc src:nwchem src:opm-common src:opm-simulators src:opm-upscaling src:otf src:p4est src:rmpi src:ruby-mpi src:superlu-dist(*) → mpi-default-bin → openmpi-bin → libopenmpi40 → libpsm2-2 → (*) → mpi-default-dev → libopenmpi-dev → libopenmpi40 → libpsm2-2 libpsm2-2:amd64
29 29src:dbcsr src:dune-common src:dune-geometry src:dune-istl src:dune-localfunctions src:dune-typetree src:dune-uggrid src:elkcode src:esys-particle src:ffindex src:form src:gretl src:hpcc src:lammps src:liggghts src:med-fichier src:meep-mpi-default src:molds src:mpgrafic src:mpi4py src:mpqc src:opm-common src:opm-simulators src:opm-upscaling src:otf src:p4est src:rmpi src:ruby-mpi src:superlu-dist(*) → mpi-default-bin → openmpi-bin → libopenmpi40 → libucx0 → libamdhip64-5 → (*) → mpi-default-dev → libopenmpi-dev → libopenmpi40 → libucx0 → libamdhip64-5 libamdhip64-5:amd64

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.