14
14
__ https://help.launchpad.net/PPAQuickStart
16
As of June 2008, there are two PPAs:
16
As of June 2008, there are three PPAs:
18
18
<https://launchpad.net/~bzr/+archive>
19
19
Final released versions.
21
21
<https://launchpad.net/~bzr-beta-ppa/+archive>
22
Releases and release candidates.
22
Releases and release candidates.
24
<https://launchpad.net/~bzr-nightly-ppa/+archive>
25
Automatic nightly builds from trunk.
24
27
We build packages for every supported Ubuntu release
25
28
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
34
37
Every package is first uploaded into the beta ppa. For final release
35
38
versions it is also copied to the main PPA.
37
The ``debian/`` directory containing the packaging information is kept in
38
branches on Launchpad, named like
40
The packaging information is kept in branches of bzr on Launchpad, named
39
42
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
41
<lp:~bzr/bzr/packaging-hardy>.
44
<lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used
45
with the ``bzr-builddeb`` plugin.
46
* You must have a Launchpad account and be a member of the teams
50
* You must have a Launchpad account and be a member of the teams
47
51
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
49
53
* You must have a GPG key registered to your Launchpad account.
73
77
default_host_main = notspecified
79
* Configure ``bzr-builddeb`` to sign the package, which is required for
80
Launchpad to build it. Put this in ``~/.bazaar/builddeb.conf`` ::
83
builder = dpkg-buildpackage -rfakeroot
84
source-builder= dpkg-buildpackage -rfakeroot -S -sa
75
86
* You need a Ubuntu (or probably Debian) machine, and ::
77
sudo apt-get install build-essential devscripts dput quilt patch
79
* You will also want to have the ``bzr-builddeb`` plugin installed.
88
sudo apt-get install build-essential devscripts dput quilt patch libcrypt-ssleay-perl debhelper cdbs python-docutils
90
Please update this document if you encounter unmet dependencies or find a
91
shorter way to express them.
93
* You will also want to have the `bzr-builddeb`_ plugin installed, which
94
depends on `bzrtools`_.
96
.. _`bzr-builddeb`: http://launchpad.net/bzr-builddeb
97
.. _`bzrtools`: http://launchpad.net/bzrtools
89
107
release packages is as simple as::
91
109
cd ~/dev/bzr/releases/packaging
92
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
110
export VERSION="1.17~rc1-1~bazaar1"
112
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
93
113
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
94
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
95
~/dev/bzr/bzr.dev/tools/packaging/build-packages
96
dput bzr-beta-ppa build-area/bzr_1.6~beta3~bazaar1*.changes
114
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh
115
~/dev/bzr/bzr.dev/tools/packaging/update-control.sh 1.16 1.17 1.18
116
~/dev/bzr/bzr.dev/tools/packaging/build-packages.sh
117
dput bzr-beta-ppa ${PACKAGE}_$VERSION*.changes
119
Rinse and repeat for all the plugins by changing VERSION and PACKAGE.
101
124
#. You will end up checking out a separate directory for each supported
102
release. Such as ``~/dev/bzr/releases/packaging/hardy``
125
release. Such as ``~/dev/bzr/releases/packaging/hardy``. In each of these
126
branches, you will produce the package for the release.
128
The scripts will also create the branches and produce packages for
129
bzrtools and bzr-svn.
104
131
#. Decide on the final version number. It should be of this form::
106
bzr-1.6~beta3-1~bazaar1~hardy1
133
bzr-1.17~rc1-1~bazaar1~hardy1
108
There are three hyphen-separated parts: the *package name*, the *upstream
109
version*, and the *packaging version*.
135
**Note:** There are three hyphen-separated parts: the *package name*,
136
the *upstream version*, and the *packaging version*.
111
138
**Caution:** Upstream betas or release candidates must insert a tilde
112
139
to make them sort before the final release, like this:
113
``bzr-1.6~beta3-1~bazaar1~hardy1``.
140
``bzr-1.17~rc1-1~bazaar1~hardy1``.
115
142
Final releases will use a release string of the form:
116
``bzr-1.6-1~bazaar1~hardy1``
143
``bzr-1.17-1~bazaar1~hardy1``
145
Set this base of this up as a usable environment variable::
147
export VERSION="1.17~rc1-1~bazaar1"
118
149
#. Export the distroreleases that you will be packaging for::
120
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
151
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
153
#. Export the program you are packaging::
122
157
#. Checkout (or update) the packaging branch for each supported release::
128
163
tools/packaging/update-packaging-branches.sh
130
165
#. The ``bzr-builddeb`` step will download the original tarball if you do
131
not already have it. Putting it into a ``tarballs`` directory.
166
not already have it, putting it into a ``tarballs`` directory.
133
168
#. For Bazaar plugins, change the ``debian/control`` file to express a
134
169
dependency on the correct version of ``bzr``.
136
171
For bzrtools this is typically::
138
Build-Depends-Indep: bzr (>= 1.6~), rsync
139
Depends: ${python:Depends}, bzr (>= 1.6~), bzr (<< 1.7~), patch
173
Build-Depends-Indep: bzr (>= 1.17~), rsync
174
Depends: ${python:Depends}, bzr (>= 1.17~), bzr (<< 1.18~), patch
176
There is a helper script which will update the control file and commit it
177
for all of your ``$UBUNTU_RELEASES``. It is available as::
179
tools/packaging/update-control.sh
181
You must supply the versions as arguments as follows
182
OLD_VERSION CURRENT_VERSION NEXT_VERSION, such as::
184
tools/packaging/update-control.sh 1.16 1.17 1.18
141
186
#. Make a new ``debian/changelog`` entry for the new release,
142
187
either by using ``dch`` or just editing the file::
144
dch -v '1.6~beta3-1~bazaar1~hardy1' -D hardy
189
dch -v '1.17~rc1-1~bazaar1~hardy1' -D hardy
146
191
dch will default to the distro you're working in and this isn't checked
147
against the version number (which is just our convention), so make sure
192
against the version number (which is just our convention), so make sure
150
Make sure you have the correct email address for yourself, version
151
number, and distribution. It should look something like this::
153
bzr (1.6~beta3-1~bazaar1~hardy1) hardy; urgency=low
195
Make sure you have the correct email address for yourself (you may need
196
export DEBEMAIL=`bzr whoami` if it isn't already set), version number, and
197
distribution. It should look something like this::
199
bzr (1.17~rc1-1~bazaar1~hardy1) hardy; urgency=low
155
201
* New upstream release.
157
203
-- John Sample <sample@example.com> Mon, 31 Mar 2008 12:36:27 +1100
159
205
If you need to upload the package again to fix a problem, normally you
165
211
You will also want to commit these changes into the packaging branch.
167
There is a helper script which will update the changelog and commit it
213
There is a helper script which will build all the packages
168
214
for all of your ``$UBUNTU_RELEASES``. It is available as::
170
216
tools/packaging/update-changelogs.sh
172
You must supply the release string, such as::
174
tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
176
It will automatically append the distro numbering on the end.
178
218
#. Build the source packages::
180
220
cd packaging-$DISTRO; bzr builddeb -S
182
This will create a ``.changes`` file in ``build-area``. You will need
185
debsign -m$UID build-area/*.changes
187
Where ``$UID`` is the gpg key you want to use to sign the changes.
188
Alternatively, you can configure ``~/.bazaar/builddeb.conf`` with::
191
builder = dpkg-buildpackage -rfakeroot
192
source-builder= dpkg-buildpackage -rfakeroot -S -sa
194
Which tells ``bzr builddeb`` to automatically sign the package with the
195
key associated with the user who created the changelog entry.
222
This will create a ``.changes`` file. If you didn't configure builddeb
223
to automatically sign them, you can use ::
225
debsign -m$UID *.changes
227
where ``$UID`` is the gpg key you want to use to sign the changes.
229
There is a helper script which will build the package
230
for all of your ``$UBUNTU_RELEASES``. It is available as::
232
tools/packaging/build-packages.sh
197
234
#. Upload into the beta PPA for each release::
199
dput bzr-beta-ppa build-area/*.changes
236
dput bzr-beta-ppa bzr*1.17-1*.changes
201
238
#. For final release versions, also copy it into the ``~bzr`` PPA::
203
dput bzr-ppa ../bzr__1.6-1\~bazaar1\~hardy1\_source.changes
240
dput bzr-ppa ../bzr_1.17-1\~bazaar1\~hardy1\_source.changes
205
242
Alternatively, you can use Launchpad's "copy" feature to copy the
206
243
packages between repositories.
211
248
<https://launchpad.net/~bzr-beta-ppa/+archive/+builds>.
254
bzr-svn uses a packaging branch that contains both the source
255
(including any changes against upstream) and the ``debian/`` directory.
259
#. Get a checkout of ``lp:~bzr/bzr-svn/hardy-ppa/``
261
#. Merge from ``http://bzr.debian.org/pkg-bazaar/bzr-svn/unstable/``
263
This should bring in both upstream and packaging changes for the new
264
release, and it's updated as part of the bzr-svn release process.
266
It's quite possible you will need to resolve some conflicts.
268
#. Run ``dch -v 0.4.15-1~bazaar1-hardy1 -D hardy`` or similar
270
#. Run ``bzr builddeb --source``
272
bzr-builddeb will automatically check out the appropriate tag from the
273
main branch of bzr-svn, build, and package it.
275
#. ``dput bzr-beta-ppa ../bzr-svn_0.4.15-1~bazaar1~hardy1_source.changes``
214
278
Monitoring the contents of PPAs
215
279
-------------------------------
added
removed
doc/developers/ppa.txt
