Hi Raphael, Thanks for the bug report. This is not a problem (for jessie, or at all), correct at minor severity or maybe wont-fix.
On Sat, Dec 06, 2014 at 14:59:40 +0100, Raphael Geissert wrote: > 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/share/vpnc-scripts/vpnc-script-sshd line 194 > > (sleep only takes one integer): > > sleep 0.1 > > possible bashism in ./usr/share/vpnc-scripts/vpnc-script-sshd line 222 > > (sleep only takes one integer): > > sleep 0.1 > > possible bashism in ./usr/share/vpnc-scripts/vpnc-script-sshd line 288 > > (sleep only takes one integer): > > sleep 0.1 > > possible bashism in ./usr/share/vpnc-scripts/vpnc-script line 615 (sleep > > only takes one integer): > > sleep 0.1 > > > 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. Agree with the general principle of shell portability, but I fail to see how this specific instance is a bashism. If anything, this is a GNU-ism of the coreutils package. The sleep command does seem to a be a ksh builtin, but is not a bash builtin. The same sleep command is used whether the shell interpreter is dash or bash or posh. $ time dash -c "sleep 0.5" real 0m0.505s user 0m0.004s sys 0m0.000s So this bashism check seems to be a false positive at best. -- mike
signature.asc
Description: Digital signature
