On 25 February 2015 at 10:14, Piotr Ożarowski <pi...@debian.org> wrote:

> PyPI link you mentioned points to these:
>
>
> https://pypi.python.org/packages/source/d/devpi-server/devpi-server-2.1.4.tar.gz#md5=c92749708b957922f30bc7af0fb8a7b0
>
> https://pypi.python.org/packages/source/d/devpi-web/devpi-web-2.2.3.tar.gz#md5=323fed68d7d1cef1f78c774d1d59e45f
>
> https://pypi.python.org/packages/source/d/devpi-client/devpi-client-2.0.5.tar.gz#md5=7075078c7b23f343adecd70e93885118
>
>
I just noticed https://pypi.python.org/pypi/devpi/ is just an empty shell
and useless by itself.

drwxrwxr-x hpk/hpk           0 2014-09-22 20:46 devpi-2.1.0/
drwxrwxr-x hpk/hpk           0 2014-09-22 20:46 devpi-2.1.0/devpi.egg-info/
-rw-rw-r-- hpk/hpk           1 2014-09-22 20:46
devpi-2.1.0/devpi.egg-info/not-zip-safe
-rw-rw-r-- hpk/hpk           1 2014-09-22 20:46
devpi-2.1.0/devpi.egg-info/top_level.txt
-rw-rw-r-- hpk/hpk          81 2014-09-22 20:46
devpi-2.1.0/devpi.egg-info/requires.txt
-rw-rw-r-- hpk/hpk        1635 2014-09-22 20:46
devpi-2.1.0/devpi.egg-info/PKG-INFO
-rw-rw-r-- hpk/hpk         221 2014-09-22 20:46
devpi-2.1.0/devpi.egg-info/SOURCES.txt
-rw-rw-r-- hpk/hpk           1 2014-09-22 20:46
devpi-2.1.0/devpi.egg-info/dependency_links.txt
-rw-rw-r-- hpk/hpk          59 2014-09-22 20:46 devpi-2.1.0/setup.cfg
-rw-rw-r-- hpk/hpk          46 2014-09-22 20:46 devpi-2.1.0/MANIFEST.in
-rw-rw-r-- hpk/hpk        1635 2014-09-22 20:46 devpi-2.1.0/PKG-INFO
-rw-rw-r-- hpk/hpk         174 2014-09-22 20:46 devpi-2.1.0/tox.ini
-rw-rw-r-- hpk/hpk         785 2014-09-22 20:46 devpi-2.1.0/README.rst
-rw-rw-r-- hpk/hpk       28599 2014-09-22 20:46 devpi-2.1.0/CHANGELOG
-rw-rw-r-- hpk/hpk        1153 2014-09-22 20:46 devpi-2.1.0/setup.py

I suspect you need these instead.

http://pypi.python.org/pypi/devpi-server
http://pypi.python.org/pypi/devpi-web
http://pypi.python.org/pypi/devpi-client

As each one has its own version number, and presumably its own release
cycle, presumably you should be packaging them as separate Debian source
packages.
-- 
Brian May <br...@microcomaustralia.com.au>

Reply via email to