On Sat, Sep 27, 2003 at 03:27:53PM -0400, Marco Paganini wrote: > > > I did and it just says: > > > > > > W: ask: prerm-does-not-remove-usr-doc-link > > > W: ask: postinst-does-not-set-usr-doc-link
I forgot to say you should pass "-i" to lintian, so that it outputs the full warning/error message once for each warning/error type. > > Not really important. > > Is there a way to "remove" these, just like in lint? Something inside > the package itself that tells lintian to ignore those? I'm not sure if you should remove them. Please paste the full lintian warning. > > > W: ask: unusual-interpreter ./usr/bin/ask.py #!python2.2 > > > > That should be "#!/usr/bin/python2.2" (or better, 2.3). > > That's the thing: Python's documentation suggests the use of "env", to > make the physical location of python irrelevant. But the question is: > How do I tell lintian that "env" is OK? Sometimes Debian's policy disagrees with upstream's (in this case Python's upstream). In these cases your package should always follow Debian's policy rather than upstream's. On this situation, Debian policy follows the FHS standard (you should read that too, btw), which mandates the physical location of python should be "/usr/bin/". Since the location of phyton is standarised in Debian, the use of relative path may not be needed. Again, the full lintian warning message seems relevant here. -- Robert Millan "[..] but the delight and pride of Aule is in the deed of making, and in the thing made, and neither in possession nor in his own mastery; wherefore he gives and hoards not, and is free from care, passing ever on to some new work." -- J.R.R.T, Ainulindale (Silmarillion)