Your message dated Sat, 30 Dec 2017 22:09:54 +0000 with message-id <1514671794.865090.1219850240.26fed...@webmail.messagingengine.com> and subject line Re: lintian: wrong-path-for-interpreter should not trigger on non-executables has caused the Debian Bug report #762273, regarding wrong-path-for-interpreter should not trigger on non-executables 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: lintian Version: 2.5.27 Severity: normal X-Debbugs-CC: p...@packages.debian.org perl currently suffers from this: E: perl-modules: wrong-path-for-interpreter usr/share/perl/5.20.1/Config/Perl/V.pm (#!/pro/bin/perl != /usr/bin/perl) Now, whilst it is certainly 'wrong', it's also harmless; a perl module (ending .pm) should never be executed (and indeed it's not installed with the executable bit). I imagine that someone put the shebang there as a hint to a syntax highlighter, or similar. Carrying around a patch to strip the shebang line seems like the wrong solution, and there's no generally correct fix to send upstream. Instead, can this check be updated to only look at files with the executable bit set? Thanks, Dominic.
--- End Message ---
--- Begin Message ---retitle 762273 wrong-path-for-interpreter should not trigger on non-executables tags 762273 + wontfix thanks > > lintian: wrong-path-for-interpreter should not trigger on non-executables > > I don't this is the right approach, otherwise we may not find files > installed outside of ${prefix}/bin etc. > > Thus renaming this to exclude .pm files. On second thoughts... I remembered that the usual/canonical way of doing this via using the "#!perl" quasi-shebang. This should — and can — be sent upstream. Thus closing this report. :) Apologies for the unnecessary noise getting here. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
--- End Message ---
