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!
** Changed in: autopkgtest (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2056334
Title:
wrong version when building a package that's already part of the
initial image
Status in autopkgtest package in Ubuntu:
Incomplete
Bug description:
While working on needrestart autopkgtests, I've run into issues
testing it using my standard invocation:
autopkgtest . -U -- lxd autopkgtest/ubuntu/noble/amd64
The runner wouldn't install the built package but would just keep
whichever version is in the archive, while still using the new sources
for getting the test scripts, which of course would result in failures
:)
It works fine with packages not part of the base image, e.g. hello.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056334/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
