Heh, this can indeed be surprising, the only reason I knew is because
I've been bitten by this in the past.
Neither me nor Paul immediately why that built-tree detection and
treatment is needed; what I can see is that it was implemented a long
time ago, likely for good reasons we'll need to figure out before
changing the existing behavior.
** Summary changed:
- wrong version when building a package that's already part of the initial image
+ autopkgtest <src/pkg/directory> "built tree" detection is surprising and not
well documented
** Changed in: autopkgtest (Ubuntu)
Status: Incomplete => Triaged
** Changed in: autopkgtest (Ubuntu)
Importance: Undecided => Wishlist
--
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
