Speaking of your workflow, instead of `dpkg-buildpackage -S` you could call the clean target before running autopkgtest, to make sure the tree is "unbuilt"
debuild -- clean && autopkgtest ... dpkg-buildpackage -S calls the clean target, so this should just work in your case. -- 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: autopkgtest <src/pkg/directory> "built tree" detection is surprising and not well documented Status in autopkgtest package in Ubuntu: Triaged 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
