Control: tags -1 + moreinfo On Mon, 01 Jun 2020 Michael Banck <mba...@gmail.com> wrote: > Package: autopkgtest > Version: 5.13.1 > Severity: wishlist > > Dear Maintainer, > > in order to run autopkgtest on porter machines, I have written a small > proof-of-concept script[1]. > > This script starts a schroot session, installs autopkgtest and the > package's binary packages into it and then tries to figure out the > required test dependencies in order to install them as well, followed by > running autopkgtest. > > It currently tries to figure out the dependencies by capturing the error > output from autopkgtest first, then installing the dependencies, then > running autopkgtest again. I am worried there will be cases without > dependencies or where dependencies are already satisfied by installing > the binary packages (and their dependencies), so autopkgtest will run > twice. > > It would helpful if autopkgtest had a mode which basically just checks > whether the test dependencies are satisfied, and if not, print them out, > then exiting before actually running the tests. Hi Michael, thanks for the suggestion, however I don't think this should be standard functionality (other autopkgtest maintainers may disagree).
However what you are looking for could by achieved via something like: $ apt-get satisfy \ "$(grep-dctrl -F Tests -s Depends -n test_name debian/tests/control)" where test_name is the test for which you want dependencies to be satisfied. Is this good enough for your use case? If you agree on this, I'd like to tag this bug as wontfix and close it. Cheers, Paride
