6711
Comment: Fix instruction for setting user identity
|
6615
Update series.
|
Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
= Packages = | = Packages, All distroseries = |
Line 30: | Line 30: |
1. Set the DEBEMAIL and DEBFULLNAME environment variables. Your name and email address must match an identity in your GPG key exactly. | 1. 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. |
Line 39: | Line 39: |
1. Actually build your source upload: {{{ bzr builddeb -S |
1. Since the package has a Launchpad build recipe, you only need to push the branch to Launchpad:{{{ bzr push lp:meta-lp-deps |
Line 42: | Line 42: |
1. Tag it, push it, upload it: {{{ bzr mark-uploaded bzr push lp:meta-lp-deps debsign -S debrelease --dput -S ppa:launchpad/ppa }}} 1. '''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.''' |
1. '''After it has built, go to the PPA's [[https://launchpad.net/~launchpad/+archive/ppa/+copy-packages|+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.''' |
Line 53: | Line 47: |
XXX: Explain maintenance process. | |
Line 55: | Line 48: |
pocket-lint is in the Ubuntu primary archive for natty, so it is only required in the PPA for lucid and maverick. | pocket-lint is in the Ubuntu primary archive for natty, so it is only required in the PPA for lucid. |
Line 57: | Line 50: |
== 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 |
You can build trunk on demand using a recipe https://code.launchpad.net/~sinzui/+recipe/pocket-lint-daily |
Line 60: | Line 53: |
== 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 |
|
Line 69: | Line 58: |
== testrepository == ? = Packages, Lucid only = == apt == ? == dpkg == ? == pycassa == for cassandra == slony1 == stub requested an update to slony1 1.2.21 for lucid. https://code.launchpad.net/~launchpad-committers/ubuntu/lucid/slony1/ppa-8.4 == thrift == for cassandra |
|
Line 71: | Line 80: |
* The current development series - to permit Ubuntu developers on the bleeding edge to develop Launchpad (currently: natty). | * The current development series - to permit Ubuntu developers on the bleeding edge to develop Launchpad (currently: oneiric). |
Line 73: | Line 82: |
* The current release - most developers run it (currently: maverick). | * The current release - most developers run it (currently: natty). |
Line 76: | Line 85: |
* As many other older releases as it is reasonably practicable to do so, to accomodate developers on older releases (currently: none), | * As many other older releases as it is reasonably practicable to do so, to accommodate developers on older releases (currently: maverick), |
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
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?
- 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)
launchpad-dependencies
The launchpad-dependencies source is managed in Bazaar branches at https://code.launchpad.net/meta-lp-deps.
Policy/procedure for updates:
- You will need bzr-builddeb and debhelper packages installed.
- Edit debian/control to add or change the dependencies.
- 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.
- 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.
- debcommit or bzr commit
- 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
Since the package has a Launchpad build recipe, you only need to push the branch to Launchpad:
bzr push lp:meta-lp-deps
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
tarmac
XXX: Explain maintenance process. https://code.launchpad.net/~matsubara/+recipe/lp-tarmac
testrepository
?
Packages, Lucid only
apt
?
dpkg
?
pycassa
for cassandra
slony1
stub requested an update to slony1 1.2.21 for lucid. https://code.launchpad.net/~launchpad-committers/ubuntu/lucid/slony1/ppa-8.4
thrift
for cassandra
Distro series support
At any given time, we will be supporting multiple Ubuntu series in the PPA:
- The current development series - to permit Ubuntu developers on the bleeding edge to develop Launchpad (currently: oneiric).
- Use pragmatism in deciding when to start supporting a new development series - almost certainly not until alpha 1, at least.
- The current release - most developers run it (currently: natty).
- The current LTS - the datacentre either runs it, or is going to be running it shortly (currently: lucid).
- The next older LTS, if it's still in use on production datacentre machines (currently: none).
- As many other older releases as it is reasonably practicable to do so, to accommodate developers on older releases (currently: maverick),
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.
- Sourceful changes - in bzr branches
- No-source-change rebuilds
- distribute (didn't actually work, was just to facilitate building 2.5 eggs, for which the immediate need passed, so hasn't been fixed.)
- egenix-mx-base
- psycopg2
- pycxx
- pysvn (no-source-change since lucid; earlier patching in branches)
- python-apt
- python-crypto
- python-geoip
- python-imaging
- python-pysqlite2
- subversion (no-source-change since lucid)
- tickcount
- In PPA for karmic but not for lucid:
- python-sqlite: lucid version is still Python 2.5 compatible
Other compatibility issues in Lucid
These also have gone to "obsolete" PPA.
- postgresql-8.3: was dropped, we needed it still, and it needed a no-change rebuild to pick up a ${shlibs:Depends} change.
- python2.5: was dropped, binary-copied last version from the primary archive.
slony1pg83: built against postgresql 8.3 instead of 8.4. (https://code.edge.launchpad.net/~launchpad-committers/ubuntu/lucid/slony1/ppa-8.3)