launchpad development|
Size: 6611
Comment:
|
← Revision 77 as of 2021-08-24 10:48:34 ⇥
Size: 4691
Comment: various package-specific series updates and similar
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| = Packages, All distroseries = | = Launchpad-specific packages = |
| Line 11: | Line 11: |
== 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 [[https://help.launchpad.net/Packaging/SourceBuilds/Recipes|recipe]]. See: https://code.launchpad.net/~launchpad-committers/+recipe/bzr-pqm-launchpad-ppa == bzr-tarmacland == XXX: Explain maintenance process. |
|
| Line 39: | Line 31: |
| 1. Since the package has a Launchpad build recipe, you only need to push the branch to Launchpad:{{{ | 1. Since the package has a [[https://code.launchpad.net/~launchpad/+recipe/meta-lp-deps-on-demand|Launchpad build recipe]], you only need to push the branch to Launchpad:{{{ |
| Line 42: | Line 34: |
| 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.''' 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 |
|
| Line 54: | Line 36: |
| == tarmac == XXX: Explain maintenance process. https://code.launchpad.net/~matsubara/+recipe/lp-tarmac |
== launchpad-buildd == |
| Line 58: | Line 38: |
| == testrepository == ? |
This is from https://launchpad.net/launchpad-buildd. |
| Line 61: | Line 40: |
| = Packages, Lucid only = | python-lpbuildd is used by the test suite, so is part of launchpad-developer-dependencies. launchpad-buildd itself runs an actual buildd and is only needed on slaves. |
| Line 63: | Line 42: |
| == apt == ? |
[[https://code.launchpad.net/~launchpad/+recipe/launchpad-buildd-daily|The package is built daily or on request by a recipe]] |
| Line 66: | Line 44: |
| == dpkg == ? |
|
| Line 69: | Line 45: |
| == pycassa == for cassandra |
== lpsetup == |
| Line 72: | Line 47: |
| == slony1 == stub requested an update to slony1 1.2.21 for lucid. https://code.launchpad.net/~launchpad-committers/ubuntu/lucid/slony1/ppa-8.4 |
?? (probably only used by parallel buildbot slaves, which are probably using the puppet fork anyway) |
| Line 75: | Line 49: |
| == thrift == for cassandra |
== mmm-archive-manager == ?? = Backported or patched Ubuntu packages = == postgresql-10, postgresql-common, postgresql-debversion, slony1-2 (trusty, xenial) == Straight backports of PostgreSQL 10 and paraphernalia from bionic to trusty. bionic's version is fine. == pgbouncer (trusty) == Trusty's pgbouncer with wgrant's ENABLE/DISABLE patch as required by full-update.py. For the benefit of launchpad-dependencies, the patched package additionally Provides pgbouncer-with-disconnect. The ENABLE/DISABLE patch is included upstream in pgbouncer 1.6, so xenial's version is fine. == libgit2, git (bionic) == Various updates backported from focal for use on git.launchpad.net. == convoy == [[https://code.launchpad.net/~launchpad/+recipe/launchpad-convoy|Daily builds of lp:convoy with custom packaging]]. The packaging is based on [[https://code.launchpad.net/~landscape/+recipe/convoy-daily-trunk-lds|Landscape's]], but modified to install Launchpad's convoy.wsgi. Ubuntu's modern packaging uses dh-python and supports Python 3. == debian-archive-keyring (xenial, bionic, focal) == Straight backport for new Debian archive keys for gina's mirror. hirsute's version is fine. == git-build-recipe == [[https://code.launchpad.net/~launchpad/+recipe/git-build-recipe-daily|Daily builds of lp:git-build-recipe]] for buildds. |
| Line 79: | Line 90: |
| 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: natty). * 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: maverick). * 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 accomodate developers on older releases (currently: none), |
== Stable == * trusty (obsolete production LTS, still used by databases) * xenial (current production LTS) * bionic (next production LTS) == In progress == * focal (next, next production LTS?) |
| Line 88: | Line 103: |
---------- = 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 * python-defaults (https://code.launchpad.net/~launchpad-committers/ubuntu/lucid/python-defaults/launchpad-ppa) * python-support (https://code.launchpad.net/~launchpad-committers/ubuntu/lucid/python-support/launchpad-ppa) * 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) |
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-specific packages
bzr-lpreview-body
This package contains the lpreview_body plugin for Bazaar. The packaging can be found in lp:~launchpad/lpreview-body/packaging.
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
launchpad-buildd
This is from https://launchpad.net/launchpad-buildd.
python-lpbuildd is used by the test suite, so is part of launchpad-developer-dependencies. launchpad-buildd itself runs an actual buildd and is only needed on slaves.
The package is built daily or on request by a recipe
lpsetup
?? (probably only used by parallel buildbot slaves, which are probably using the puppet fork anyway)
mmm-archive-manager
??
Backported or patched Ubuntu packages
postgresql-10, postgresql-common, postgresql-debversion, slony1-2 (trusty, xenial)
Straight backports of PostgreSQL 10 and paraphernalia from bionic to trusty. bionic's version is fine.
pgbouncer (trusty)
Trusty's pgbouncer with wgrant's ENABLE/DISABLE patch as required by full-update.py. For the benefit of launchpad-dependencies, the patched package additionally Provides pgbouncer-with-disconnect.
The ENABLE/DISABLE patch is included upstream in pgbouncer 1.6, so xenial's version is fine.
libgit2, git (bionic)
Various updates backported from focal for use on git.launchpad.net.
convoy
Daily builds of lp:convoy with custom packaging. The packaging is based on Landscape's, but modified to install Launchpad's convoy.wsgi. Ubuntu's modern packaging uses dh-python and supports Python 3.
debian-archive-keyring (xenial, bionic, focal)
Straight backport for new Debian archive keys for gina's mirror. hirsute's version is fine.
git-build-recipe
Daily builds of lp:git-build-recipe for buildds.
Distro series support
Stable
- trusty (obsolete production LTS, still used by databases)
- xenial (current production LTS)
- bionic (next production LTS)
In progress
- focal (next, next production LTS?)
When the supported series change, remember to also update Getting and Running.
