Your message dated Sun, 06 Jan 2008 10:52:15 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#459407: lintian: unusual-interpreter /usr/bin/env
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: lintian
Version: 1.23.41
Severity: normal
Lintian reports /usr/bin/env as an unusual-interpreter. However, many
python scripts use "#!/usr/bin/env python" to find python on the path
rather than assuming a particular location. Lintian should allow
/usr/bin/env as an interpreter. Better yet, it should special-case
/usr/bin/env and look at the second argument to determine the
interpreter, with a whitelist of permissible env-indirect
interpreters; to start with, that list should include python.
- Josh Triplett
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages lintian depends on:
ii binutils 2.18.1~cvs20080103-1 The GNU assembler, linker and bina
ii diffstat 1.45-2 produces graph of changes introduc
ii dpkg-dev 1.14.14 package building tools for Debian
ii file 4.21-4 Determines file type using "magic"
ii gettext 0.17-2 GNU Internationalization utilities
ii intltool-debian 0.35.0+20060710.1 Help i18n of RFC822 compliant conf
ii libparse-debianchan 1.1.1-1 parse Debian changelogs and output
ii liburi-perl 1.35.dfsg.1-1 Manipulates and accesses URI strin
ii man-db 2.5.0-4 on-line manual pager
ii perl [libdigest-md5 5.8.8-12 Larry Wall's Practical Extraction
lintian recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Russ Allbery wrote:
> Josh Triplett <[EMAIL PROTECTED]> writes:
>> Package: lintian
>> Version: 1.23.41
>> Severity: normal
>>
>> Lintian reports /usr/bin/env as an unusual-interpreter. However, many
>> python scripts use "#!/usr/bin/env python" to find python on the path
>> rather than assuming a particular location. Lintian should allow
>> /usr/bin/env as an interpreter. Better yet, it should special-case
>> /usr/bin/env and look at the second argument to determine the
>> interpreter, with a whitelist of permissible env-indirect interpreters;
>> to start with, that list should include python.
>
> #!/usr/bin/env python is one of the test cases in lintian's test suite, so
> I'm pretty sure it works in general. lintian's script checking logic
> already does implement pretty much exactly what you describe. As Chris
> says, we'll need to see the specific problem that triggered this.
Sigh. Clearly I should have checked more carefully; the script in question
really does just have "#!/usr/bin/env", unlike all the other scripts in the
same package which have "#!/usr/bin/env python". Sorry I missed that;
lintian seems to have done its job here. (Not my package; non-Debian source
which provided a debian directory.)
Closing this bug.
- Josh Triplett
signature.asc
Description: OpenPGP digital signature
--- End Message ---
