1
Managing the Bazaar PPA
2
=======================
4
See also: `Bazaar Developer Document Catalog <index.html>`_.
10
We build Ubuntu ``.deb`` packages for Bazaar as an important part of the release
11
process. These packages are hosted in a few `Personal Package Archives (PPA)`__ on
14
__ https://help.launchpad.net/PPAQuickStart
16
As of June 2008, there are three PPAs:
18
<https://launchpad.net/~bzr/+archive>
19
Final released versions.
21
<https://launchpad.net/~bzr-beta-ppa/+archive>
22
Releases and release candidates.
24
<https://launchpad.net/~bzr-nightly-ppa/+archive>
25
Automatic nightly builds from trunk.
27
We build packages for every supported Ubuntu release
28
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
29
when the release passes end-of-life because all users should
30
have upgraded by then. (As of May 2008, Edgy Eft is no longer supported.)
32
We build a distinct package for each distrorelease. As of bzr 1.5, Dapper
33
uses ``python-support`` and later distributions use ``python-central``.
34
If you upload a release-specific version, you should add a suffix to the
35
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
37
Every package is first uploaded into the beta ppa. For final release
38
versions it is also copied to the main PPA.
40
The packaging information is kept in branches of bzr on Launchpad, named
42
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
44
<lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used
45
with the ``bzr-builddeb`` plugin.
50
* You must have a Launchpad account and be a member of the teams
51
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
53
* You must have a GPG key registered to your Launchpad account.
55
* Configure ``dput`` to upload to our PPA with this section in your
59
fqdn = ppa.launchpad.net
61
incoming = ~bzr-beta-ppa/ubuntu
63
allow_unsigned_uploads = 0
66
fqdn = ppa.launchpad.net
68
incoming = ~bzr/ubuntu
70
allow_unsigned_uploads = 0
72
You may also want to add these lines to prevent inadvertently attempting
73
to upload into Ubuntu or Debian, which will give a somewhat unclear
77
default_host_main = notspecified
79
* Configure ``bzr-builddeb`` to sign the package, which is required for
80
Launchpad to build it. Put this in ``~/.bazaar/builddeb.conf`` ::
83
builder = dpkg-buildpackage -rfakeroot
84
source-builder= dpkg-buildpackage -rfakeroot -S -sa
86
* You need a Ubuntu (or probably Debian) machine, and ::
88
sudo apt-get install build-essential devscripts dput quilt patch libcrypt-ssleay-perl debhelper cdbs python-docutils
90
Please update this document if you encounter unmet dependencies or find a
91
shorter way to express them.
93
* You will also want to have the `bzr-builddeb`_ plugin installed, which
94
depends on `bzrtools`_.
96
.. _`bzr-builddeb`: http://launchpad.net/bzr-builddeb
97
.. _`bzrtools`: http://launchpad.net/bzrtools
106
For people who have already set up everything they need, building the
107
release packages is as simple as::
109
cd ~/dev/bzr/releases/packaging
110
ln ~/dev/bzr/releases/bzr-1.6.tar.gz ./bzr_1.6.orig.tar.gz
111
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
112
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
113
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
114
~/dev/bzr/bzr.dev/tools/packaging/build-packages
115
dput bzr-beta-ppa bzr_1.6~beta3-1~bazaar1*.changes
120
#. You will end up checking out a separate directory for each supported
121
release. Such as ``~/dev/bzr/releases/packaging/hardy``. In each of these
122
branches, you will produce the package for the release.
124
#. Decide on the final version number. It should be of this form::
126
bzr-1.6~beta3-1~bazaar1~hardy1
128
**Note:** There are three hyphen-separated parts: the *package name*,
129
the *upstream version*, and the *packaging version*.
131
**Caution:** Upstream betas or release candidates must insert a tilde
132
to make them sort before the final release, like this:
133
``bzr-1.6~beta3-1~bazaar1~hardy1``.
135
Final releases will use a release string of the form:
136
``bzr-1.6-1~bazaar1~hardy1``
138
#. Export the distroreleases that you will be packaging for::
140
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid jaunty"
142
#. Checkout (or update) the packaging branch for each supported release::
144
bzr co lp:~bzr/bzr/packaging-hardy
146
There is a script available to help::
148
tools/packaging/update-packaging-branches.sh
150
#. The ``bzr-builddeb`` step will download the original tarball if you do
151
not already have it, putting it into a ``tarballs`` directory.
153
#. For Bazaar plugins, change the ``debian/control`` file to express a
154
dependency on the correct version of ``bzr``.
156
For bzrtools this is typically::
158
Build-Depends-Indep: bzr (>= 1.6~), rsync
159
Depends: ${python:Depends}, bzr (>= 1.6~), bzr (<< 1.7~), patch
161
#. Make a new ``debian/changelog`` entry for the new release,
162
either by using ``dch`` or just editing the file::
164
dch -v '1.6~beta3-1~bazaar1~hardy1' -D hardy
166
dch will default to the distro you're working in and this isn't checked
167
against the version number (which is just our convention), so make sure
170
Make sure you have the correct email address for yourself (you may need
171
export DEBEMAIL=`bzr whoami` if it isn't already set), version number, and
172
distribution. It should look something like this::
174
bzr (1.6~beta3-1~bazaar1~hardy1) hardy; urgency=low
176
* New upstream release.
178
-- John Sample <sample@example.com> Mon, 31 Mar 2008 12:36:27 +1100
180
If you need to upload the package again to fix a problem, normally you
181
should increment the last number in the version number, following the
182
distro name. Make sure not to omit the initial ``-1``, and make sure
183
that the distro name in the version is consistent with the target name
184
outside the parenthesis.
186
You will also want to commit these changes into the packaging branch.
188
There is a helper script which will update the changelog and commit it
189
for all of your ``$UBUNTU_RELEASES``. It is available as::
191
tools/packaging/update-changelogs.sh
193
You must supply the release string, such as::
195
tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
197
It will automatically append the distro numbering on the end.
199
#. Build the source packages::
201
cd packaging-$DISTRO; bzr builddeb -S
203
This will create a ``.changes`` file. If you didn't configure builddeb
204
to automatically sign them, you can use ::
206
debsign -m$UID *.changes
208
where ``$UID`` is the gpg key you want to use to sign the changes.
210
#. Upload into the beta PPA for each release::
212
dput bzr-beta-ppa bzr_1.6-1*.changes
214
#. For final release versions, also copy it into the ``~bzr`` PPA::
216
dput bzr-ppa ../bzr_1.6-1\~bazaar1\~hardy1\_source.changes
218
Alternatively, you can use Launchpad's "copy" feature to copy the
219
packages between repositories.
221
#. You should soon get an "upload accepted" mail from Launchpad, which
222
means that your package is waiting to be built. You can then track its
223
progress in <https://launchpad.net/~bzr-beta-ppa/+archive> and
224
<https://launchpad.net/~bzr-beta-ppa/+archive/+builds>.
230
bzr-svn uses a packaging branch that contains both the source
231
(including any changes against upstream) and the ``debian/`` directory.
235
#. Get a checkout of ``lp:~bzr/bzr-svn/hardy-ppa/``
237
#. Merge from ``http://bzr.debian.org/pkg-bazaar/bzr-svn/experimental/``
239
This should bring in both upstream and packaging changes for the new
240
release, and it's updated as part of the bzr-svn release process.
242
#. Run ``dch -v 0.4.15-1~bazaar1-hardy1 -D hardy`` or similar
244
#. Run ``bzr builddeb --source``
246
bzr-builddeb will automatically check out the appropriate tag from the
247
main branch of bzr-svn, build, and package it.
249
#. ``dput bzr-beta-ppa ../bzr-svn_0.4.15-1~bazaar1~hardy1_source.changes``
252
Monitoring the contents of PPAs
253
-------------------------------
255
If you add all the bzr PPAs to your ``sources.list`` then you can see a
256
summary of current package versions with::
258
apt-cache madison bzr
262
vim: filetype=rst textwidth=74 ai shiftwidth=4
added
removed
doc/developers/ppa.txt
