Your message dated Fri, 19 Dec 2014 20:21:35 +0000
with message-id <[email protected]>
and subject line Re: Bug#772219: cluster-glue: bashism in /bin/sh script
has caused the Debian Bug report #772219,
regarding cluster-glue: 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.)
--
772219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772219
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cluster-glue
Severity: serious
Version: 1.0.12~rc1+hg2777-1.2
User: [email protected]
Usertags: goal-dash
Hi,
I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
"bashism".
checkbashisms' output:
> possible bashism in ./usr/sbin/hb_report line 1219 ($BASH_SOMETHING):
> [ ${BASH_VERSINFO[0]} = "4" ]; then
> possible bashism in ./usr/sbin/hb_report line 1219 (bash arrays,
> ${name[0|*|@]}):
> [ ${BASH_VERSINFO[0]} = "4" ]; then
> possible bashism in ./usr/sbin/hb_report line 1221 (BASH(_SOMETHING)=):
> BASH_XTRACEFD=3
> possible bashism in ./usr/lib/stonith/plugins/external/ippower9258 line 72
> (<<< here string):
> $LOG_ERROR "Received Challenge = <<<$challenge>>>."
> possible bashism in ./usr/lib/stonith/plugins/external/ippower9258 line 73
> (<<< here string):
> $LOG_ERROR "Sent postdata = <<<$postdata>>>."
Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.
Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.
Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh
Thanks in advance,
Raphael Geissert
--- End Message ---
--- Begin Message ---
Control: notfound -1 1.0.12~rc1+hg2777-1.2
These are all false positives:
On Sat, Dec 06, 2014 at 11:56:38AM +0100, Raphael Geissert wrote:
> checkbashisms' output:
> > possible bashism in ./usr/sbin/hb_report line 1219 ($BASH_SOMETHING):
> > [ ${BASH_VERSINFO[0]} = "4" ]; then
> > possible bashism in ./usr/sbin/hb_report line 1219 (bash arrays,
> > ${name[0|*|@]}):
> > [ ${BASH_VERSINFO[0]} = "4" ]; then
> > possible bashism in ./usr/sbin/hb_report line 1221 (BASH(_SOMETHING)=):
> > BASH_XTRACEFD=3
Wrapped in a guard which tests for the bash shell.
> > possible bashism in ./usr/lib/stonith/plugins/external/ippower9258 line 72
> > (<<< here string):
> > $LOG_ERROR "Received Challenge = <<<$challenge>>>."
> > possible bashism in ./usr/lib/stonith/plugins/external/ippower9258 line 73
> > (<<< here string):
> > $LOG_ERROR "Sent postdata = <<<$postdata>>>."
Just exotic formatting of the log messages.
Thanks,
--
Jonathan Wiltshire [email protected]
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
signature.asc
Description: Digital signature
--- End Message ---