On 11-Oct-2013, Ben Finney wrote: > For this, I use ‘bzr-buildpackage --source --merge’, which builds a > Debian source package from the pristine upstream tarball and the Debian > changes.
The ‘bzr-builddeb’ package contains the ‘bzr-buildpackage’ program. This operates the same way as the other ‘$VCS-buildpackage’ tools, as far as I know. My procedure for building from my current VCS revision is: * Finalise the release, temporarily (I don't commit a release to VCS until it's actually released). In Emacs, ‘C-c C-d unstable RET’, ‘C-c C-f’, then save the changelog. The ‘dpkg-dev-el’ package contains the ‘debian-changelog’ Emacs mode I use for this. * Build the source package, with ‘bzr-buildpackage --source --merge’. This creates the source package (in Debian source format “3.0 (quilt)”) from the pristine upstream tarball, plus a separate ‘….debian.tar.gz’ containing the contents of ‘debian/’, plus the ‘….dsc’. This also tests that the patches will apply cleanly to the upstream source, and runs Lintian on the generated source package. * Revert the finalisation of the release, ‘bzr revert debian/changelog’ (or just undo in the Emacs buffer). * Build the binary package from the generated source package, with Pbuilder. I use hooks to ensure that Lintian gets run on the resulting binary packages and reports any tags. Please let me know if there are other questions about this. -- \ “I was once walking through the forest alone and a tree fell | `\ right in front of me, and I didn't hear it.” —Steven Wright | _o__) | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
