14
14
__ https://help.launchpad.net/PPAQuickStart
16
As of June 2008, there are three PPAs:
16
As of June 2010, there are three PPAs:
18
18
<https://launchpad.net/~bzr/+archive>
19
Final released versions.
19
Final released versions and updates.
21
<https://launchpad.net/~bzr/+archive/proposed>
22
Proposed uploads to move into ~bzr, awaiting testing.
21
24
<https://launchpad.net/~bzr-beta-ppa/+archive>
22
Releases and release candidates.
24
27
<https://launchpad.net/~bzr-nightly-ppa/+archive>
25
28
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``.
30
We build a distinct package for each distrorelease.
34
31
If you upload a release-specific version, you should add a suffix to the
35
32
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.
37
38
Every package is first uploaded into the beta ppa. For final release
38
39
versions it is also copied to the main PPA.
40
41
The packaging information is kept in branches of bzr on Launchpad, named
42
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
43
<https://code.launchpad.net/~bzr/ubuntu/hardy/bzr/bzr-ppa>.
44
<lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used
45
<lp:~bzr/ubuntu/hardy/bzr/bzr-ppa>. These branches are intended to be used
45
46
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)
50
* You must have a Launchpad account and be a member of the teams
74
* You must have a Launchpad account and be a member of the teams
51
75
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
53
77
* 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
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::
77
90
default_host_main = notspecified
79
92
* Configure ``bzr-builddeb`` to sign the package, which is required for
80
93
Launchpad to build it. Put this in ``~/.bazaar/builddeb.conf`` ::
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.
107
153
release packages is as simple as::
109
155
cd ~/dev/bzr/releases/packaging
110
ln ~/dev/bzr/releases/bzr-1.6.tar.gz ./bzr_1.6.orig.tar.gz
111
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
156
export VERSION="1.17~rc1-1~bazaar1"
158
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
112
159
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
113
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
114
~/dev/bzr/bzr.dev/tools/packaging/build-packages
115
dput bzr-beta-ppa bzr_1.6~beta3-1~bazaar1*.changes
160
* Optionaly merge debian unstable.
161
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh
162
~/dev/bzr/bzr.dev/tools/packaging/update-control.sh 1.16 1.17 1.18
163
~/dev/bzr/bzr.dev/tools/packaging/build-packages.sh
164
dput ppa:bzr/proposed ${PACKAGE}_$VERSION*.changes
166
Rinse and repeat for all the plugins by changing VERSION and PACKAGE.
121
172
release. Such as ``~/dev/bzr/releases/packaging/hardy``. In each of these
122
173
branches, you will produce the package for the release.
175
The scripts will also create the branches and produce packages for
176
bzrtools and bzr-svn.
124
178
#. Decide on the final version number. It should be of this form::
126
bzr-1.6~beta3-1~bazaar1~hardy1
180
bzr-1.17~rc1-1~bazaar1~hardy1
128
182
**Note:** There are three hyphen-separated parts: the *package name*,
129
183
the *upstream version*, and the *packaging version*.
131
185
**Caution:** Upstream betas or release candidates must insert a tilde
132
186
to make them sort before the final release, like this:
133
``bzr-1.6~beta3-1~bazaar1~hardy1``.
187
``bzr-1.17~rc1-1~bazaar1~hardy1``.
135
189
Final releases will use a release string of the form:
136
``bzr-1.6-1~bazaar1~hardy1``
190
``bzr-1.17-1~bazaar1~hardy1``
192
Set this base of this up as a usable environment variable::
194
export VERSION="1.17~rc1-1~bazaar1"
138
196
#. Export the distroreleases that you will be packaging for::
140
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid jaunty"
198
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
200
#. Export the program you are packaging::
142
204
#. Checkout (or update) the packaging branch for each supported release::
144
bzr co lp:~bzr/bzr/packaging-hardy
206
bzr co lp:~bzr/ubuntu/hardy/bzr/bzr-ppa
146
208
There is a script available to help::
148
210
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/
150
216
#. The ``bzr-builddeb`` step will download the original tarball if you do
151
217
not already have it, putting it into a ``tarballs`` directory.
156
222
For bzrtools this is typically::
158
Build-Depends-Indep: bzr (>= 1.6~), rsync
159
Depends: ${python:Depends}, bzr (>= 1.6~), bzr (<< 1.7~), patch
224
Build-Depends-Indep: bzr (>= 1.17~), rsync
225
Depends: ${python:Depends}, bzr (>= 1.17~), bzr (<< 1.18~), patch
227
There is a helper script which will update the control file and commit it
228
for all of your ``$UBUNTU_RELEASES``. It is available as::
230
tools/packaging/update-control.sh
232
You must supply the versions as arguments as follows
233
OLD_VERSION CURRENT_VERSION NEXT_VERSION, such as::
235
tools/packaging/update-control.sh 1.16 1.17 1.18
161
237
#. Make a new ``debian/changelog`` entry for the new release,
162
238
either by using ``dch`` or just editing the file::
164
dch -v '1.6~beta3-1~bazaar1~hardy1' -D hardy
240
dch -v '1.17~rc1-1~bazaar1~hardy1' -D hardy
166
242
dch will default to the distro you're working in and this isn't checked
167
against the version number (which is just our convention), so make sure
243
against the version number (which is just our convention), so make sure
170
246
Make sure you have the correct email address for yourself (you may need
171
247
export DEBEMAIL=`bzr whoami` if it isn't already set), version number, and
172
248
distribution. It should look something like this::
174
bzr (1.6~beta3-1~bazaar1~hardy1) hardy; urgency=low
250
bzr (1.17~rc1-1~bazaar1~hardy1) hardy; urgency=low
176
252
* New upstream release.
178
254
-- John Sample <sample@example.com> Mon, 31 Mar 2008 12:36:27 +1100
180
256
If you need to upload the package again to fix a problem, normally you
186
262
You will also want to commit these changes into the packaging branch.
188
There is a helper script which will update the changelog and commit it
264
There is a helper script which will build all the packages
189
265
for all of your ``$UBUNTU_RELEASES``. It is available as::
191
267
tools/packaging/update-changelogs.sh
193
You must supply the release string, such as::
195
tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
197
It will automatically append the distro numbering on the end.
199
269
#. Build the source packages::
201
cd packaging-$DISTRO; bzr builddeb -S
271
cd bzr-$DISTRO; bzr builddeb -S
203
273
This will create a ``.changes`` file. If you didn't configure builddeb
204
274
to automatically sign them, you can use ::
208
278
where ``$UID`` is the gpg key you want to use to sign the changes.
210
#. Upload into the beta PPA for each release::
212
dput bzr-beta-ppa bzr_1.6-1*.changes
214
#. For final release versions, also copy it into the ``~bzr`` PPA::
216
dput bzr-ppa ../bzr_1.6-1\~bazaar1\~hardy1\_source.changes
218
Alternatively, you can use Launchpad's "copy" feature to copy the
219
packages between repositories.
280
There is a helper script which will build the package
281
for all of your ``$UBUNTU_RELEASES``. It is available as::
283
tools/packaging/build-packages.sh
285
#. Upload into the PPA for each release::
287
dput dput ppa:bzr/proposed bzr*1.17-1*.changes
221
289
#. You should soon get an "upload accepted" mail from Launchpad, which
222
290
means that your package is waiting to be built. You can then track its
227
295
Packaging bzr-svn
228
296
~~~~~~~~~~~~~~~~~
230
bzr-svn uses a packaging branch that contains both the source
298
bzr-svn uses a packaging branch that contains both the source
231
299
(including any changes against upstream) and the ``debian/`` directory.
233
301
To build bzr-svn:
235
303
#. Get a checkout of ``lp:~bzr/bzr-svn/hardy-ppa/``
237
#. Merge from ``http://bzr.debian.org/pkg-bazaar/bzr-svn/experimental/``
305
#. Merge from ``http://bzr.debian.org/pkg-bazaar/bzr-svn/unstable/``
239
307
This should bring in both upstream and packaging changes for the new
240
308
release, and it's updated as part of the bzr-svn release process.
310
It's quite possible you will need to resolve some conflicts.
242
312
#. Run ``dch -v 0.4.15-1~bazaar1-hardy1 -D hardy`` or similar
244
314
#. Run ``bzr builddeb --source``
added
removed
doc/developers/ppa.txt
