Python Applications Packaging Team - Policy

Author: Piotr O┼╝arowski <> (based on PMPT's policy)
License:GNU GPL v2 or later

Python Applications Packaging Team is a sister of Python Modules Packaging Team. We are taking care of Python applications, i.e. programs written in Python that are not providing public modules.

PAPT or just python-apps is hosted at, the Debian GForge installation. We currently have a SVN_repository and a mailing_list whose email address can be used in the Maintainer field on co-maintained packages.

For more information send a message to:


Joining the team

The team is open to any python-related package maintainer. To be added to the team, please request to join on Alioth (you need to create alioth's account first if you don't have one yet). Please indicate why you want to join the team: maintain your current packages within the team, help maintain some specific packages, etc.

Any Python Modules Packaging Team member who wishes to integrate his packages in the team can do so without requesting access (as the repository is writable by all PMPT members and thus by all DD). If one wants to be more involved in the team, we still recommend requesting access so that he appears in the public member list displayed on Alioth's project page. Debian developers: please note if you're willing to act as a sponsor, you'll get a "sponsor" role on Alioth.

The team accepts all contributors and is not restricted to Debian developers. Several Debian developers of the team will gladly sponsor packages of non-DD who are part of the team. Sponsorship requests can be sent on the main discussion list or on #debian-python IRC channel (OFCT network).

All team members should of course follow the main discussion list: (DP_listinfo)


A package maintained within the team should have the name of the team either in the Maintainer field or in the Uploaders field.

Maintainer: Python Applications Packaging Team <>

This enables the team to have an overview of its packages on the DDPO_website.

Thus if you bring some packages into the team, you can keep your name in the Maintainer field. You will receive bug reports and handle your package as usual except that other team members may help from time to time and/or take over when you're too busy.

If you put the team in the Maintainer field, the package will be handled completely by the team and every member is invited to work on any outstanding issue.

Team members who have broad interest should subscribe to the mailing list whereas members who are only interested in some packages should use the Package Tracking System to follow the packages.

Subversion Procedures

We're using a Subversion repository to maintain all the packages, then if you're not already using it you will need to install svn-buildpackage.

The repository layout

Ignore this directory (reserved for future usage).

The source packages are here.

If you or someone wants to play with a package possible breaking the trunk, give it a name and do it here.
For each release, a tag. More information below.
That's where the main development happens, it should contain only the debian/ subdirectory part of a package.
Documents and stuff that will be or are being published online in our website.


  • To keep your package tree clean as pointed out above, always svn-inject your packages using -o argument.
  • If you svn-inject'ed a package without -o you should remove upstream sources and run svn propset mergeWithUpstream 1 debian/.
  • Since you are keeping only debian/ directory in the svn tree you need to put the 'package-foo'_'version'.orig.tar.gz in tarballs/ a directory above the package and svn-buildpackage will do the merge for you. More information about this in the svn-buildpackage howto at /usr/share/doc/svn-buildpackage/.
  • After upload, tag the latest revision running svn-buildpackage --svn-tag-only into 'package-foo' directory.
  • You can revert the changelog changes after tagging, running svn revert debian/changelog.
  • If you're a pbuilder user, you can invoke it using svn-buildpackage --svn-builder pdebuild <args>.
  • Do not forget to add Vcs-Svn and Scs-Browser to your debian/control file

Example inject command

svn-inject -o pypar2_1.4-1.dsc svn+ssh://

Quality Assurance

The goal of the team is to maintain all packages as best as possible. Thus every member is encouraged to do general QA work on all the packages: fix bugs, test packages, improve them to use the latest Python packaging tools, etc.


Copyright (c) 2007 Python Applications Packaging Team. All rights reserved. This document is free software; you may redistribute it and/or modify it under the same terms as GNU GPL v2 or later.