> You said "I want to check during the autopkgtest that the runtime > dependencies are well defines in the package" and for that you shouldn't > have any additional packages installed, but to run tests you normally need > additional packages, usually quite a lot of them.
I was spoken about the test specific dependencies. not the dependencies of the packages (dependencies which are imported in the upstream module code). > Most of them are, considering that the build process of a pure-Python > package is moving files around, building docs and running tests. > Which ones aren't? sphinx and friends? So how do we guaranty that the listed dependencies (from the upstream, supposing there are right ;) are well define in the binary package dependencies ? I just tell this because entry_point checking for the module dependencies. So sometimes I get <something> is missing when running entry points. > Yes, I just don't think the difference between @builddep@ and actual test > deps is big enough to matter for this task and, as I wrote above, this > won't help for your originally stated task so I'll assume you didn't > actually want that. thanks for your time Fred
