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 2010, there are three PPAs:
16
As of January 2011, there are the following PPAs:
18
<https://launchpad.net/~bzr/+archive>
18
<https://launchpad.net/~bzr/+archive/ppa>
19
19
Final released versions and updates.
20
Most users who want updates to bzr should add this.
21
22
<https://launchpad.net/~bzr/+archive/proposed>
22
Proposed uploads to move into ~bzr, awaiting testing.
24
<https://launchpad.net/~bzr-beta-ppa/+archive>
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>
27
<https://launchpad.net/~bzr-nightly-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>
28
37
Automatic nightly builds from trunk.
30
We build a distinct package for each distrorelease.
39
We build a distinct package for each distrorelease.
31
40
If you upload a release-specific version, you should add a suffix to the
32
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
41
package version, e.g. ``1.3-1~bazaar1~dapper1``.
34
43
Dapper uses the ``python-support`` framework and later distributions use
35
44
``python-central``. This has little effect on everyday packaging but does
36
45
mean that some of the control files are quite different.
38
Every package is first uploaded into the beta ppa. For final release
39
versions it is also copied to the main PPA.
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.
41
59
The packaging information is kept in branches of bzr on Launchpad, named
45
63
<lp:~bzr/ubuntu/hardy/bzr/bzr-ppa>. These branches are intended to be used
46
64
with the ``bzr-builddeb`` plugin.
48
**You should almost always upload to the beta ppa first** and then either
49
upload again or copy the packages into the release ppa. That reduces the
50
risk of breaking the main archive from which people get bzr updates.
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.
68
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.
74
* You must have a Launchpad account and be a member of the teams
75
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
94
* You must have a Launchpad account and be a member of the team
95
that owns these PPAs (``~bzr``).
77
97
* You must have a GPG key registered to your Launchpad account.
79
99
On reasonably recent versions of Ubuntu you no longer need special dput
80
100
configuration, because you can just say ::
82
dput ppa:bzr/proposed <source.changes
102
dput ppa:bzr/proposed source.changes
85
105
However, you may still want to add these lines to ``~/.dput.cf`` prevent
90
110
default_host_main = notspecified
92
* Configure ``bzr-builddeb`` to sign the package, which is required for
93
Launchpad to build it. Put this in ``~/.bazaar/builddeb.conf`` ::
96
builder = dpkg-buildpackage -rfakeroot
97
source-builder= dpkg-buildpackage -rfakeroot -S -sa
99
112
* You need a Ubuntu (or probably Debian) machine, and ::
101
114
sudo apt-get install build-essential devscripts dput quilt patch libcrypt-ssleay-perl debhelper cdbs python-docutils
130
141
* Now merge across that change into each supported branch with a
131
142
simple ``bzr merge``.
133
Locally testing builds
134
~~~~~~~~~~~~~~~~~~~~~~
144
Locally testing using pbuilder
145
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
136
147
It may be useful to locally test builds inside pbuilder. You may want to
137
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.
140
Update all packages in proposed before copping the main ppa
141
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
151
Update all packages in proposed before copying to the main ppa
152
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
143
154
If one updates bzr, and there are plugins that are not compatible with the
144
155
new version of bzr, this can cause pain for users using the ppa. In order to
328
339
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
332
356
Packaging dependencies
333
357
----------------------
added
removed
doc/developers/ppa.txt
