Package: autopkgtest
Version: 5.5
Severity: wishlist
Hi,
when a tested package has unsatisfiable deps, autopkgtest reports only
that the package had such a problem -- no information about what is
actually triggering the problem is given, which makes it harder to debug
than should be.
In the log, I had first:
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU mK Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on node-nanomatch:amd64 < none |
1.2.13-1 @un uH >
Considering node-nanomatch:amd64 1 as a solution to
autopkgtest-satdep:amd64 -2
Removing autopkgtest-satdep:amd64 rather than change node-nanomatch:amd64
Done
Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
then later:
autopkgtest: WARNING: package node-nanomatch is not installed though it
should be
require FAIL badpkg
blame: node-nanomatch_1.2.13-1.dsc
badpkg: Test dependencies are unsatisfiable. A common reason is that
your testbed is out of date with respect to the archive, and you need to
use a current testbed or run apt-get update or use -U.
The common reason given wasn't applicable.
jpuydt on irc.debian.org
