(I don't intend to sponsor this package.)
* Daniel Pocock <dan...@pocock.com.au>, 2012-10-03, 12:23:
http://mentors.debian.net/debian/pool/main/p/python-eventlib/python-eventlib_0.1.0-1.dsc
lintian reports:
I: python-eventlib source: debian-watch-file-is-missing
P: python-eventlib: no-upstream-changelog
I: python-eventlib: description-synopsis-might-not-be-phrased-properly
Furthermore, lintian4python reports:
i: python-eventlib source: debian-pycompat-is-obsolete
e: python-eventlib: except-shadows-builtin
usr/share/pyshared/eventlib/db_pool.py:175: ValueError
e: python-eventlib: except-shadows-builtin
usr/share/pyshared/eventlib/httpd.py:497: ValueError
e: python-eventlib: string-exception
usr/share/pyshared/eventlib/saranwrap.py:654
(+ a bunch of pyflakes-* tags, most of which are likely either false
positives or not worth caring.)
The copyright file is not policy-compliant. Please see:
https://lists.debian.org/debian-devel-announce/2006/03/msg00023.html
Worse, it doesn't seem to be factually correct either. It says "LGPL-2",
whereas e.g. setup.py says "MIT License".
I'd use "debhelper (>= 8)" instead of "debhelper (>= 8.0.0)".
The versioned build-dependency on python-all is insufficent; as per
dh_python2 manpage it should be at least >= 2.6.6-3~.
Current standards version is 3.9.4.
What is the purpose of "Conflicts: python-eventlet"?
Out of curiosity, why do you remove dist and MANIFEST in the clean
target?
Upstream seems to provide a test suite. Please run it at build time.
Upstream provides some examples. It might be worth including the in the
binary package.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121003200634.ga3...@jwilk.net
