Your message dated Mon, 25 May 2009 21:37:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#530120: libtool: bashism in /bin/sh script
has caused the Debian Bug report #530120,
regarding libtool: depcomp should not rely on the behaviour of echo regarding
backslashes
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.)
--
530120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530120
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libtool
Severity: important
Version: 2.2.6a-4
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 ./usr/bin/libtoolize line 492 ($RANDOM):
> my_tmpdir="${my_template}-${RANDOM-0}$$"
> possible bashism in ./usr/share/libtool/config/depcomp line 139 (unsafe
> echo with backslash):
> echo "$object : \\" > "$depfile"
> possible bashism in ./usr/share/libtool/config/depcomp line 183 (unsafe
> echo with backslash):
> echo "$object : \\" > "$depfile"
> possible bashism in ./usr/share/libtool/config/depcomp line 533 (unsafe
> echo with backslash):
> echo "$object : \\" > "$depfile"
> possible bashism in ./usr/share/libtool/config/depcomp line 563 (unsafe
> echo with backslash):
> echo "$object : \\" > "$depfile"
> possible bashism in ./usr/share/libtool/config/install-sh line 341
> ($RANDOM):
> tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
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 ---
On Sun, May 24, 2009 at 02:49:15PM -0500, Raphael Geissert wrote:
>
> First of all removing the goal-dash user tag since it isn't relevant for it.
> After checking busybox's sh, dash, posh, pdksh, mksh, zsh, bash, and ksh I've
> confirmed that they all print the desired result.
> But just for the sake of conforming to SUSv3's recommendations I'm leaving
> this bug open. I don't think switching to printf would do any harm, and who
> knows, there might actually be a sh implementation that doesn't behave that
> way.
I'm just going to close this bug in that case. Upstream
libtool will probably notice if there really is a portability
issue.
Kurt
--- End Message ---
