14
14
__ https://help.launchpad.net/PPAQuickStart
16
As of June 2010, there are three PPAs:
16
As of June 2008, there are three PPAs:
18
18
<https://launchpad.net/~bzr/+archive>
19
Final released versions and updates.
21
<https://launchpad.net/~bzr/+archive/proposed>
22
Proposed uploads to move into ~bzr, awaiting testing.
19
Final released versions.
24
21
<https://launchpad.net/~bzr-beta-ppa/+archive>
22
Releases and release candidates.
27
24
<https://launchpad.net/~bzr-nightly-ppa/+archive>
28
25
Automatic nightly builds from trunk.
30
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``.
31
34
If you upload a release-specific version, you should add a suffix to the
32
35
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
34
Dapper uses the ``python-support`` framework and later distributions use
35
``python-central``. This has little effect on everyday packaging but does
36
mean that some of the control files are quite different.
38
37
Every package is first uploaded into the beta ppa. For final release
39
38
versions it is also copied to the main PPA.
41
40
The packaging information is kept in branches of bzr on Launchpad, named
43
<https://code.launchpad.net/~bzr/ubuntu/hardy/bzr/bzr-ppa>.
42
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
45
<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
46
45
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.
56
We build packages for every supported Ubuntu release
57
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
58
when the release passes end-of-life because all users should
59
have upgraded by then.
61
As of August 2010, the following releases are supported:
66
* Jaunty (support ends October 2010)
68
* Dapper LTS (supported but no longer updated for new releases)
77
53
* You must have a GPG key registered to your Launchpad account.
79
On reasonably recent versions of Ubuntu you no longer need special dput
80
configuration, because you can just say ::
82
dput ppa:bzr/proposed <source.changes
85
However, you may still want to add these lines to ``~/.dput.cf`` prevent
86
inadvertently attempting to upload into Ubuntu or Debian, which will
87
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
90
77
default_host_main = notspecified
116
Overview of packaging with builddeb
117
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
119
* First update the oldest supported branch, using ``bzr merge-upstream``.
121
* Run ``bzr builddeb -S -- -sa`` to build a source package, then put
124
(``-S`` says to make a source-only upload, which is
125
required for Launchpad's builders. ``--sa`` says to include the
126
``.orig.tgz`` even if this doesn't seem to be the first upload for an
127
upstream release: this is often needed when rebuilding something that's
128
previously been uploaded to Debian or Ubuntu or into a different PPA.)
130
* Now merge across that change into each supported branch with a
131
simple ``bzr merge``.
133
Locally testing builds
134
~~~~~~~~~~~~~~~~~~~~~~
136
It may be useful to locally test builds inside pbuilder. You may want to
137
use the script from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255165>
140
Update all packages in proposed before copping the main ppa
141
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
143
If one updates bzr, and there are plugins that are not compatible with the
144
new version of bzr, this can cause pain for users using the ppa. In order to
145
avoid this, we first get all packages up to date in the proposed ppa, and then
146
copy them to the main ppa.
157
111
export PACKAGE="bzr"
158
112
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
159
113
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
160
* Optionaly merge debian unstable.
161
114
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh
162
115
~/dev/bzr/bzr.dev/tools/packaging/update-control.sh 1.16 1.17 1.18
163
116
~/dev/bzr/bzr.dev/tools/packaging/build-packages.sh
164
dput ppa:bzr/proposed ${PACKAGE}_$VERSION*.changes
117
dput bzr-beta-ppa ${PACKAGE}_$VERSION*.changes
166
119
Rinse and repeat for all the plugins by changing VERSION and PACKAGE.
204
157
#. Checkout (or update) the packaging branch for each supported release::
206
bzr co lp:~bzr/ubuntu/hardy/bzr/bzr-ppa
159
bzr co lp:~bzr/bzr/packaging-hardy
208
161
There is a script available to help::
210
163
tools/packaging/update-packaging-branches.sh
212
#. Optionaly, merge the Debian unstable branch into each of the packaging
213
branches. You can find the Debian unstable branch here:
214
http://bzr.debian.org/pkg-bazaar/
216
165
#. The ``bzr-builddeb`` step will download the original tarball if you do
217
166
not already have it, putting it into a ``tarballs`` directory.
283
232
tools/packaging/build-packages.sh
285
#. Upload into the PPA for each release::
287
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.
289
245
#. You should soon get an "upload accepted" mail from Launchpad, which
290
246
means that your package is waiting to be built. You can then track its
added
removed
doc/developers/ppa.txt
