User: [EMAIL PROTECTED]
While performing an archive wide checkbashisms (from the 'devscripts' package)
check I've found your package containing one or more /bin/sh scripts making
use of bashisms.
> possible bashism in ./usr/share/apps/kile/test/runTests.sh line 15
> declare -i totalnotests=17
> possible bashism in ./usr/share/apps/kile/test/runTests.sh line 16
> declare -i current=0
> possible bashism in ./usr/share/apps/kile/test/runTests.sh line 42
> declare -i result=$?
> possible bashism in ./usr/share/apps/kile/test/runTests.sh line 56
> declare -i result=`$kileDCOP $*`
Not using bash (or a Debian Policy conformant shell interpreter which does
provide such an extra feature) as /bin/sh is likely to lead to errors or
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.
If you want more information about dash as /bin/sh, you can read:
For more information please refer to the Debian Policy section 10.4 supporting
this argument at:
Hints about how to fix bashisms:
Sometimes these bugs are already fixed in Ubuntu, look at the PTS.
If not already fixed you can read:
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
pkg-kde-extras mailing list