Interestingly enough distutils doesn't keep executable bits on
libraries, and this causes lintian to complain:
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/dfa.py
N:
N: This file starts with the #! sequence that marks interpreted scripts,
N: but it is not executable.
N:
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/dot.py
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/lexer.py
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/nfa.py
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/pyggy.py
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/pylly.py
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/slrgram.py
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/srgram.py
W: python-pyggy: script-not-executable ./usr/lib/python2.3/site-packages/pyggy/util.py
How should this be resolved? Manually putting the executable bits on the
files before packing? Removing '#!.*' in the mentioned files?
Is there a policy for this?
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus@therning.org
http://magnus.therning.org/
Don't bother just to be better than your contemporaries or predecessors.
Try to be better than yourself.
-- William Faulkner
Attachment:
signature.asc
Description: Digital signature