Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: Re: Python Policy Date: Wed, 21 Oct 2015 02:20:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Oct 21 00:18:39 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.109 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, CAPINIT=0.5, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 32 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: jigong.madmonks.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney Cancel-Lock: sha1:Y5/gqWQipPQkhIfD+KlWXquhsLE= X-Mailing-List: archive/latest/13038 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/85y4exoz0u.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 21 Oct 2015 11:17:53 +1100 X-Original-Message-ID: <85y4exoz0u.fsf@benfinney.id.au> X-Original-References: <20151019133137.6174ef07@limelight.wooz.org> <20151019212639.GF3846@p1otr.com> <20151020165359.69f44eae@limelight.wooz.org> <5626AD5E.8000900@debian.org> X-Original-X-Complaints-To: usenet@ger.gmane.org Xref: csiph.com linux.debian.maint.python:7726 "IOhannes m zmölnig (Debian/GNU)" writes: > thanks a lot for preparing all this. > > On 10/20/2015 10:53 PM, Barry Warsaw wrote: > > +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. > > i find the justification a bit weird: "no releases can be made from > upstream git because some upstreams use tarballs"? Yes, that is weird, and it's not what you quoted. I don't know how you get that meaning from the text you quoted: This is because PyPI contains upstream tarballs, and tarballs are what we upload to the Debian archive. > in any case, i don't think that there is actually a need for the > policy to justify the decision to require tarballs (let's put that in > the wiki for those interested). On the contrary, I think the Policy document should document the rationale for contingent decisions like this. When it is inevitably discussed again in the future, it is always better to know the intent of the authors. -- \ “Our products just aren't engineered for security.” —Brian | `\ Valentine, senior vice-president of Microsoft Windows | _o__) development, 2002 | Ben Finney