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.
24
27
We build packages for every supported Ubuntu release
25
28
<https://wiki.ubuntu.com/Releases>. Packages need no longer be updated
26
29
when the release passes end-of-life because all users should
27
30
have upgraded by then. (As of May 2008, Edgy Eft is no longer supported.)
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
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
34
35
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
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.
37
Every package is first uploaded into the beta ppa. For final release
38
versions it is also copied to the main PPA.
40
The ``debian/`` directory containing the packaging information is kept in
41
branches on Launchpad, named like
40
The packaging information is kept in branches of bzr on Launchpad, named
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.
74
77
default_host_main = notspecified
77
fqdn = SPECIFY.A.PPA.NAME
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
79
86
* You need a Ubuntu (or probably Debian) machine, and ::
81
88
sudo apt-get install build-essential devscripts dput quilt patch
90
* You will also want to have the `bzr-builddeb`_ plugin installed, which
91
depends on `bzrtools`_.
93
.. _`bzr-builddeb`: http://launchpad.net/bzr-builddeb
94
.. _`bzrtools`: http://launchpad.net/bzrtools
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.
103
For people who have already set up everything they need, building the
104
release packages is as simple as::
106
cd ~/dev/bzr/releases/packaging
107
ln ~/dev/bzr/releases/bzr-1.6.tar.gz ./bzr_1.6.orig.tar.gz
108
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
109
~/dev/bzr/bzr.dev/tools/packaging/update-packaging-branches.sh
110
~/dev/bzr/bzr.dev/tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
111
~/dev/bzr/bzr.dev/tools/packaging/build-packages
112
dput bzr-beta-ppa bzr_1.6~beta3-1~bazaar1*.changes
117
#. You will end up checking out a separate directory for each supported
118
release. Such as ``~/dev/bzr/releases/packaging/hardy``
92
120
#. Decide on the final version number. It should be of this form::
94
bzr-1.6~beta3-1~bazaar1
122
bzr-1.6~beta3-1~bazaar1~hardy1
96
There are three hyphen-separated parts: the *package name*, the *upstream
97
version*, and the *packaging version*.
124
**Note:** There are three hyphen-separated parts: the *package name*,
125
the *upstream version*, and the *packaging version*.
99
127
**Caution:** Upstream betas or release candidates must insert a tilde
100
128
to make them sort before the final release, like this:
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 \
129
``bzr-1.6~beta3-1~bazaar1~hardy1``.
131
Final releases will use a release string of the form:
132
``bzr-1.6-1~bazaar1~hardy1``
134
#. Export the distroreleases that you will be packaging for::
136
export UBUNTU_RELEASES="dapper feisty gutsy hardy intrepid"
138
#. Checkout (or update) the packaging branch for each supported release::
140
bzr co lp:~bzr/bzr/packaging-hardy
142
There is a script available to help::
144
tools/packaging/update-packaging-branches.sh
146
#. The ``bzr-builddeb`` step will download the original tarball if you do
147
not already have it, putting it into a ``tarballs`` directory.
119
149
#. For Bazaar plugins, change the ``debian/control`` file to express a
120
150
dependency on the correct version of ``bzr``.
122
152
For bzrtools this is typically::
124
Build-Depends-Indep: bzr (>= 1.3~), rsync
125
Depends: ${python:Depends}, bzr (>= 1.3~), bzr (<< 1.4~), patch
154
Build-Depends-Indep: bzr (>= 1.6~), rsync
155
Depends: ${python:Depends}, bzr (>= 1.6~), bzr (<< 1.7~), patch
127
157
#. Make a new ``debian/changelog`` entry for the new release,
128
158
either by using ``dch`` or just editing the file::
130
dch -v '1.3-1~bazaar1' -D hardy
160
dch -v '1.6~beta3-1~bazaar1~hardy1' -D hardy
132
162
dch will default to the distro you're working in and this isn't checked
133
against the version number (which is just our conversion), so make sure
163
against the version number (which is just our convention), so make sure
136
166
Make sure you have the correct email address for yourself, version
137
167
number, and distribution. It should look something like this::
139
bzr (1.3-1~bazaar1) hardy; urgency=low
169
bzr (1.6~beta3-1~bazaar1~hardy1) hardy; urgency=low
141
171
* New upstream release.
148
178
that the distro name in the version is consistent with the target name
149
179
outside the parenthesis.
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.
181
You will also want to commit these changes into the packaging branch.
183
There is a helper script which will update the changelog and commit it
184
for all of your ``$UBUNTU_RELEASES``. It is available as::
186
tools/packaging/update-changelogs.sh
188
You must supply the release string, such as::
190
tools/packaging/update-changelogs.sh 1.6~beta3-1~bazaar1
192
It will automatically append the distro numbering on the end.
194
#. Build the source packages::
196
cd packaging-$DISTRO; bzr builddeb -S
198
This will create a ``.changes`` file. If you didn't configure builddeb
199
to automatically sign them, you can use ::
201
debsign -m$UID *.changes
203
where ``$UID`` is the gpg key you want to use to sign the changes.
205
#. Upload into the beta PPA for each release::
207
dput bzr-beta-ppa bzr_1.6-1*.changes
209
#. For final release versions, also copy it into the ``~bzr`` PPA::
211
dput bzr-ppa ../bzr_1.6-1\~bazaar1\~hardy1\_source.changes
213
Alternatively, you can use Launchpad's "copy" feature to copy the
214
packages between repositories.
174
216
#. You should soon get an "upload accepted" mail from Launchpad, which
175
217
means that your package is waiting to be built. You can then track its
177
219
<https://launchpad.net/~bzr-beta-ppa/+archive/+builds>.
225
bzr-svn uses bzr-builddeb in "split" mode, where the packaging branch
226
contains both the source and the ``debian/`` directory, and the
227
``orig.tar.gz`` is split off when building the packgae.
231
#. Get a checkout of ``lp:~bzr/bzr-svn/hardy-ppa/``
233
#. Merge from ``http://bzr.debian.org/pkg-bazaar/bzr-svn/experimental/``
235
This should bring in both upstream and packaging changes for the new
236
release, and it's updated as part of the bzr-svn release process.
238
#. ``export UPSTREAM_VERSION=bzr-svn-0.4.15`` or similar
240
#. Run ``dch -v 0.4.15-1~bazaar1-hardy1 -D hardy`` or similar
242
#. Run ``bzr builddeb --source``
244
bzr-builddeb will automatically check out the appropriate tag from the
245
main branch of bzr-svn, build, and package it.
247
#. ``dput bzr-beta-ppa ../bzr-svn_0.4.15-1~bazaar1~hardy1_source.changes``
180
250
Monitoring the contents of PPAs
181
251
-------------------------------
added
removed
doc/developers/ppa.txt
