Your message dated Wed, 02 Apr 2008 23:02:30 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468689: fixed in nessus-plugins 2.2.10-4
has caused the Debian Bug report #468689,
regarding nessus-plugins: 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.)


-- 
468689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468689
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: nessus-plugins
Severity: important
Version: 2.2.10-3
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/nessus-build line 24 ($RANDOM):
> NESSUS_BUILD="nessus-build.$RANDOM"


Not using bash as /bin/sh would lead to errors or unexpected behaviours. 
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: nessus-plugins
Source-Version: 2.2.10-4

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

nessus-plugins_2.2.10-4.diff.gz
  to pool/main/n/nessus-plugins/nessus-plugins_2.2.10-4.diff.gz
nessus-plugins_2.2.10-4.dsc
  to pool/main/n/nessus-plugins/nessus-plugins_2.2.10-4.dsc
nessus-plugins_2.2.10-4_i386.deb
  to pool/main/n/nessus-plugins/nessus-plugins_2.2.10-4_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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated 
nessus-plugins 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 [EMAIL PROTECTED])


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

Format: 1.7
Date: Thu, 03 Apr 2008 00:29:08 +0200
Source: nessus-plugins
Binary: nessus-plugins
Architecture: source i386
Version: 2.2.10-4
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description: 
 nessus-plugins - Nessus plugins
Closes: 468689
Changes: 
 nessus-plugins (2.2.10-4) unstable; urgency=low
 .
   * Make the nessus-build script use bash since it uses the RANDOM
     construct (Closes: #468689)
   * Remove the patch/unpatch code from debian/rules, move the diff files
     over to extra/ and provide the patched files directly
Files: 
 994ad5fb9c61ccda86d2adb345ce9c5a 718 admin optional nessus-plugins_2.2.10-4.dsc
 49c1b876fd5be294cd5e77d6624d84a2 3343670 admin optional 
nessus-plugins_2.2.10-4.diff.gz
 6ff1b778b0461556ba57009127798848 2783650 admin optional 
nessus-plugins_2.2.10-4_i386.deb

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

iD8DBQFH9AwesandgtyBSwkRApkHAJ0QFVc/BVi0L+vRy5e8APkCljJlfACeK5lt
8TAKJ4gBfN5YnquY04gtZAg=
=y8A8
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to