10
We build Ubuntu ``.deb`` packages for Bazaar as an important part of the
11
release process. These packages are hosted in a few `Personal Package
12
Archives (PPA)`__ on Launchpad.
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
14
__ https://help.launchpad.net/PPAQuickStart
16
As of September 2010, there are four PPAs:
16
As of June 2010, there are three PPAs:
18
<https://launchpad.net/~bzr/+archive/ppa>
18
<https://launchpad.net/~bzr/+archive>
19
19
Final released versions and updates.
20
Most users who want updates to bzr should add this.
22
<https://launchpad.net/~bzr/+archive/proposed>
23
Proposed uploads to move into ~bzr, awaiting testing.
25
21
<https://launchpad.net/~bzr-beta-ppa/+archive>
28
24
<https://launchpad.net/~bzr-nightly-ppa/+archive>
29
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.
31
32
We build a distinct package for each distrorelease.
32
33
If you upload a release-specific version, you should add a suffix to the
33
34
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
42
43
The packaging information is kept in branches of bzr on Launchpad, named
44
<https://code.launchpad.net/~bzr/ubuntu/hardy/bzr/bzr-ppa>.
45
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
46
<lp:~bzr/ubuntu/hardy/bzr/bzr-ppa>. These branches are intended to be used
47
<lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used
47
48
with the ``bzr-builddeb`` plugin.
49
**You should almost always upload to the beta ppa first** and then either
50
upload again or copy the packages into the release ppa. That reduces the
51
risk of breaking the main archive from which people get bzr updates.
57
We build packages for every supported Ubuntu release
58
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
59
when the release passes end-of-life because all users should
60
have upgraded by then.
62
As of August 2010, the following releases are supported:
67
* Jaunty (support ends October 2010)
69
* Dapper LTS (supported but no longer updated for new releases)
78
56
* You must have a GPG key registered to your Launchpad account.
80
On reasonably recent versions of Ubuntu you no longer need special dput
81
configuration, because you can just say ::
83
dput ppa:bzr/proposed <source.changes
86
However, you may still want to add these lines to ``~/.dput.cf`` prevent
87
inadvertently attempting to upload into Ubuntu or Debian, which will
88
give a somewhat unclear error::
58
* Configure ``dput`` to upload to our PPA with this section in your
62
fqdn = ppa.launchpad.net
64
incoming = ~bzr-beta-ppa/ubuntu
66
allow_unsigned_uploads = 0
69
fqdn = ppa.launchpad.net
71
incoming = ~bzr/ubuntu
73
allow_unsigned_uploads = 0
75
You may also want to add these lines to prevent inadvertently attempting
76
to upload into Ubuntu or Debian, which will give a somewhat unclear
91
80
default_host_main = notspecified
117
Overview of packaging with builddeb
118
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
120
* First update the oldest supported branch, using ``bzr merge-upstream``.
122
* Run ``bzr builddeb -S -- -sa`` to build a source package, then put
125
(``-S`` says to make a source-only upload, which is
126
required for Launchpad's builders. ``--sa`` says to include the
127
``.orig.tgz`` even if this doesn't seem to be the first upload for an
128
upstream release: this is often needed when rebuilding something that's
129
previously been uploaded to Debian or Ubuntu or into a different PPA.)
131
* Now merge across that change into each supported branch with a
132
simple ``bzr merge``.
134
Locally testing using pbuilder
135
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
137
It may be useful to locally test builds inside pbuilder. You may want to
138
use the script from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255165>
139
to wrap it, and to give it sensible defaults for your local machine.
141
Update all packages in proposed before copping the main ppa
142
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
144
If one updates bzr, and there are plugins that are not compatible with the
145
new version of bzr, this can cause pain for users using the ppa. In order to
146
avoid this, we first get all packages up to date in the proposed ppa, and then
147
copy them to the main ppa.
158
114
export PACKAGE="bzr"
159
115
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
160
116
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
161
* Optionaly merge debian unstable.
162
117
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh
163
118
~/dev/bzr/bzr.dev/tools/packaging/update-control.sh 1.16 1.17 1.18
164
119
~/dev/bzr/bzr.dev/tools/packaging/build-packages.sh
165
dput ppa:bzr/proposed ${PACKAGE}_$VERSION*.changes
120
dput bzr-beta-ppa ${PACKAGE}_$VERSION*.changes
167
122
Rinse and repeat for all the plugins by changing VERSION and PACKAGE.
205
160
#. Checkout (or update) the packaging branch for each supported release::
207
bzr co lp:~bzr/ubuntu/hardy/bzr/bzr-ppa
162
bzr co lp:~bzr/bzr/packaging-hardy
209
164
There is a script available to help::
211
166
tools/packaging/update-packaging-branches.sh
213
#. Optionaly, merge the Debian unstable branch into each of the packaging
214
branches. You can find the Debian unstable branch here:
215
http://bzr.debian.org/pkg-bazaar/
217
168
#. The ``bzr-builddeb`` step will download the original tarball if you do
218
169
not already have it, putting it into a ``tarballs`` directory.
270
221
#. Build the source packages::
272
cd bzr-$DISTRO; bzr builddeb -S
223
cd packaging-$DISTRO; bzr builddeb -S
274
225
This will create a ``.changes`` file. If you didn't configure builddeb
275
226
to automatically sign them, you can use ::
284
235
tools/packaging/build-packages.sh
286
#. Upload into the PPA for each release::
288
dput dput ppa:bzr/proposed bzr*1.17-1*.changes
237
#. Upload into the beta PPA for each release::
239
dput bzr-beta-ppa bzr*1.17-1*.changes
241
#. For final release versions, also copy it into the ``~bzr`` PPA::
243
dput bzr-ppa ../bzr_1.17-1\~bazaar1\~hardy1\_source.changes
245
Alternatively, you can use Launchpad's "copy" feature to copy the
246
packages between repositories.
290
248
#. You should soon get an "upload accepted" mail from Launchpad, which
291
249
means that your package is waiting to be built. You can then track its
327
285
summary of current package versions with::
329
287
apt-cache madison bzr
332
Testing the contents of the PPA
333
-------------------------------
335
A somewhat crude but useful way to test the contents of the PPA is to
336
install the relevant packages into an schroot::
338
schroot -c hardy-test -u root -- \
339
apt-get install -o 'APT::Install-Suggests="true"' \
340
-o 'APT::Install-Recommends="true"' \
343
This should make sure everything can be installed; it won't guarantee that
346
Packaging dependencies
347
----------------------
349
Some of our updates to bzr in previous releases require backports of our
350
dependencies. Specific branches holding these backports:
352
* ``lp:~bzr/ubuntu/dapper/configobj/dapper-backport``
added
removed
doc/developers/ppa.txt
