Your message dated Tue, 15 Jul 2008 21:18:52 +0100
with message-id <[EMAIL PROTECTED]>
and subject line gibraltar-bootsupport has been removed from Debian, closing 
#476757
has caused the Debian Bug report #476757,
regarding gibraltar-bootsupport: 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.)


-- 
476757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476757
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gibraltar-bootsupport
Severity: important
Version: 2.1
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 several /bin/sh scripts making 
use of a bashism.

checkbashisms' output:
> possible bashism in ./sbin/update-rollback line 7 (echo -e):
>   echo -e "Rolling back last update ... "
> possible bashism in ./sbin/update-removeold line 7 (echo -e):
>   echo -e "Removing old Gibraltar version ... "
> possible bashism in ./sbin/update-removeold line 24 (echo -e):
>   echo -e "Removing files from last upgrade ... "
> possible bashism in ./sbin/restore-etc-old2 line 54 ((push|pod)d):
>   pushd $mountpoint > /dev/null
> possible bashism in ./sbin/restore-etc-old2 line 61 ((push|pod)d):
>   pushd $mountpoint > /dev/null
> possible bashism in ./sbin/save-etc line 66 ((push|pod)d):
>   pushd $maskingmountpoint > /dev/null
> possible bashism in ./sbin/restore-etc line 68 ((push|pod)d):
>     pushd $maskingmountpoint > /dev/null
> possible bashism in ./sbin/restore-etc line 76 ((push|pod)d):
>   pushd $mountpoint > /dev/null
> possible bashism in ./etc/init.d/update-finalize line 8 (echo -e):
>   echo -e "Finalizing update now ... "
> possible bashism in ./etc/init.d/setup-unconfigured.sh line 37 (echo -e):
>   echo -e "This is an ${COLOR_RED}unconfigured${COLOR_NORMAL} system."\

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 
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

For more information please refer to the Debian Policy section 10.4 supporting 
this argument at:
http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

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:
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 ---
Version: 2.1+rm

The gibraltar-bootsupport package has been removed from Debian testing, 
unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/489721 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org


--- End Message ---

Reply via email to