LaunchpadPpa

Not logged in - Log In / Register

Revision 55 as of 2011-02-23 11:07:07

Clear message

This page is documentation for uploaders to the Launchpad PPA.

The Launchpad PPA (https://launchpad.net/~launchpad/+archive/ppa) contains dependencies for running Launchpad.

Packages

bzr-lpreview-body

This package contains the lpreview_body plugin for Bazaar. The packaging can be found in lp:~launchpad/lpreview-body/packaging.

bzr-pqm

bzr-pqm contains various plugins like lp-land. It needs to be maintained for all distroseries that we support development on.

This package is maintained through a recipe. See: https://code.launchpad.net/~launchpad-committers/+recipe/bzr-pqm-launchpad-ppa

bzr-tarmacland

XXX: Explain maintenance process.

geoip-data-city-lite

This package is a single data file, which upstream publishes updates to monthly. Why haven't we updated it since 2008?

launchpad-dependencies

The launchpad-dependencies source is managed in Bazaar branches at https://code.launchpad.net/meta-lp-deps.

Policy/procedure for updates:

  1. You will need bzr-builddeb and debhelper packages installed.
  2. Edit debian/control to add or change the dependencies.
  3. Set the DEBEMAIL and DEBFULLNAME environment variables. Your name and email address must match an identity in your GPG key exactly. You may want to put this in your shell rc file so you don't have to set it manually every time.
  4. Run 'debchange -i' in the root to increment the version number and add a changelog entry in the correct format. Remember that launchpad-dependencies should not have an ubuntu1 suffix on its version number, so if debchange -i adds that for you, take it out again and increment the unsuffixed version number instead.
  5. debcommit or bzr commit
  6. Exercise personal judgment on whether your change merits a merge proposal, or is sufficiently trivial to just be committed directly.
  7. If preparing a merge proposal, please ensure your branch for review contains a complete debian/changelog entry ready for release.
  8. Go to the trunk (or older distro) branch and merge / commit or pull changes ready to build.
  9. Test-build your package:

    bzr builddeb
  10. Actually build your source upload:

    bzr builddeb -S
  11. Tag it, push it, upload it:

    bzr mark-uploaded
    bzr push lp:meta-lp-deps
    debsign -S
    debrelease --dput -S ppa:launchpad/ppa
  12. After it has built, go to the PPA's +copy-packages page. Copy the package to all the other distroseries that the trunk branch is currently serving. Use the copy existing binaries option when copying.

After you've done this, you may need to update EC2Test/Image

pocket-lint

XXX: Explain maintenance process.

pocket-lint is in the Ubuntu primary archive for natty, so it is only required in the PPA for lucid and maverick.

slony1 (lucid only)

stub requested an update to slony1 1.2.21 for lucid. https://code.launchpad.net/~launchpad-committers/ubuntu/lucid/slony1/ppa-8.4

spidermonkey

Our jslint process requires a Javascript interpreter, ideally Spidermonkey, because Rhino is too slow. The Ubuntu archive no longer contains spidermonkey. Therefore we have it built in the PPA, from packaging derived from the Debian iceweasel source package, sliced and diced to only build the spidermonkey packages.

https://code.launchpad.net/~launchpad-committers/ubuntu/lucid/spidermonkey/ppa

tarmac

XXX: Explain maintenance process. https://code.launchpad.net/~matsubara/+recipe/lp-tarmac

Distro series support

At any given time, we will be supporting multiple Ubuntu series in the PPA:

When the supported series change, remember to also update Getting and Running.


Obsolete packages

Some notes on past contents of the PPA.

Rebuilds to restore older Python support

Most of the PPA used to be rebuilds of python library packages to re-instate support for the old Python version Launchpad required, which was dropped as a supported version in Ubuntu.

In jaunty/karmic, the need was to re-add Python 2.4 support. Launchpad made it to Python 2.5 for Karmic... and then the need was to re-add Python 2.5 support in lucid packages. Now, Launchpad made it to 2.6, and the relevant Lucid packages have been moved to the "obsolete" PPA.

Towards the end, we had most of the rebuilds working via a no-source-change rebuild.

Other compatibility issues in Lucid

These also have gone to "obsolete" PPA.