Bug#813096: ITP: logdata-anomaly-miner -- lightweight tool for log checking, log analysis
Hi
>I had already added it already to
>* control
>Depends: ${python:Depends}, python-tz, ${misc:Depends}
>which was mangled (with warning) to:
maybe you are installing the files in usr/lib/foo, instead of usr/lib/python*/
and then dh_python2 is not acting correctly?
I don't think installing python stuff outside that directory is a good idea...
>@@ -1,4 +1,4 @@
>-#!/usr/bin/python2 -BEsSt
>+#!/usr/bin/python2.7 -BEsSt
this should be also handled by dh_python2 AFAIK
>Everything seems to work without it also and the same package could have been
>used for python2.6 and python2.7 systems but lintian does not understand that.
well, installing into usr/lib/python* should fix that issue
I would prefer you to ask on debian-python about this issue, because I'm wondering
about something bad that is just hidden and will be spot when the package enters the
archive.
having an ack for a more python-savvy person would be great
(I could even sponsor the package as-is, but I'm not too confident with that)
>I hope this fixed all the review comments for regarding the packaging. I would
>like to keep the deeper restructuring of upstream code + Debian packaging
>scripts for upstream/Debian release V0.0.3. Is that OK from Debian side?
it is ok to have new uploads, don't worry about that, I just would like to have a feedback
from another DD before uploading/finish the review.
is it possible for you?
otherwise let me know and I'll finish the review and do the final checks+upload.
G.
Reply to: