14
14
__ https://help.launchpad.net/PPAQuickStart
16
As of September 2010, there are four PPAs:
16
As of January 2011, there are the following PPAs:
18
18
<https://launchpad.net/~bzr/+archive/ppa>
19
19
Final released versions and updates.
20
20
Most users who want updates to bzr should add this.
22
22
<https://launchpad.net/~bzr/+archive/proposed>
23
Proposed uploads to move into ~bzr, awaiting testing.
25
<https://launchpad.net/~bzr-beta-ppa/+archive>
23
Proposed uploads to move into ~bzr/ppa, awaiting testing.
25
<https://launchpad.net/~bzr/+archive/obsolete>
26
A preserved copy of the final version of packages from ~bzr/ppa for
27
obsolete Ubuntu series.
29
<https://launchpad.net/~bzr/+archive/beta>
28
<https://launchpad.net/~bzr-nightly-ppa/+archive>
32
<https://launchpad.net/~bzr/+archive/beta-obsolete>
33
A preserved copy of the final version of packages from
34
~bzr/beta for obsolete Ubuntu series.
36
<https://launchpad.net/~bzr/+archive/daily>
29
37
Automatic nightly builds from trunk.
31
We build a distinct package for each distrorelease.
39
We build a distinct package for each distrorelease.
32
40
If you upload a release-specific version, you should add a suffix to the
33
package version, e.g. ``bzr.1.3-1~bazaar1~dapper1``.
41
package version, e.g. ``1.3-1~bazaar1~dapper1``.
35
43
Dapper uses the ``python-support`` framework and later distributions use
36
44
``python-central``. This has little effect on everyday packaging but does
37
45
mean that some of the control files are quite different.
39
Every package is first uploaded into the beta ppa. For final release
40
versions it is also copied to the main PPA.
47
Beta releases of bzr and plugins are uploaded into the beta PPA.
49
Final release versions are first uploaded into the proposed PPA, which
50
serves as a staging area to allow for new packages to be tested, and also
51
so that a complete set of Bazaar core and plugin updated versions can be
52
prepared together, when negotiating an API version transition.
54
Once ready, packages can be copied from the proposed PPA to the main PPA
55
using the lp-promote-ppa script found within the hydrazine project. This
56
procedure reduces the risk of broken packages or dependencies between
57
packages in the main PPA from which many people get bzr updates.
42
59
The packaging information is kept in branches of bzr on Launchpad, named
46
63
<lp:~bzr/ubuntu/hardy/bzr/bzr-ppa>. These branches are intended to be used
47
64
with the ``bzr-builddeb`` plugin.
49
**You should almost always upload to the beta ppa first** and then either
50
upload again or copy the packages into the release ppa. That reduces the
51
risk of breaking the main archive from which people get bzr updates.
66
The page <http://wiki.bazaar.canonical.com/PpaPackagingBranches> is a
67
reference to where the PPA packaging branches for each of the source
68
packages in the ``~bzr`` PPAs may be found.
77
* You must have a Launchpad account and be a member of the teams
78
that own these PPAs (``~bzr``, ``~bzr-beta-ppa``).
94
* You must have a Launchpad account and be a member of the team
95
that owns these PPAs (``~bzr``).
80
97
* You must have a GPG key registered to your Launchpad account.
82
99
On reasonably recent versions of Ubuntu you no longer need special dput
83
100
configuration, because you can just say ::
85
dput ppa:bzr/proposed <source.changes
102
dput ppa:bzr/proposed source.changes
88
105
However, you may still want to add these lines to ``~/.dput.cf`` prevent
93
110
default_host_main = notspecified
95
* Configure ``bzr-builddeb`` to sign the package, which is required for
96
Launchpad to build it. Put this in ``~/.bazaar/builddeb.conf`` ::
99
builder = dpkg-buildpackage -rfakeroot
100
source-builder= dpkg-buildpackage -rfakeroot -S -sa
102
112
* You need a Ubuntu (or probably Debian) machine, and ::
104
114
sudo apt-get install build-essential devscripts dput quilt patch libcrypt-ssleay-perl debhelper cdbs python-docutils
106
116
Please update this document if you encounter unmet dependencies or find a
107
117
shorter way to express them.
109
* You will also want to have the `bzr-builddeb`_ plugin installed, which
110
depends on `bzrtools`_.
119
* You will also want to have the `bzr-builddeb`_ plugin installed.
112
121
.. _`bzr-builddeb`: http://launchpad.net/bzr-builddeb
113
.. _`bzrtools`: http://launchpad.net/bzrtools
125
133
that into the ppa.
127
135
(``-S`` says to make a source-only upload, which is
128
required for Launchpad's builders. ``--sa`` says to include the
136
required for Launchpad's builders. ``-sa`` says to include the
129
137
``.orig.tgz`` even if this doesn't seem to be the first upload for an
130
138
upstream release: this is often needed when rebuilding something that's
131
139
previously been uploaded to Debian or Ubuntu or into a different PPA.)
140
148
use the script from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255165>
141
149
to wrap it, and to give it sensible defaults for your local machine.
143
Update all packages in proposed before copping the main ppa
144
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
151
Update all packages in proposed before copying to the main ppa
152
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
146
154
If one updates bzr, and there are plugins that are not compatible with the
147
155
new version of bzr, this can cause pain for users using the ppa. In order to
292
300
#. You should soon get an "upload accepted" mail from Launchpad, which
293
301
means that your package is waiting to be built. You can then track its
294
progress in <https://launchpad.net/~bzr-beta-ppa/+archive> and
295
<https://launchpad.net/~bzr-beta-ppa/+archive/+builds>.
302
progress in <https://launchpad.net/~bzr/+archive/proposed> and
303
<https://launchpad.net/~bzr/+archive/proposed/+builds>.
298
306
Packaging bzr-svn
319
327
bzr-builddeb will automatically check out the appropriate tag from the
320
328
main branch of bzr-svn, build, and package it.
322
#. ``dput bzr-beta-ppa ../bzr-svn_0.4.15-1~bazaar1~hardy1_source.changes``
330
#. ``dput ppa:bzr/proposed ../bzr-svn_0.4.15-1~bazaar1~hardy1_source.changes``
325
333
Monitoring the contents of PPAs
added
removed
doc/developers/ppa.txt
