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 two 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
We build packages for every supported Ubuntu release
25
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
26
when the release passes end-of-life because all users should
27
have upgraded by then. (As of May 2008, Edgy Eft is no longer supported.)
29
We build a distinct package for each distrorelease that has
30
different packaging requirements. As of bzr 1.5, Dapper uses
31
``python-support`` and later distributions use ``python-central``, so we
32
build one version for dapper and one version for everything else. If you
33
upload a release-specific version, you should add a suffix to the
34
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
36
Every package is first uploaded into one distroversion of the beta ppa.
37
It can then be copied to other compatible distroversions. For final
38
release versions it is also copied to the main PPA.
40
The ``debian/`` directory containing the packaging information is kept in
41
branches on Launchpad, named like
42
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
47
* You must have a Launchpad account and be a member of the teams
48
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
50
* You must have a GPG key registered to your Launchpad account.
52
* Configure ``dput`` to upload to our PPA with this section in your
56
fqdn = ppa.launchpad.net
58
incoming = ~bzr-beta-ppa/ubuntu
60
allow_unsigned_uploads = 0
63
fqdn = ppa.launchpad.net
65
incoming = ~bzr/ubuntu
67
allow_unsigned_uploads = 0
69
You may also want to add these lines to prevent inadvertently attempting
70
to upload into Ubuntu or Debian, which will give a somewhat unclear
74
default_host_main = notspecified
76
* You need a Ubuntu (or probably Debian) machine, and ::
78
sudo apt-get install build-essential devscripts dput quilt patch
83
#. You will need a working directory for each supported release, such as
84
``~/bzr/Packaging/hardy``
86
#. Download the official tarball of the release to e.g. ``~/bzr/Releases``
87
if you don't already have it.
89
#. Decide on the final version number. It should be of this form::
91
bzr-1.6~beta3-1~bazaar1~hardy1
93
There are three hyphen-separated parts: the *package name*, the *upstream
94
version*, and the *packaging version*.
96
**Caution:** Upstream betas or release candidates must insert a tilde
97
to make them sort before the final release, like this:
98
``bzr-1.6~beta3-1~bazaar1~hardy1``.
100
#. Create a directory per release::
102
mkdir ~/bzr/Releases/hardy
104
#. Copy or hardlink the original tarball into your per-disto directory, under an
105
appropriate name ending in ``.orig.tar.gz``. Untar it. The extracted
106
source directory and ``.orig`` file must match the version number you
107
calculated above. For example::
109
cp -l ~/bzr/Releases/bzr-1.6b3.tar.gz ~/bzr/Releases/hardy/bzr_1.6~beta3.orig.tar.gz
110
cd ~/bzr/Releases/hardy
111
tar xfvz bzr_1.6~beta3.orig.tar.gz
112
mv bzr-1.6b3 bzr-1.6~beta3
114
#. Change into that directory and check out the packaging branch::
118
bzr+ssh://bazaar.launchpad.net/~bzr/bzr/packaging-hardy \
121
#. For Bazaar plugins, change the ``debian/control`` file to express a
122
dependency on the correct version of ``bzr``.
124
For bzrtools this is typically::
126
Build-Depends-Indep: bzr (>= 1.6~), rsync
127
Depends: ${python:Depends}, bzr (>= 1.6~), bzr (<< 1.7~), patch
129
#. Make a new ``debian/changelog`` entry for the new release,
130
either by using ``dch`` or just editing the file::
132
dch -v '1.6~beta3-1~bazaar1~hardy1' -D hardy
134
dch will default to the distro you're working in and this isn't checked
135
against the version number (which is just our conversion), so make sure
138
Make sure you have the correct email address for yourself, version
139
number, and distribution. It should look something like this::
141
bzr (1.6~beta3-1~bazaar1~hardy1) hardy; urgency=low
143
* New upstream release.
145
-- John Sample <sample@example.com> Mon, 31 Mar 2008 12:36:27 +1100
147
If you need to upload the package again to fix a problem, normally you
148
should increment the last number in the version number, following the
149
distro name. Make sure not to omit the initial ``-1``, and make sure
150
that the distro name in the version is consistent with the target name
151
outside the parenthesis.
153
#. Commit these changes into the packaging branch::
155
bzr ci -m '1.6~beta3-1~bazaar1~hardy1: New upstream release.' debian
157
#. Remove the .bzr directory from the Debian dir, as this adds unnecessary
158
cruft to the package::
162
#. Build a source package::
166
This will create a ``.changes`` file in the per-distro directory,
167
and should invoke gpg to sign it with your key.
168
Check that file is reasonable: it should be uploading to the intended
169
distribution, have a .orig file included, and the right version number.
171
#. Upload into the beta PPA for each release::
173
dput bzr-beta-ppa ../bzr__1.6~beta3-1\~bazaar1\~hardy1\_source.changes
175
#. For final release versions, also copy it into the ``~bzr`` PPA::
177
dput bzr-ppa ../bzr__1.6-1\~bazaar1\~hardy1\_source.changes
179
#. You should soon get an "upload accepted" mail from Launchpad, which
180
means that your package is waiting to be built. You can then track its
181
progress in <https://launchpad.net/~bzr-beta-ppa/+archive> and
182
<https://launchpad.net/~bzr-beta-ppa/+archive/+builds>.
185
Monitoring the contents of PPAs
186
-------------------------------
188
If you add all the bzr PPAs to your ``sources.list`` then you can see a
189
summary of current package versions with::
191
apt-cache madison bzr
195
vim: filetype=rst textwidth=74 ai shiftwidth=4
added
removed
doc/developers/ppa.txt
