Your message dated Thu, 07 Feb 2008 20:51:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#464632: autoconf2.13: bashism in /bin/sh script has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: autoconf2.13 Severity: important Version: 2.13-59 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 ./usr/bin/autoupdate2.13 line 70 (trap with signal > numbers): trap 'rm -f $sedtmp $tmpout; exit 1' 1 2 15 > possible bashism in ./usr/bin/ifnames2.13 line 62 ('function' is useless): > function file_sym(sym, i, fs) { > possible bashism in ./usr/bin/autoconf2.13 line 99 (trap with signal > numbers): trap 'rm -f $tmpin $tmpout; exit 1' 1 2 15 > possible bashism in ./usr/bin/autoheader2.13 line 144 (trap with signal > numbers): trap "rm -f $tmpout; exit 1" 1 2 15 > possible bashism in ./usr/bin/autoheader2.13 line 198 (trap with signal > numbers): trap "rm -f $fgrep_tmp; exit 1" 1 2 15 Not using bash as /bin/sh would lead to errors. 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 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 ---Raphael Geissert <[EMAIL PROTECTED]> writes: > 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. It really seems quite unlikely that Autoconf would contain bashisms. I believe that these are false positives, so I am closing the bug report. Details follow: > checkbashisms' output: >> possible bashism in ./usr/bin/autoupdate2.13 line 70 (trap with signal >> numbers): trap 'rm -f $sedtmp $tmpout; exit 1' 1 2 15 >> possible bashism in ./usr/bin/autoconf2.13 line 99 (trap with signal >> numbers): trap 'rm -f $tmpin $tmpout; exit 1' 1 2 15 >> possible bashism in ./usr/bin/autoheader2.13 line 144 (trap with signal >> numbers): trap "rm -f $tmpout; exit 1" 1 2 15 >> possible bashism in ./usr/bin/autoheader2.13 line 198 (trap with signal >> numbers): trap "rm -f $fgrep_tmp; exit 1" 1 2 15 I think that checkbashism is being too stringent here, as XSI-conformant systems must accept these numeric signals (and some others). >> possible bashism in ./usr/bin/ifnames2.13 line 62 ('function' is useless): >> function file_sym(sym, i, fs) { This instance of "function" is within an awk program embedded in the shell script. -- "I consider that the golden rule requires that if I like a program I must share it with other people who like it." --Richard Stallman
--- End Message ---
