A machine parsable version can be retrieved in dose yaml format
You can get an overview of all bugs tagged like that in the Debian bts
|# of packages per conflict||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 depchain||packages with (possibly transitive) conflicting dependencies||Depchain 1||Depchain2||Conflict|
|1||1||src:gprolog||(*) → gcc → cpp → cpp-6 →||(*) → build-essential → g++ → cpp → cpp-6||cpp-6:armhf|
|1||1||src:gprolog||(*) → build-essential → g++ → cpp →||(*) → gcc → cpp||cpp:amd64|
|1||1||src:gprolog||(*) → gcc → gcc-6 → binutils →||(*) → debhelper → binutils||elf-binutils:amd64|
|1||1||src:gprolog||(*) → build-essential → g++ → gcc-6 →||(*) → gcc → gcc-6||gcc-6:amd64|
|1||1||src:gprolog||(*) → gcc →||(*) → build-essential → gcc||gcc:armhf|
For questions and bugreports please contact j [dot] schauer [at] email [dot] de.