launchpad development|
Size: 2554
Comment:
|
Size: 2885
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| = launchpad-dependencies = | = launchpad-dependencies = |
| Line 13: | Line 13: |
| bzr builddeb --native -- --no-lintian | bzr builddeb |
| Line 16: | Line 16: |
| bzr builddeb -S --native -- --no-lintian | bzr builddeb -S |
| Line 21: | Line 21: |
| dput ppa:launchpad/ppa ../launchpad-dependencies_<whatever>_source.changes | debsign -S debrelease --dput -S ppa:launchpad/ppa |
| Line 23: | Line 24: |
| 1. 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. |
|
| Line 27: | Line 30: |
| * Because we are using it only for tests and updating too frequently may actually break some tests (we've seen it happen). It's no big deal if developers don't get the fully up-to-date geoIP DB. Production uses the proprietary geoIP DB instead. — Danilo (2010-01-21) | |
| Line 28: | Line 32: |
| = Rebuilds to restore Python 2.4 support = | = Rebuilds to restore older Python support = |
| Line 31: | Line 35: |
| maxb is leading a migration towards using no-source-change rebuilds for this where possible. | 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. |
| Line 34: | Line 40: |
| * python-defaults - https://code.edge.launchpad.net/~maxb/ubuntu/karmic/python-defaults/launchpad-ppa * Sourceful changes - not in bzr branches * pysvn - debian/rules required rework to deal with changed Python versions. Should go to branch and should be pushed upstream. * python-support: * Embedded list of supported python versions is changed. * Python version-specific Provides added, so that launchpad-dependencies can enforce a launchpad-modified version. * subversion - requires XS-Python-Version amendment. Change to trivial to be worth maintaining in a bzr branch. |
* python-defaults (https://code.edge.launchpad.net/~launchpad-committers/ubuntu/lucid/python-defaults/launchpad-ppa) * python-support (https://code.edge.launchpad.net/~launchpad-committers/ubuntu/lucid/python-support/launchpad-ppa) |
| Line 44: | Line 44: |
| * python-sqlite * No-source-change rebuilds |
|
| Line 46: | Line 49: |
| * python-imaging * python-sqlite * tickcount * No-source-change rebuilds |
* pysvn (since lucid; earlier patching in branches) |
| Line 54: | Line 53: |
| * python-imaging | |
| Line 55: | Line 55: |
| * subversion (since lucid) * tickcount |
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:
- Exercise personal judgment on whether your change merits a merge proposal, or is sufficiently trivial to just be committed directly.
- If preparing a merge proposal, please ensure your branch for review contains a complete debian/changelog entry ready for release.
- Go to the trunk (or older distro) branch and merge / commit or pull changes ready to build.
Test-build your package:
bzr builddeb
Actually build your source upload:
bzr builddeb -S
Tag it, push it, upload it:
bzr mark-uploaded bzr push debsign -S debrelease --dput -S ppa:launchpad/ppa
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.
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?
- Because we are using it only for tests and updating too frequently may actually break some tests (we've seen it happen). It's no big deal if developers don't get the fully up-to-date geoIP DB. Production uses the proprietary geoIP DB instead. — Danilo (2010-01-21)
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.
- Sourceful changes - in bzr branches
- Sourceful changes - not rebuilt since jaunty, might be able to be no-source-change on next upload
- python-sqlite
- No-source-change rebuilds
- psycopg2
- pycxx
- pysvn (since lucid; earlier patching in branches)
- python-apt
- python-crypto
- python-geoip
- python-imaging
- python-pysqlite2
- subversion (since lucid)
- tickcount
