LaunchpadPpa

Not logged in - Log In / Register

Revision 67 as of 2016-11-14 04:50:03

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, All distroseries

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

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. Since the package has a Launchpad build recipe, you only need to push the branch to Launchpad:

    bzr push lp:meta-lp-deps
  11. 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

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

You can build trunk on demand using a recipe https://code.launchpad.net/~sinzui/+recipe/pocket-lint-daily

python-lpbuildd and launchpad-buildd

These are also from https://launchpad.net/launchpad-buildd and they actually run a buildd.

The Python modules are needed to run Launchpad integration tests and are part of launchpad-developer-dependencies. The actual launchpad-buildd package is only needed to run the slaves.

They are built daily or on request by a recipe

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.