Your message dated Tue, 16 Oct 2012 22:18:24 +0200
with message-id <[email protected]>
and subject line Re: Bug#690709: grml-debootstrap: bashism in /bin/sh script
has caused the Debian Bug report #690709,
regarding grml-debootstrap: 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.)
--
690709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690709
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grml-debootstrap
Version: 0.53
Severity: important
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 a /bin/sh script making
use of a bashism.
checkbashisms' output:
>possible bashism in ./etc/debootstrap/chroot-script line 307 ($HOST(TYPE|
NAME)):
> sed -i "s#127.0.0.1 .*#127.0.0.1 localhost $HOSTNAME#"
> /etc/hosts
>possible bashism in ./etc/debootstrap/chroot-script line 308 ($HOST(TYPE|
NAME)):
> [ -n "$HOSTNAME" ] && sed -i "s/grml/$HOSTNAME/g" /etc/hosts
>possible bashism in ./etc/debootstrap/chroot-script line 396 ($HOST(TYPE|
NAME)):
> if [ -n "$HOSTNAME" ] ; then
>possible bashism in ./etc/debootstrap/chroot-script line 397 ($HOST(TYPE|
NAME)):
> echo "Setting hostname to ${HOSTNAME}."
>possible bashism in ./etc/debootstrap/chroot-script line 398 ($HOST(TYPE|
NAME)):
> echo "$HOSTNAME" > /etc/hostname
>possible bashism in ./etc/debootstrap/chroot-script line 403 ($HOST(TYPE|
NAME)):
> sed -i "s/grml/$HOSTNAME/g" /etc/postfix/main.cf
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.
You can find hints about how to fix bashisms at:
https://wiki.ubuntu.com/DashAsBinSh
Thank you,
Raphael Geissert
--- End Message ---
--- Begin Message ---
* Raphael Geissert [Tue Oct 16, 2012 at 12:47:43PM -0500]:
> 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 ./etc/debootstrap/chroot-script line 307 ($HOST(TYPE|
> NAME)):
[...]
This is a false positive, we explicitely set the HOSTNAME variable
in our scripts.
regards,
-mika-
signature.asc
Description: Digital signature
--- End Message ---
