On 18/03/2008, Lionel Elie Mamane <[EMAIL PROTECTED]> wrote: > user [EMAIL PROTECTED] > usertags 471418 -goal-dash > severity 471418 serious > thanks > > On Mon, Mar 17, 2008 at 09:23:30PM -0600, Raphael Geissert wrote: > > > 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/init.d/capi4hylafax line 15 (local foo=bar): > >> local SPOOL=/var/spool/hylafax/ > > This particular bashism is supported by dash, so on a pragmatic level, > this is not a problem for "dash as /bin/sh".
Yes, sorry for that, I forgot to edit the template. > > It is still a serious bug, though, because according to policy only > local a > a=foo > can be used and not > local a=foo > > (Policy 10.4) I've already discussed about the severity of these issues and some people have said that using bashisms in /bin/sh scripts does not qualify for RC. Based on the way I parse the RC policy for lenny[1] I would also say that they are RC bugs, so please feel free to express your opinion (probably on -devel and -release) if you want to support this idea. [1]http://release.debian.org/lenny/rc_policy.txt > > > 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 > > I suggest you also include a link to Debian Policy 10.4, which > contains the actual information of what /bin/sh scripts may and may > not do. None of the links you gave explained whether local was allowed > at all or not, etc. Just added to the template, thanks :). > > -- > > Lionel > Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html Say NO to Microsoft Office broken standard. See http://www.noooxml.org/petition Earth Hour 2008 - Take action! http://www.earthhour.org/user/xJKk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
