zynjacku

Felipe Sateler fsateler at gmail.com
Thu Oct 1 19:26:26 UTC 2009


On Thu, 2009-10-01 at 18:44 +0200, Jaromír Mikeš wrote:
> Hi,
> 
> just working on zynjacku package and have here a bunch of lintian warnings which I would like discus with list.
> --------
> W: zynjacku: binary-without-manpage usr/bin/lv2rack.py
> W: zynjacku: binary-without-manpage usr/bin/zynjacku.py
> W: zynjacku: binary-without-manpage usr/bin/zynspect
> W: zynjacku: binary-without-manpage usr/bin/zynspect.py
> 
> * I already have man pages for lv2rack and zynjacku I should also make them for zynspect.
> But what about lv2rack.py, zynjacku.py and zynspect.py?
> They should have man pages too?

See below.

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

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

> 
> X: zynjacku: shlib-calls-exit usr/lib/python2.5/site-packages/zynworld/zynjacku_ttl.so
> 
> *this probably can be ignored if I understand well ...
> http://lintian.debian.org/tags/shlib-calls-exit.html

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

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

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


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


-- 
Saludos,
Felipe Sateler

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20091001/fdacedbf/attachment.pgp>


More information about the pkg-multimedia-maintainers mailing list