At file:///home/pqm/archives/thelove/bzr/%2Btrunk/ ------------------------------------------------------------ revno: 5344 [merge] revision-id: [email protected] parent: [email protected] parent: [email protected] committer: Canonical.com Patch Queue Manager <[email protected]> branch nick: +trunk timestamp: Tue 2010-07-13 21:20:23 +0100 message: (mbp) more documentation about maintaing the ppa (Martin Pool) modified: doc/developers/ppa.txt ppa.txt-20080722055539-606u7t2z32t3ae4w-1 === modified file 'doc/developers/ppa.txt' --- a/doc/developers/ppa.txt 2010-06-30 04:11:36 +0000 +++ b/doc/developers/ppa.txt 2010-07-13 17:14:43 +0000 @@ -47,6 +47,10 @@ <lp:~bzr/bzr/packaging-hardy>. These branches are intended to be used with the ``bzr-builddeb`` plugin. +**You should almost always upload to the beta ppa first** and then either +upload again or copy the packages into the release ppa. That reduces the +risk of breaking the main archive from which people get bzr updates. + Preconditions ------------- @@ -55,26 +59,15 @@ * You must have a GPG key registered to your Launchpad account. -* Configure ``dput`` to upload to our PPA with this section in your - ``~/.dput.cf``:: - - [bzr-beta-ppa] - fqdn = ppa.launchpad.net - method = ftp - incoming = ~bzr-beta-ppa/ubuntu - login = anonymous - allow_unsigned_uploads = 0 - - [bzr-ppa] - fqdn = ppa.launchpad.net - method = ftp - incoming = ~bzr/ubuntu - login = anonymous - allow_unsigned_uploads = 0 - - You may also want to add these lines to prevent inadvertently attempting - to upload into Ubuntu or Debian, which will give a somewhat unclear - error:: +On reasonably recent versions of Ubuntu you no longer need special dput +configuration, because you can just say :: + + dput ppa:bzr/2.1-proposed <source.changes + + +However, you may still want to add these lines to ``~/.dput.cf`` prevent +inadvertently attempting to upload into Ubuntu or Debian, which will +give a somewhat unclear error:: [DEFAULT] default_host_main = notspecified @@ -103,6 +96,31 @@ Packaging Bazaar ---------------- +Overview of packaging with builddeb +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +* First update the oldest supported branch, using ``bzr merge-upstream``. + +* Run ``bzr builddeb -S -- -sa`` to build a source package, then put + that into the ppa. + + (``-S`` says to make a source-only upload, which is + required for Launchpad's builders. ``--sa`` says to include the + ``.orig.tgz`` even if this doesn't seem to be the first upload for an + upstream release: this is often needed when rebuilding something that's + previously been uploaded to Debian or Ubuntu or into a different PPA.) + +* Now merge across that change into each supported branch with a + simple ``bzr merge``. + +Locally testing builds +~~~~~~~~~~~~~~~~~~~~~~ + +It may be useful to locally test builds inside pbuilder. You may want to +use the script from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255165> +to wrap it. + + Short form ~~~~~~~~~~ @@ -285,6 +303,16 @@ summary of current package versions with:: apt-cache madison bzr + + + +Packaging dependencies +---------------------- + +Some of our updates to bzr in previous releases require backports of our +dependencies. Specific branches holding these backports: + + * ``lp:~bzr/ubuntu/dapper/configobj/dapper-backport`` ..
-- bazaar-commits mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/bazaar-commits
