Hi, autopkgtest should already setup pinning to ensure that the tested package is the built one.
Before digging any deeper let's check one thing. When you specify a source package directory, autopkgtest distinguishes between a "built tree" and an "unbuilt tree". In the case of a "built tree", all test dependencies get satisfied by archive packages (see the manpage, under TESTING A DEBIAN PACKAGE).
So, if "." is a "built tree", the behavior you observe is expected. Now, what is it that makes autopkgtest consider a tree a "built tree"? It's the presence of the debian/files file.
@Simon can you please check if this is it? Thanks!
Hi, autopkgtest should already setup pinning to ensure that the tested package is the built one.
Before digging any deeper let's check one thing. When you specify a source package directory, autopkgtest distinguishes between a "built tree" and an "unbuilt tree". In the case of a "built tree", all test dependencies get satisfied by archive packages (see the manpage, under TESTING A DEBIAN PACKAGE).
So, if "." is a "built tree", the behavior you observe is expected. Now, what is it that makes autopkgtest consider a tree a "built tree"? It's the presence of the debian/files file.
@Simon can you please check if this is it? Thanks!