LaunchpadPpa

Not logged in - Log In / Register

Revision 27 as of 2010-05-06 01:10:12

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.

launchpad-dependencies

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

Policy/procedure for updates:

  1. Remember that launchpad-dependencies should not have an ubuntu1 suffix on its version number, so if dch -i adds that for you, take it out again and increment the unsuffixed version number instead.
  2. Exercise personal judgment on whether your change merits a merge proposal, or is sufficiently trivial to just be committed directly.
  3. If preparing a merge proposal, please ensure your branch for review contains a complete debian/changelog entry ready for release.
  4. Go to the trunk (or older distro) branch and merge / commit or pull changes ready to build.
  5. Test-build your package:

    bzr builddeb
  6. Actually build your source upload:

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

    bzr mark-uploaded
    bzr push
    debsign -S
    debrelease --dput -S ppa:launchpad/ppa
  8. If uploading a version from the trunk branch, after it has built, go to the PPA +copy-packages page copy it 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

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?

Rebuilds to restore older Python support

Most of the PPA is rebuilds of python library packages to re-instate support for the old Python version Launchpad requires, which has since been 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 now the need is to re-add Python 2.5 support in lucid packages.

This should generally be done with a no-source-change rebuild where possible.

Other compatibility issues (Lucid)