Re: zynjacku

[Jaromír Mikeš]

Hi,

JM> just working on zynjacku package and have here a bunch of lintian warnings which I would like discus with list.
JM> --------
JM> W: zynjacku: binary-without-manpage usr/bin/lv2rack.py
JM> W: zynjacku: binary-without-manpage usr/bin/zynjacku.py
JM> W: zynjacku: binary-without-manpage usr/bin/zynspect
JM> W: zynjacku: binary-without-manpage usr/bin/zynspect.py
JM> 
JM> * I already have man pages for lv2rack and zynjacku I should also make them for zynspect.
JM> But what about lv2rack.py, zynjacku.py and zynspect.py?
JM> They should have man pages too?

FS>See below.

 
JM> W: zynjacku: script-with-language-extension usr/bin/lv2rack.py
JM> W: zynjacku: script-with-language-extension usr/bin/zynjacku.py
JM> W: zynjacku: script-with-language-extension usr/bin/zynspect.py
 
JM> *I don't understand what should I do with these.. any advice appreciated.
JM> http://lintian.debian.org/tags/script-with-language-extension.html

FS>Zynjacku is installing the scripts with .py extension plus a symlink
FS>without it. The package should only install the script without the
FS>extension (eg, lv2rack.py should be named lvrack). I've just commited a
FS>fix for that.

Many thanks for that :) you save me hours.

JM> X: zynjacku: shlib-calls-exit usr/lib/python2.5/site-packages/zynworld/zynjacku_ttl.so

JM> *this probably can be ignored if I understand well ...
JM> http://lintian.debian.org/tags/shlib-calls-exit.html

FS>I'm not sure what can be done for this. Flex is generating those exit
FS>calls. You may want to talk to upstream about this.

I will contact him. 
 
JM> W: zynjacku: executable-not-elf-or-script ./usr/lib/python2.5/site-packages/zynworld/__init__.py
JM> W: zynjacku: executable-not-elf-or-script ./usr/lib/python2.5/site-packages/zynworld/lv2.py
 
JM> * Also here I am not sure what to do.

FS> The lintian warning here is because those python files are executable
FS> but do not start with a shebang line. However, this indicates another
FS> problem, this package ships a python module but it is not compatible
FS> with the python policy. You need to use python-central or
FS> python-support. Moreover, you are shipping .la files in the python dir,
FS> which is not necessary either. You have to use python-support or
FS> python-central (apparently python-support is better). I'm no python
FS> expert, however.

I know nothing about python, but anyway I will try investigate and solve this. 

FS> BTW, the git repository is broken. The upstream/5 tag does not point to
FS> the latest upstream version, but to the merge of it with the master
FS> branch! I think it should be retagged. Did you use git-import-orig to
FS> import the source?

Actually I am not sure if I used  git-import-orig ... it was probably one of first git operation so I wouldn't  be surprise by some troubles.
Anyway I think I used git-import-orig.  Any suggestion how to fix it?

best regards

mira