14
14
__ https://help.launchpad.net/PPAQuickStart
16
As of June 2008, there are three PPAs:
16
As of June 2008, there are two PPAs:
18
18
<https://launchpad.net/~bzr/+archive>
19
19
Final released versions.
21
21
<https://launchpad.net/~bzr-beta-ppa/+archive>
22
22
Releases and release candidates.
24
<https://launchpad.net/~bzr-nightly-ppa/+archive>
25
Automatic nightly builds from trunk.
27
24
We build packages for every supported Ubuntu release
28
25
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
29
26
when the release passes end-of-life because all users should
37
34
Every package is first uploaded into the beta ppa. For final release
38
35
versions it is also copied to the main PPA.
40
The packaging information is kept in branches of bzr on Launchpad, named
37
The ``debian/`` directory containing the packaging information is kept in
38
branches on Launchpad, named like
42
39
<https://code.launchpad.net/~bzr/bzr/packaging-hardy>.
44
<lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used
45
with the ``bzr-builddeb`` plugin.
41
<lp:~bzr/bzr/packaging-hardy>.
77
73
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
86
75
* You need a Ubuntu (or probably Debian) machine, and ::
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
77
sudo apt-get install build-essential devscripts dput quilt patch
79
* You will also want to have the ``bzr-builddeb`` plugin installed.
107
89
release packages is as simple as::
109
91
cd ~/dev/bzr/releases/packaging
110
ln ~/dev/bzr/releases/bzr-1.6.tar.gz ./bzr_1.6.orig.tar.gz
111
92
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
112
93
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
113
94
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
114
95
~/dev/bzr/bzr.dev/tools/packaging/build-packages
115
dput bzr-beta-ppa bzr_1.6~beta3-1~bazaar1*.changes
96
dput bzr-beta-ppa build-area/bzr_1.6~beta3~bazaar1*.changes
120
101
#. You will end up checking out a separate directory for each supported
121
release. Such as ``~/dev/bzr/releases/packaging/hardy``. In each of these
122
branches, you will produce the package for the release.
102
release. Such as ``~/dev/bzr/releases/packaging/hardy``
124
104
#. Decide on the final version number. It should be of this form::
126
106
bzr-1.6~beta3-1~bazaar1~hardy1
128
**Note:** There are three hyphen-separated parts: the *package name*,
129
the *upstream version*, and the *packaging version*.
108
There are three hyphen-separated parts: the *package name*, the *upstream
109
version*, and the *packaging version*.
131
111
**Caution:** Upstream betas or release candidates must insert a tilde
132
112
to make them sort before the final release, like this:
138
118
#. Export the distroreleases that you will be packaging for::
140
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid jaunty"
120
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
142
122
#. Checkout (or update) the packaging branch for each supported release::
148
128
tools/packaging/update-packaging-branches.sh
150
130
#. The ``bzr-builddeb`` step will download the original tarball if you do
151
not already have it, putting it into a ``tarballs`` directory.
131
not already have it. Putting it into a ``tarballs`` directory.
153
133
#. For Bazaar plugins, change the ``debian/control`` file to express a
154
134
dependency on the correct version of ``bzr``.
167
147
against the version number (which is just our convention), so make sure
170
Make sure you have the correct email address for yourself (you may need
171
export DEBEMAIL=`bzr whoami` if it isn't already set), version number, and
172
distribution. It should look something like this::
150
Make sure you have the correct email address for yourself, version
151
number, and distribution. It should look something like this::
174
153
bzr (1.6~beta3-1~bazaar1~hardy1) hardy; urgency=low
201
180
cd packaging-$DISTRO; bzr builddeb -S
203
This will create a ``.changes`` file. If you didn't configure builddeb
204
to automatically sign them, you can use ::
206
debsign -m$UID *.changes
208
where ``$UID`` is the gpg key you want to use to sign the changes.
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.
210
197
#. Upload into the beta PPA for each release::
212
dput bzr-beta-ppa bzr_1.6-1*.changes
199
dput bzr-beta-ppa build-area/*.changes
214
201
#. For final release versions, also copy it into the ``~bzr`` PPA::
216
dput bzr-ppa ../bzr_1.6-1\~bazaar1\~hardy1\_source.changes
203
dput bzr-ppa ../bzr__1.6-1\~bazaar1\~hardy1\_source.changes
218
205
Alternatively, you can use Launchpad's "copy" feature to copy the
219
206
packages between repositories.
224
211
<https://launchpad.net/~bzr-beta-ppa/+archive/+builds>.
230
bzr-svn uses a packaging branch that contains both the source
231
(including any changes against upstream) and the ``debian/`` directory.
235
#. Get a checkout of ``lp:~bzr/bzr-svn/hardy-ppa/``
237
#. Merge from ``http://bzr.debian.org/pkg-bazaar/bzr-svn/experimental/``
239
This should bring in both upstream and packaging changes for the new
240
release, and it's updated as part of the bzr-svn release process.
242
#. Run ``dch -v 0.4.15-1~bazaar1-hardy1 -D hardy`` or similar
244
#. Run ``bzr builddeb --source``
246
bzr-builddeb will automatically check out the appropriate tag from the
247
main branch of bzr-svn, build, and package it.
249
#. ``dput bzr-beta-ppa ../bzr-svn_0.4.15-1~bazaar1~hardy1_source.changes``
252
214
Monitoring the contents of PPAs
253
215
-------------------------------
added
removed
doc/developers/ppa.txt
