[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#465349: marked as done (metamail: bashism in /bin/sh script)

Your message dated Sat, 08 Mar 2008 23:47:13 +0000
with message-id <E1JY8kz-0004zz-SM@ries.debian.org>
and subject line Bug#465349: fixed in metamail 2.7-54
has caused the Debian Bug report #465349,
regarding metamail: 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 owner@bugs.debian.org
immediately.)


-- 
465349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465349
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: metamail
Severity: important
Version: 2.7-53
User: debian-release@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/bin/showaudio line 264 (should be 'b = a'):
>         if test "$thishost" == "$AUDIOPHONEHOST" \
> possible bashism in ./usr/bin/showaudio line 265 (should be 'b = a'):
>                 -o "$thishost" == "$AUDIOPHONEHOSTLONG"


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 --- 
Source: metamail
Source-Version: 2.7-54

We believe that the bug you reported is fixed in the latest version of
metamail, which is due to be installed in the Debian FTP archive:

metamail_2.7-54.diff.gz
  to pool/main/m/metamail/metamail_2.7-54.diff.gz
metamail_2.7-54.dsc
  to pool/main/m/metamail/metamail_2.7-54.dsc
metamail_2.7-54_i386.deb
  to pool/main/m/metamail/metamail_2.7-54_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 465349@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marc 'HE' Brockschmidt <he@debian.org> (supplier of updated metamail package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 09 Mar 2008 00:36:59 +0100
Source: metamail
Binary: metamail
Architecture: source i386
Version: 2.7-54
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Marc 'HE' Brockschmidt <he@debian.org>
Description: 
 metamail   - implementation of MIME
Closes: 465349
Changes: 
 metamail (2.7-54) unstable; urgency=low
 .
   * QA upload.
   * Fix bashisms in bin/showaudio. checkbashisms reports false positives
     in patch-metamail ($HOSTNAME is defined in that script). (Closes: #465349)
Files: 
 7115fa3a532df2d18224a8e8dd1df84c 597 mail optional metamail_2.7-54.dsc
 2071dc7b9c33345443ab9a619e640a69 324193 mail optional metamail_2.7-54.diff.gz
 b1bf2de75e336b441a02ca03a9b01925 156192 mail optional metamail_2.7-54_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH0yOmmO5zOp3h7rERAuVMAJ9fB5TNDzVLur0mum3UPs5UIZoJtwCfTWqh
36xdLuZ/zZBQauaqINbdzDM=
=rnXF
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: