Process for Making Debian Packages
We keep debian packaging info in a separate branch from trunk, managed by bzr-builddeb. The packaging branch is a child branch and is not intended to be merged directly back in to trunk. For instance, using pristine-tarball it stores the contents of the release tarballs in the branch itself.
When a new release is made upstream (for instance, 1.0.2), the process is:
Get a copy of the debian packaging branch:
bzr branch lp:~swift-core/swift/debian cd debian
Merge in all of the changes from trunk up until the released version:
bzr merge -rtag:1.0.2 lp:swift bzr commit
Merge in the contents of the released tarball:
bzr merge-upstream ../swift-1.0.2.tar.gz --version=1.0.2
Check things out, potentially commit:
debcommit
Build packages: (bzr bd can be configured to use pdebuild or whatever to actually do the build step)
bzr bd -S # For source packages, or: bzr bd # For binary packages
Once the package is uploaded to the debian repo, don't forget to run:
bzr mark-uploaded
Which will tag the repo appropriately so that UDD will eventually be able to match package versions to repo versions.