Your message dated Sat, 8 Mar 2008 23:37:11 -0500
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: More on bashisms]
has caused the Debian Bug report #468699,
regarding shorewall-common: bashism in /bin/sh script
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 [EMAIL PROTECTED]
immediately.)
--
468699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468699
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: shorewall-common
Severity: important
Version: VERSION
User: [EMAIL PROTECTED]
Usertags: goal-dash
Hello maintainer,
While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing a /bin/sh script making
use of a bashism.
checkbashisms' output:
> possible bashism in ./sbin/shorewall line 253 (EXP: local foo=bar):
> local sc=${SHELLSHAREDIR}/compiler
> possible bashism in ./sbin/shorewall line 254 (EXP: local foo=bar):
> local pc=${PERLSHAREDIR}/compiler.pl
> possible bashism in ./sbin/shorewall line 261 (EXP: local foo=bar):
> local command=$1
> possible bashism in ./sbin/shorewall line 366 (EXP: local foo=bar):
> local finished=0
> possible bashism in ./sbin/shorewall line 369 (EXP: local foo=bar):
> local rc=0
> possible bashism in ./sbin/shorewall line 495 (EXP: local foo=bar):
> local finished=0
> possible bashism in ./sbin/shorewall line 587 (EXP: local foo=bar):
> local finished=0
> possible bashism in ./sbin/shorewall line 665 (EXP: local foo=bar):
> local finished=0 rc=0
> possible bashism in ./sbin/shorewall line 748 (EXP: local foo=bar):
> local finished=0
> possible bashism in ./sbin/shorewall line 815 (EXP: local foo=bar):
> local finished=0
> possible bashism in ./sbin/shorewall line 953 (EXP: local foo=bar):
> local finished=0 timeout=
> possible bashism in ./sbin/shorewall line 1098 (EXP: local foo=bar):
> local verbose=$(make_verbose) file= capabilities= finished=0 saveit=
> result directory system getcaps= root=root compiler= possible bashism in
> ./sbin/shorewall line 1211 (EXP: local foo=bar): local
> verbose=$(make_verbose) file= finished=0 directory target compiler=
> possible bashism in ./sbin/shorewall line 1422 (EXP: local foo=bar): local
> finished=0 all=
> possible bashism in ./sbin/shorewall line 1518 ($HOST(TYPE|NAME)):
> banner="Shorewall-$version Status at $HOSTNAME -"
> possible bashism in ./sbin/shorewall line 1614 ($HOST(TYPE|NAME)):
> echo "Shorewall-$version Status at $HOSTNAME - $(date)"
> possible bashism in ./sbin/shorewall line 1660 ($HOST(TYPE|NAME)):
> banner="Shorewall-$version Logwatch at $HOSTNAME -"
Not using bash as /bin/sh would lead to errors or unexpected behaviours.
Please be aware that although
bash is currently the default /bin/sh there's a release goal for Lenny to
make dash the default /bin/sh[1].
If you want more information about dash as /bin/sh, you can read:
http://lists.debian.org/debian-release/2008/01/msg00189.html
https://wiki.ubuntu.com/DashAsBinSh
[1]http://release.debian.org/lenny/goals.txt
Thank you,
--
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 ---
This is not a bug, and so I am closing it.
----- Forwarded message from Tom Eastep <[EMAIL PROTECTED]> -----
Date: Sun, 02 Mar 2008 19:32:12 -0800
Subject: More on bashisms
From: Tom Eastep <[EMAIL PROTECTED]>
To: "Roberto C. Sanchez" <[EMAIL PROTECTED]>
The end of http://bugs.debian.org/468699 which complains:
> possible bashism in ./sbin/shorewall line 1518 ($HOST(TYPE|NAME)):
> banner="Shorewall-$version Status at $HOSTNAME -"
> possible bashism in ./sbin/shorewall line 1614 ($HOST(TYPE|NAME)):
> echo "Shorewall-$version Status at $HOSTNAME - $(date)"
> possible bashism in ./sbin/shorewall line 1660 ($HOST(TYPE|NAME)):
> banner="Shorewall-$version Logwatch at $HOSTNAME -"
Here's what happens on a Ubuntu system:
[EMAIL PROTECTED]:~# shorewall status
Shorewall-4.0.9 Status at tipper - Sun Mar 2 19:21:55 PST 2008
Shorewall is running
State:Started (Sat Feb 23 09:41:57 PST 2008)
[EMAIL PROTECTED]:~# ls -il /bin/sh
408813 lrwxrwxrwx 1 root root 4 2006-10-22 10:09 /bin/sh -> dash
[EMAIL PROTECTED]:~#
Clearly, the host name (tipper) is properly displayed in the output.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ [EMAIL PROTECTED]
PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
----- End forwarded message -----
--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
signature.asc
Description: Digital signature
--- End Message ---
