[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#547765: marked as done (speakup-tools: bashism in /bin/sh script)

Your message dated Fri, 30 Oct 2009 00:25:10 +0100
with message-id <20091029232510.GI4692@const.famille.thibault.fr>
and subject line Fixed in 3.1.3-3
has caused the Debian Bug report #547765,
regarding speakup-tools: 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 owner@bugs.debian.org
immediately.)


-- 
547765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547765
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: speakup-tools
Severity: important
Version: 3.1.3-1
User: debian-release@lists.debian.org
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 ./usr/sbin/talkwith line 74 (should be >word 2>&1):
>	  if which espeakup >& /dev/null; then
> possible bashism in ./usr/sbin/talkwith line 77 (should be >word 2>&1):
>	  if which speechd-up >& /dev/null; then


Not using bash (or a Debian Policy conformant shell interpreter which 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 now the default /bin/sh.

Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh

If you still don't know how to fix the bashisms don't hesitate to reply to
this email, or tag the bug as 'help'.

Thank you,
Raphael Geissert

--- End Message ---
--- Begin Message --- 
Version: 3.1.3-3

Hello,

I forgot to close this bug in the 3.1.3-3 changelog.

Samuel

--- End Message ---
Reply to: