> Maybe we indeed want a "minimal" autopkgtest environment, but many > upstream tests will fail in those and I don't see an automatic way to test > a random package in this way.
Even if not minimal, at least correspond to the upstream declares dependencies. by 'declare' I am not even sure of the meaning. dependencies of the test can be different from the required installed ones. Maybe we should install only the python binaries and the dependencies marked <!nocheck>. Is there a standard in the Python community for the test dependencies ?
