On 2014-01-25 07:39:30, Thomas Goirand wrote: > On 01/24/2014 11:13 PM, Sebastian Ramacher wrote: > > On 2014-01-24 23:05:57, Thomas Goirand wrote: > >> Package: wnpp > >> Severity: wishlist > >> Owner: Thomas Goirand <zigo@debian.org> > >> > >> * Package name : python-future > >> Version : 2.1.6 > >> Upstream Author : Alex Gronholm <alex.gronholm+pypi@nextday.fi> > >> * URL : https://pypi.python.org/pypi/futures > >> * License : BSD-2-clause > >> Programming Lang: Python > >> Description : backport of the concurrent.futures package > >> > >> This package is a backport of concurrent.futures from Python 3.2 to Python > >> 2.6, 2.7 and 3.1. In Debian, there is no use of Python 3.1 support anymore, > >> and only 2.7, and to some extend 2.6 (for backports), is useful. > > > > It's already packages python-concurrent.futures: > > http://packages.qa.debian.org/p/python-concurrent.futures.html > > > > Regards > > I know, but that's not the same package. python-taskflow, which I'm > packaging, only works with python-futures, and not with > concurrent.futures for example. Ähm, what? Both python-concurrent.futures and the proposed python-future point to the same upstream. The sha1sum of the tarball found at the URL you have given and the sha1sum of the the orig tarball of python-concurrent.futures in the archive are the same [1]. If there is a problem with the package in the archive, please report it. There is no need to package the same package twice with a different name. Regards [1] futures-2.1.6.tar.gz [2] and python-concurrent.features_2.1.6.orig.tar.gz [3] have both 5247ac8fa0eaf54051aa51e736ffc7b4d450a3d0 as sha1sum. [2] https://pypi.python.org/packages/source/f/futures/futures-2.1.6.tar.gz [3] http://http.debian.net/debian/pool/main/p/python-concurrent.futures/python-concurrent.futures_2.1.6.orig.tar.gz -- Sebastian Ramacher
Attachment:
signature.asc
Description: Digital signature