Your message dated Sun, 10 Feb 2008 21:37:01 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#463193: checkbashisms: "script $filename does not appear
to be a /bin/sh script" on csh scripts and others
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: devscripts
Version: 2.10.13
User: [EMAIL PROTECTED]
Usertags: checkbashisms
On scripts with a /bin/csh shebang and other scripts with a
non /bin/{sh,ash,dash} shebang checkscripts quits without processing them.
The portion of code is:
elsif ($interpreter !~ m,/(sh|ash|dash)$,) {
It should instead use something like:
elsif ($interpreter !~ m,/[a-z]*(sh)$,) {
Kind regards,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--- End Message ---
--- Begin Message ---
Hi,
On Fri, 2008-02-01 at 17:24 -0600, Raphael Geissert wrote:
[...]
> Ack. But at least posh's description says:
>
> > posh is a stripped-down version of pdksh that aims for compliance
> > with Debian's policy, and few extra features.
> > .
> > WARNING: Since many of Debian's /bin/sh scripts are not actually
> > policy-compliant, using posh as your /bin/sh may reveal breakage.
>
> So it might worth to be added to the list.
I've now added posh to the list of supported shells; thanks for the
suggestion.
I am, however, closing this bug as it's intentional that the files you
mentioned not be checked.
Regards,
Adam
--- End Message ---
