Bill Allombert wrote: > On Mon, Nov 27, 2017 at 09:10:12PM +0100, Bill Allombert wrote: >> On Mon, Nov 27, 2017 at 11:34:15AM -0600, Gunnar Wolf wrote: >>> Sean Whitton dijo [Sat, Oct 14, 2017 at 11:49:59AM -0700]:
>>>> I am seeking seconds for the following patch to close this bug, which I >>>> think is uncontroversial at this point. >>>> >>>>> @@ -185,7 +185,7 @@ All command scripts, including the package maintainer >>>>> scripts inside the >>>>> package and used by ``dpkg``, should have a ``#!`` line naming the shell >>>>> to be used to interpret them. >>>>> >>>>> -In the case of Perl scripts this should be ``#!/usr/bin/perl``. >>>>> +In the case of Perl scripts this must be ``#!/usr/bin/perl``. >>>>> >>>>> When scripts are installed into a directory in the system PATH, the >>>>> script name should not include an extension such as ``.sh`` or ``.pl`` >>> >>> Seconded. >> >> Before we make it a must, is there a lintian test for it ? >> How may packages need to be fixed ? > > Given Russ answer about the lintian test and result, I second this > proposal. Seconded as well. Thanks! Jonathan