allow to decide which package provides a virtual package in all dependency relationships

use order induced by reduced_dist to classify nodes in the graph

use centrality/distance in graph

write script for bisecting Packages/Sources from snapshot.debian.org for changes in main scc and also compare different dists

try different external solver

reduced build dependencies can also be used to bootstrap languages

source packages that were cross compiled must be recompiled natively

during graph analysis:
  provide a way to mark build dependencies as non-breakable even in source
  packages without a build profile

when building a source package with a build profile, it might not generate some binary packages
which are otherwise needed in the same SCC. In this case, both versions of the source package must
be part of the SCC.

Package A and B provide C. A source package build depends on C. Its
installation set contains B. When calculating the intersection of each
disjunction with the installation set, how can one be sure that the package
that was chosen to provide C was indeed B and not A?

allow other libraries to use code of botch

find a way to combine order1.lst and order2.lst

allow all operations on packages to be made in-place

transparent decompression independent of filename extension

investigate why the main SCC is smaller if calculating a self contained repo first

write a program which analyzes all mixed real/virtual disjunctive dependencies and remove all virtual packages from it so that only real packages are left

add a subgraph inside installation set nodes such that one can check how one gets from the binary package of the installation set to the binary package that builds from one of the connected source packages

sort lists in json and html output

deterministic order of dictionary key traversal

blocking python3:
 - no soap module (needed for bts access)
 - networkx dot output doesnt work
 - networkx graph output is undeterministic (bug#749710)

build profile todo:

15:08 < helmut> wookey: we (josch) did write patches for wheezy-pu (rejected by srm, too invasive, but what could be less invasive?)
15:09 < helmut> wookey: we proposed backports, but full apt and dpkg is too invasive
15:09 < helmut> wookey: we proposed those stable patches for backports, but then the backport does not come from jessie violating backports policy
15:09 < helmut> wookey: we asked dsa to install auxillary packages (from neither wheezy nor wheezy-backports)
15:10 < helmut> wookey: we asked ftp to locally install a custom version of python-apt

create an importance metric for the cross case as well

allow an external list to be fed to cross.sh which contains information about which packages can and cannot be cross compiled
botch has to find a solution for cross compilation with only those packages that can be cross compiled

given a set of available binary packages (Packages file), and a set of package names, determine whether there is an installation set and if not, (important bit follows) give as many reasons as possible.
in my case the most common reason shall be "no installation candidate

the loop in cross.sh does not take into account that the order of packages might change

make all output sorted
