Your message dated Thu, 14 Jan 2010 00:01:56 +0100
with message-id <20100113230156.ga4...@gandalf.is-a-geek.org>
and subject line Fixed in current snapshot of 6.4
has caused the Debian Bug report #530092,
regarding grass: 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 ow...@bugs.debian.org
immediately.)


-- 
530092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grass
Severity: important
Version: 6.4.0~rc4-3
User: debian-rele...@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/lib/grass64/scripts/mkftcap line 34 (should be
> >word 2>&1):
>     if which fc-list >&/dev/null ; then
> possible bashism in ./usr/lib/grass64/scripts/d.m line 13
> ($HOST(TYPE|NAME)):
>         if [ "$HOSTTYPE" = "macintosh" -o "$HOSTTYPE" = "powermac" -o
> "$HOSTTYPE" = "powerpc" -o "$HOSTTYPE" = "intel-pc" ] ; then
> possible bashism in ./usr/lib/grass64/etc/grass-run.sh line 5 ($BASH):
> if [ "$TERM" = "xterm" ] && [ -n "$BASH" ] ; then
> possible bashism in ./usr/lib/grass64/etc/grass-run.sh line 7 (echo -e):
>    echo -e "\033]0;${TITLE}\007\c"
> possible bashism in ./usr/lib/grass64/etc/grass-run.sh line 35 (should be
> read [-r] variable):
>    read
> possible bashism in ./usr/lib/grass64/etc/Init.sh line 330
> ($HOST(TYPE|NAME)):
> if [ "$HOSTTYPE" = "arm" ] ; then
> possible bashism in ./usr/lib/grass64/etc/Init.sh line 859 (unsafe echo
> with backslash):
>     echo "set prompt = '\\" >> "$cshrc"
> possible bashism in ./usr/lib/grass64/etc/Init.sh line 860 (unsafe echo
> with backslash):
>     echo "Mapset <${MAPSET}> in Location <${LOCATION_NAME}> \\" >> "$cshrc"


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 although bash is currently the default /bin/sh there was
a release goal for Lenny to make dash the default /bin/sh[1], and has been
proposed for squeeze as well[2].

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 supporting this goal please refer to Debian Policy,
section 10.4, 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

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

[1]http://release.debian.org/lenny/goals.txt
[2]http://lists.debian.org/debian-release/2009/04/msg00133.html

Thank you,
Raphael Geissert



--- End Message ---
--- Begin Message ---
Package: grass
Version: 6.4.0~rc5+40109-1 

As explained in the report the bashism issues seem definitively fixed.
So, I'm closing this bug.

-- 
Francesco P. Lovergine


--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel

Reply via email to