Opened at 2010-11-12T11:28:53Z
Closed at 2011-12-21T04:32:10Z
#1256 closed enhancement (invalid)
set up pbuilder for Debian/Ubuntu buildslaves
| Reported by: | zooko | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | undecided |
| Component: | dev-infrastructure | Version: | 1.8.0 |
| Keywords: | debian packaging buildbot | Cc: | |
| Launchpad Bug: |
Description
pbuilder is a tool to make sure that your build is not using any Debian packages other than the packages specified in your debian control file.
By using pbuilder on our Debian buildslaves we can be sure that any regressions in the Debian build will be detected. For example, if we change our Python source code to start depending on a library but we forget to add that library to the debian/control file (such as we recently did with pyasn1 (#1095)), then the pbuilder-powered build step will go red.
Change History (1)
comment:1 Changed at 2011-12-21T04:32:10Z by warner
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
We stopped creating debs, so this is now the responsibility of the debian/ubuntu maintainers. They usually use pbuilders (and a decent amount of automation) to create those debs, so they'll discover quickly if we've accidentally added a dependency. Not as short a feedback cycle as if we discovered it ourselves right after the commit, but I don't think it's worth maintaining duplicate copies of the .deb -building infrastructure just for that.