> example-unusual-interpreter incorrectly flags "#!/usr/bin/env python" as being
> problematic. This feels like a new behavior, because I have many packages
> with files with this shebang and have never had an issue before.
I don’t see how this is incorrect, as python does not exist anymore on pristine
debian systems.
A small reproducer:
$ /bin/cat reproducer.py
#!/usr/bin/env python
print("hello”)
$ ./reproducer.py
env: ‘python’: No such file or directory
> However, perhaps it only flags them incorrectly if they are shipped as
> examples.
Yes, there are2 tags: "unusual-interpreter” and "example-unusual-interpreter”.
I looked up codesearch and see a bunch of patches fixing the interpreter[1]. In
this case, this is an
Issue with your package rather than lintian. If you agree, please close this
bug report.
[1]
https://codesearch.debian.net/search?q=env+python3+path%3Adebian%2Fpatches&literal=1&page=170
