Comment 2 for bug 1183916

Running into the same issue. I'm trying to spin up fresh cloud instances that include an unpacked source tree. I'd like to catch instances where a dependencies are missing from the packages' Depends, regardless of their existence in Build-Depends. Currently, if the runner has reached the post-build, post-install tests, its usually a sign that the dependency exists in Build-Depends (or the package probably woudln't have built). But at this point, the package has been installed on the system and the functional tests of the package pass even tho the dependency is missing.