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:
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/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/+archive/beta>
21
<https://launchpad.net/~bzr-beta-ppa/+archive>
32
<https://launchpad.net/~bzr/+archive/beta-obsolete>
33
A preserved copy of the final version of packages from
34
~bzr/beta for obsolete Ubuntu series.
36
<https://launchpad.net/~bzr/+archive/daily>
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.
32
We build a distinct package for each distrorelease.
40
33
If you upload a release-specific version, you should add a suffix to the
41
package version, e.g. ``1.3-1~bazaar1~dapper1``.
34
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
43
36
Dapper uses the ``python-support`` framework and later distributions use
44
37
``python-central``. This has little effect on everyday packaging but does
45
38
mean that some of the control files are quite different.
47
Beta releases of bzr and plugins are uploaded into the beta PPA.
49
Final release versions are first uploaded into the proposed PPA, which
50
serves as a staging area to allow for new packages to be tested, and also
51
so that a complete set of Bazaar core and plugin updated versions can be
52
prepared together, when negotiating an API version transition.
54
Once ready, packages can be copied from the proposed PPA to the main PPA
55
using the lp-promote-ppa script found within the hydrazine project. This
56
procedure reduces the risk of broken packages or dependencies between
57
packages in the main PPA from which many people get bzr updates.
40
Every package is first uploaded into the beta ppa. For final release
41
versions it is also copied to the main PPA.
59
43
The packaging information is kept in branches of bzr on Launchpad, named
61
<https://code.launchpad.net/~bzr/ubuntu/hardy/bzr/bzr-ppa>.
45
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
63
<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
64
48
with the ``bzr-builddeb`` plugin.
66
The page <http://wiki.bazaar.canonical.com/PpaPackagingBranches> is a
67
reference to where the PPA packaging branches for each of the source
68
packages in the ``~bzr`` PPAs may be found.
74
We build packages for every supported Ubuntu release
75
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
76
when the release passes end-of-life because all users should
77
have upgraded by then.
79
As of August 2010, the following releases are supported:
84
* Jaunty (support ends October 2010)
86
* Dapper LTS (supported but no longer updated for new releases)
88
The ``rmadison bzr`` command will gives you an up-to-date summary
89
of which bzr releases are current in each Ubuntu release.
50
**You should almost always upload to the beta ppa first** and then either
51
upload again or copy the packages into the release ppa. That reduces the
52
risk of breaking the main archive from which people get bzr updates.
94
* You must have a Launchpad account and be a member of the team
95
that owns these PPAs (``~bzr``).
57
* You must have a Launchpad account and be a member of the teams
58
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
97
60
* You must have a GPG key registered to your Launchpad account.
99
62
On reasonably recent versions of Ubuntu you no longer need special dput
100
63
configuration, because you can just say ::
102
dput ppa:bzr/proposed source.changes
65
dput ppa:bzr/2.1-proposed <source.changes
105
68
However, you may still want to add these lines to ``~/.dput.cf`` prevent
141
113
* Now merge across that change into each supported branch with a
142
114
simple ``bzr merge``.
144
Locally testing using pbuilder
145
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
116
Locally testing builds
117
~~~~~~~~~~~~~~~~~~~~~~
147
119
It may be useful to locally test builds inside pbuilder. You may want to
148
120
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.
294
253
tools/packaging/build-packages.sh
296
#. Upload into the PPA for each release::
298
dput dput ppa:bzr/proposed bzr*1.17-1*.changes
255
#. Upload into the beta PPA for each release::
257
dput bzr-beta-ppa bzr*1.17-1*.changes
259
#. For final release versions, also copy it into the ``~bzr`` PPA::
261
dput bzr-ppa ../bzr_1.17-1\~bazaar1\~hardy1\_source.changes
263
Alternatively, you can use Launchpad's "copy" feature to copy the
264
packages between repositories.
300
266
#. You should soon get an "upload accepted" mail from Launchpad, which
301
267
means that your package is waiting to be built. You can then track its
302
progress in <https://launchpad.net/~bzr/+archive/proposed> and
303
<https://launchpad.net/~bzr/+archive/proposed/+builds>.
268
progress in <https://launchpad.net/~bzr-beta-ppa/+archive> and
269
<https://launchpad.net/~bzr-beta-ppa/+archive/+builds>.
306
272
Packaging bzr-svn
added
removed
doc/developers/ppa.txt
