[Bug 1183916] Re: Purge build dependencies after building package

[Adam Gandelman]

Yes, it certainly is confusing. :P

I've thrown up a patch against  autopkgtest 2.0.1ubuntu4, I need to
rebase against newest version before submitting.  It attempts to track
new dependencies that are installed during package build time and does a
quick attempt at purging them post-build.  ATM the purge is pretty naive
(just a dpkg -P $PACKAGES), but this fixes the issue for me and fails
tests when a package is missing a run-time Depends that happens to be
listed as a Build-Depends.

http://bazaar.launchpad.net/~gandelman-a/ubuntu/precise/autopkgtest/purge_build_deps/revision/31

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1183916

Title:
  Purge build dependencies after building package

Status in Automated Testing of Ubuntu Packages:
  Confirmed
Status in “autopkgtest” package in Ubuntu:
  New

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:///home/asb/development/pkg-bzr/bzr-git

  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://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-
  adt-bzr-git/1/

   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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1183916/+subscriptions