Purge build dependencies after building package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
Fix Released
|
Undecided
|
Unassigned | ||
autopkgtest (Ubuntu) |
Won't Fix
|
Wishlist
|
Adam Gandelman |
Bug Description
Adding autopkgtests to bzr-git, I ran into an issue.
I did tested my changes locally using using lp:auto-package-testing.
.bin/run-adt-test -S file://
Log attached...
The tests were successful. After uploading to Debian and syncing to Ubuntu, the test failed due to a dependency problem on Ubuntu's jenkins instance:
https:/
Apparently, if you run it on an unpacked source tree, it builds the package installing all the build dependencies. It then installs the built binary and runs the tests without purging the build dependencies. This is not what I would think the expected result would be. I think it would make sense to purge the build dependencies after building package.
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.