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
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.
14
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.
16
As of September 2010, there are four PPAs:
18
<https://launchpad.net/~bzr/+archive/ppa>
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.
21
25
<https://launchpad.net/~bzr-beta-ppa/+archive>
22
Releases and release candidates.
24
28
<https://launchpad.net/~bzr-nightly-ppa/+archive>
25
29
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``.
31
We build a distinct package for each distrorelease.
34
32
If you upload a release-specific version, you should add a suffix to the
35
33
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
35
Dapper uses the ``python-support`` framework and later distributions use
36
``python-central``. This has little effect on everyday packaging but does
37
mean that some of the control files are quite different.
37
39
Every package is first uploaded into the beta ppa. For final release
38
40
versions it is also copied to the main PPA.
40
42
The packaging information is kept in branches of bzr on Launchpad, named
42
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
44
<https://code.launchpad.net/~bzr/ubuntu/hardy/bzr/bzr-ppa>.
44
<lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used
46
<lp:~bzr/ubuntu/hardy/bzr/bzr-ppa>. These branches are intended to be used
45
47
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)
53
78
* 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
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::
77
91
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.
111
158
export PACKAGE="bzr"
112
159
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
113
160
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
161
* Optionaly merge debian unstable.
114
162
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh
115
163
~/dev/bzr/bzr.dev/tools/packaging/update-control.sh 1.16 1.17 1.18
116
164
~/dev/bzr/bzr.dev/tools/packaging/build-packages.sh
117
dput bzr-beta-ppa ${PACKAGE}_$VERSION*.changes
165
dput ppa:bzr/proposed ${PACKAGE}_$VERSION*.changes
119
167
Rinse and repeat for all the plugins by changing VERSION and PACKAGE.
157
205
#. Checkout (or update) the packaging branch for each supported release::
159
bzr co lp:~bzr/bzr/packaging-hardy
207
bzr co lp:~bzr/ubuntu/hardy/bzr/bzr-ppa
161
209
There is a script available to help::
163
211
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/
165
217
#. The ``bzr-builddeb`` step will download the original tarball if you do
166
218
not already have it, putting it into a ``tarballs`` directory.
232
284
tools/packaging/build-packages.sh
234
#. Upload into the beta PPA for each release::
236
dput bzr-beta-ppa bzr*1.17-1*.changes
238
#. For final release versions, also copy it into the ``~bzr`` PPA::
240
dput bzr-ppa ../bzr_1.17-1\~bazaar1\~hardy1\_source.changes
242
Alternatively, you can use Launchpad's "copy" feature to copy the
243
packages between repositories.
286
#. Upload into the PPA for each release::
288
dput dput ppa:bzr/proposed bzr*1.17-1*.changes
245
290
#. You should soon get an "upload accepted" mail from Launchpad, which
246
291
means that your package is waiting to be built. You can then track its
282
327
summary of current package versions with::
284
329
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
