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 January 2011, there are the following 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/ppa, awaiting testing.
25
<https://launchpad.net/~bzr/+archive/obsolete>
26
A preserved copy of the final version of packages from ~bzr/ppa for
27
obsolete Ubuntu series.
29
<https://launchpad.net/~bzr-beta-ppa/+archive/ppa>
32
<https://launchpad.net/~bzr-beta-ppa/+archive/obsolete>
33
A preserved copy of the final version of packages from
34
~bzr-beta-ppa/ppa for obsolete Ubuntu series.
36
<https://launchpad.net/~bzr/+archive/daily>
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>
37
25
Automatic nightly builds from trunk.
39
We build a distinct package for each distrorelease.
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``.
40
34
If you upload a release-specific version, you should add a suffix to the
41
package version, e.g. ``1.3-1~bazaar1~dapper1``.
43
Dapper uses the ``python-support`` framework and later distributions use
44
``python-central``. This has little effect on everyday packaging but does
45
mean that some of the control files are quite different.
35
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
47
37
Every package is first uploaded into the beta ppa. For final release
48
38
versions it is also copied to the main PPA.
50
40
The packaging information is kept in branches of bzr on Launchpad, named
52
<https://code.launchpad.net/~bzr/ubuntu/hardy/bzr/bzr-ppa>.
42
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
54
<lp:~bzr/ubuntu/hardy/bzr/bzr-ppa>. These branches are intended to be used
44
<lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used
55
45
with the ``bzr-builddeb`` plugin.
57
**You should almost always upload to the proposed or beta ppa first** and
58
then copy the packages into the release ppa. That reduces the
59
risk of breaking the main archive from which people get bzr updates.
65
We build packages for every supported Ubuntu release
66
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
67
when the release passes end-of-life because all users should
68
have upgraded by then.
70
As of August 2010, the following releases are supported:
75
* Jaunty (support ends October 2010)
77
* Dapper LTS (supported but no longer updated for new releases)
79
The ``rmadison bzr`` command will gives you an up-to-date summary
80
of which bzr releases are current in each Ubuntu release.
88
53
* You must have a GPG key registered to your Launchpad account.
90
On reasonably recent versions of Ubuntu you no longer need special dput
91
configuration, because you can just say ::
93
dput ppa:bzr/proposed source.changes
96
However, you may still want to add these lines to ``~/.dput.cf`` prevent
97
inadvertently attempting to upload into Ubuntu or Debian, which will
98
give a somewhat unclear error::
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
101
77
default_host_main = notspecified
127
Overview of packaging with builddeb
128
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
130
* First update the oldest supported branch, using ``bzr merge-upstream``.
132
* Run ``bzr builddeb -S -- -sa`` to build a source package, then put
135
(``-S`` says to make a source-only upload, which is
136
required for Launchpad's builders. ``--sa`` says to include the
137
``.orig.tgz`` even if this doesn't seem to be the first upload for an
138
upstream release: this is often needed when rebuilding something that's
139
previously been uploaded to Debian or Ubuntu or into a different PPA.)
141
* Now merge across that change into each supported branch with a
142
simple ``bzr merge``.
144
Locally testing using pbuilder
145
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
147
It may be useful to locally test builds inside pbuilder. You may want to
148
use the script from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255165>
149
to wrap it, and to give it sensible defaults for your local machine.
151
Update all packages in proposed before copying to the main ppa
152
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
154
If one updates bzr, and there are plugins that are not compatible with the
155
new version of bzr, this can cause pain for users using the ppa. In order to
156
avoid this, we first get all packages up to date in the proposed ppa, and then
157
copy them to the main ppa.
215
157
#. Checkout (or update) the packaging branch for each supported release::
217
bzr co lp:~bzr/ubuntu/hardy/bzr/bzr-ppa
159
bzr co lp:~bzr/bzr/packaging-hardy
219
161
There is a script available to help::
221
163
tools/packaging/update-packaging-branches.sh
223
#. Optionaly, merge the Debian unstable branch into each of the packaging
224
branches. You can find the Debian unstable branch here:
225
http://bzr.debian.org/pkg-bazaar/
227
165
#. The ``bzr-builddeb`` step will download the original tarball if you do
228
166
not already have it, putting it into a ``tarballs`` directory.
294
232
tools/packaging/build-packages.sh
296
#. Upload into the PPA for each release::
298
dput dput ppa:bzr/proposed bzr*1.17-1*.changes
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.
300
245
#. You should soon get an "upload accepted" mail from Launchpad, which
301
246
means that your package is waiting to be built. You can then track its
337
282
summary of current package versions with::
339
284
apt-cache madison bzr
342
Testing the contents of the PPA
343
-------------------------------
345
A somewhat crude but useful way to test the contents of the PPA is to
346
install the relevant packages into an schroot::
348
schroot -c hardy-test -u root -- \
349
apt-get install -o 'APT::Install-Suggests="true"' \
350
-o 'APT::Install-Recommends="true"' \
353
This should make sure everything can be installed; it won't guarantee that
356
Packaging dependencies
357
----------------------
359
Some of our updates to bzr in previous releases require backports of our
360
dependencies. Specific branches holding these backports:
362
* ``lp:~bzr/ubuntu/dapper/configobj/dapper-backport``
added
removed
doc/developers/ppa.txt
