[Python-modules-commits] [python-modules] 01/01: Rephrase the pristine-tar/tarball requirement. Avoid mention of gbp buildpackage.

[Barry Warsaw]

This is an automated email from the git hooks/post-receive script.

barry pushed a commit to branch git-policy
in repository python-modules.

commit 1dc3bc3f735eb3ee50f831ee83c8892ed3904215
Author: Barry Warsaw <barry at python.org>
Date:   Wed Oct 21 09:48:02 2015 -0400

    Rephrase the pristine-tar/tarball requirement.
    Avoid mention of gbp buildpackage.
---
 policy.rst | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/policy.rst b/policy.rst
index f510beb..bdb5d45 100644
--- a/policy.rst
+++ b/policy.rst
@@ -89,9 +89,9 @@ question.
 DPMT git repos are **source-full**, meaning they contain both the upstream
 source and the ``debian/`` directory.
 
-DPMT requires upstream tarballs; releases cannot be made from upstream git
-repositories directly.  This is because PyPI contains upstream tarballs, and
-tarballs are what we upload to the Debian archive.
+DPMT requires a pristine-tar branch, and only upstream tarballs can be used to
+advance the upstream branch.  Complete upstream git history should be avoided
+in the upstream branch.
 
 Deviations from this policy are strongly discouraged.  When you must (not want
 to) deviate, you MUST include a ``debian/README.source`` file explaining the
@@ -102,8 +102,6 @@ repo.
 Tools
 -----
 
-``gbp buildpackage`` is used to build the package, either as a source package
-for use with ``pbuilder``, ``sbuild``, etc. or as a binary package directory.
 Do *not* create ``quilt`` patches directly.  Instead, use ``git-dpm
 checkout-patched`` to enter a patch branch, edit the files, commit them, and
 then use ``git-dpm update-patches`` to switch back to the master branch, with

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/python-modules/tools/python-modules.git