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
Releases and release candidates.
24
<https://launchpad.net/~bzr-nightly-ppa/+archive>
25
Automatic nightly builds from trunk.
22
Releases and release candidates.
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
30
27
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``.
34
If you upload a release-specific version, you should add a suffix to the
29
We build a distinct package for each distrorelease that has
30
different packaging requirements. As of bzr 1.5, Dapper uses
31
``python-support`` and later distributions use ``python-central``, so we
32
build one version for dapper and one version for everything else. If you
33
upload a release-specific version, you should add a suffix to the
35
34
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
37
Every package is first uploaded into the beta ppa. For final release
38
versions it is also copied to the main PPA.
36
Every package is first uploaded into one distroversion of the beta ppa.
37
It can then be copied to other compatible distroversions. For final
38
release versions it is also copied to the main PPA.
40
The packaging information is kept in branches of bzr on Launchpad, named
40
The ``debian/`` directory containing the packaging information is kept in
41
branches on Launchpad, named like
42
42
<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.
50
* You must have a Launchpad account and be a member of the teams
47
* You must have a Launchpad account and be a member of the teams
51
48
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
53
50
* You must have a GPG key registered to your Launchpad account.
77
74
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
77
fqdn = SPECIFY.A.PPA.NAME
86
79
* 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
81
sudo apt-get install build-essential devscripts dput quilt patch
106
For people who have already set up everything they need, building the
107
release packages is as simple as::
109
cd ~/dev/bzr/releases/packaging
110
export VERSION="1.17~rc1-1~bazaar1"
112
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
113
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
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.
124
#. You will end up checking out a separate directory for each supported
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.
86
#. You will need a working directory for each supported release, such as
87
``~/bzr/Packaging/hardy``
89
#. Download the official tarball of the release to e.g. ``~/bzr/Releases``
90
if you don't already have it.
131
92
#. Decide on the final version number. It should be of this form::
133
bzr-1.17~rc1-1~bazaar1~hardy1
94
bzr-1.6~beta3-1~bazaar1
135
**Note:** There are three hyphen-separated parts: the *package name*,
136
the *upstream version*, and the *packaging version*.
96
There are three hyphen-separated parts: the *package name*, the *upstream
97
version*, and the *packaging version*.
138
99
**Caution:** Upstream betas or release candidates must insert a tilde
139
100
to make them sort before the final release, like this:
140
``bzr-1.17~rc1-1~bazaar1~hardy1``.
142
Final releases will use a release string of the form:
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"
149
#. Export the distroreleases that you will be packaging for::
151
export UBUNTU_RELEASES="dapper hardy intrepid jaunty karmic"
153
#. Export the program you are packaging::
157
#. Checkout (or update) the packaging branch for each supported release::
159
bzr co lp:~bzr/bzr/packaging-hardy
161
There is a script available to help::
163
tools/packaging/update-packaging-branches.sh
165
#. The ``bzr-builddeb`` step will download the original tarball if you do
166
not already have it, putting it into a ``tarballs`` directory.
101
``bzr-1.4~rc2-1~bazaar1``.
103
#. Copy or hardlink the original tarball into your per-disto directory, under an
104
appropriate name ending in ``.orig.tar.gz``. Untar it. The extracted
105
source directory and ``.orig`` file must match the version number you
106
calculated above. For example::
108
cp -l ~/bzr/Releases/bzr-1.6b3.tar.gz bzr_1.6~beta3.orig.tar.gz
109
tar xfvz bzr_1.6~beta3.orig.tar.gz
110
mv bzr-1.6b3 bzr-1.6~beta3
112
#. Change into that directory and check out the packaging branch::
116
bzr+ssh://bazaar.launchpad.net/~bzr/bzr/packaging-hardy \
168
119
#. For Bazaar plugins, change the ``debian/control`` file to express a
169
120
dependency on the correct version of ``bzr``.
171
122
For bzrtools this is typically::
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
124
Build-Depends-Indep: bzr (>= 1.3~), rsync
125
Depends: ${python:Depends}, bzr (>= 1.3~), bzr (<< 1.4~), patch
186
127
#. Make a new ``debian/changelog`` entry for the new release,
187
128
either by using ``dch`` or just editing the file::
189
dch -v '1.17~rc1-1~bazaar1~hardy1' -D hardy
130
dch -v '1.3-1~bazaar1' -D hardy
191
132
dch will default to the distro you're working in and this isn't checked
192
against the version number (which is just our convention), so make sure
133
against the version number (which is just our conversion), so make sure
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
136
Make sure you have the correct email address for yourself, version
137
number, and distribution. It should look something like this::
139
bzr (1.3-1~bazaar1) hardy; urgency=low
201
141
* New upstream release.
203
143
-- John Sample <sample@example.com> Mon, 31 Mar 2008 12:36:27 +1100
205
145
If you need to upload the package again to fix a problem, normally you
208
148
that the distro name in the version is consistent with the target name
209
149
outside the parenthesis.
211
You will also want to commit these changes into the packaging branch.
213
There is a helper script which will build all the packages
214
for all of your ``$UBUNTU_RELEASES``. It is available as::
216
tools/packaging/update-changelogs.sh
218
#. Build the source packages::
220
cd packaging-$DISTRO; bzr builddeb -S
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
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.
151
#. Commit these changes into the packaging branch::
153
bzr ci -m '1.3-1~bazaar1: New upstream release.' debian
155
#. Build a source package::
159
This will create a ``.changes`` file in the per-distro directory,
160
and should invoke gpg to sign it with your key.
161
Check that file is reasonable: it should be uploading to the intended
162
distribution, have a .orig file included, and the right version number.
164
#. Upload into the beta PPA::
166
dput bzr-beta-ppa ../bzr__1.3-1\~bazaar1\_source.changes
168
#. Copy the uploaded package over to other Ubuntu releases, taking advantage
169
of Launchpad's Copy Package feature
170
<https://launchpad.net/~bzr-beta-ppa/+archive/+copy-packages>
172
#. For final release versions, also copy it into the ``~bzr`` PPA.
245
174
#. You should soon get an "upload accepted" mail from Launchpad, which
246
175
means that your package is waiting to be built. You can then track its
added
removed
doc/developers/ppa.txt
