Your message dated Sat, 29 Aug 2009 22:32:24 +0000
with message-id <[email protected]>
and subject line Bug#535878: fixed in nsd3 3.2.3-1
has caused the Debian Bug report #535878,
regarding nsd3: 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.)
--
535878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535878
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nsd3
Severity: important
Version: 3.2.2-1
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/sbin/nsdc line 207 (should be >word 2>&1):
> kill -TERM ${pid} &>/dev/null
> possible bashism in ./usr/sbin/nsdc line 211 (should be >word 2>&1):
> kill -0 ${pid} &>/dev/null
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][3].
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
[3]http://lists.debian.org/debian-devel/2009/06/msg00767.html
Thank you,
Raphael Geissert
--- End Message ---
--- Begin Message ---
Source: nsd3
Source-Version: 3.2.3-1
We believe that the bug you reported is fixed in the latest version of
nsd3, which is due to be installed in the Debian FTP archive:
nsd3_3.2.3-1.diff.gz
to pool/main/n/nsd3/nsd3_3.2.3-1.diff.gz
nsd3_3.2.3-1.dsc
to pool/main/n/nsd3/nsd3_3.2.3-1.dsc
nsd3_3.2.3-1_amd64.deb
to pool/main/n/nsd3/nsd3_3.2.3-1_amd64.deb
nsd3_3.2.3.orig.tar.gz
to pool/main/n/nsd3/nsd3_3.2.3.orig.tar.gz
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.
Pierre Habouzit <[email protected]> (supplier of updated nsd3 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.8
Date: Sun, 30 Aug 2009 00:21:05 +0200
Source: nsd3
Binary: nsd3
Architecture: source amd64
Version: 3.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Pierre Habouzit <[email protected]>
Changed-By: Pierre Habouzit <[email protected]>
Description:
nsd3 - authoritative domain name server (3.x series)
Closes: 535878 539979 543580
Changes:
nsd3 (3.2.3-1) unstable; urgency=low
.
* New upstream release.
* Pass SHELL=/bin/bash to make so that nsdc.sh gets the proper shebang
(Closes: #535878).
* Disable largefile as it breaks architectures not allowing unaligned
8-bytes access, and it's likely to be a problem for nsd3
(Closes: #539979).
* Make init.d read more values from the actual configuration using
nsd-checkconf -o, and do less stuff if people are using chrooted stuff,
because we probably aren't doing it right (Closes: #543580).
Checksums-Sha1:
0b5b32b49bd0dbb43593a2656fa8c2cbb5f7a38e 1091 nsd3_3.2.3-1.dsc
2afcc6e1086eef7f5e538c7d837f628f83a19a86 855917 nsd3_3.2.3.orig.tar.gz
b896606dabb954397bec81ac320f9cf2637c8347 7728 nsd3_3.2.3-1.diff.gz
7d2c0cb0da9bf99aed945f276dc645e94d3930cc 907024 nsd3_3.2.3-1_amd64.deb
Checksums-Sha256:
bcc9764dbe108caf47a11fbe16223857a68938b517fa59a1050a601a68dff888 1091
nsd3_3.2.3-1.dsc
2a9b4cb63b002a2a63ec8243f90a9e041f08b9498faa5b35ca71ce3334d842ff 855917
nsd3_3.2.3.orig.tar.gz
9ae76c89246923f911bf35ccfdade6e1c3286e6be466ec725e4d0fd4c6006e19 7728
nsd3_3.2.3-1.diff.gz
a0233cb322913c72a9288f16312f6511846dde347dbc7a4208ea16460c1ffa75 907024
nsd3_3.2.3-1_amd64.deb
Files:
566bca1ccd1901c0d1f56a64304d302e 1091 net extra nsd3_3.2.3-1.dsc
5ddb35dfb7da0defb82cda4f7388cba2 855917 net extra nsd3_3.2.3.orig.tar.gz
fd507b21ad68b1961395123369bbca91 7728 net extra nsd3_3.2.3-1.diff.gz
26fd17ac2cd474994c21cbd28d380274 907024 net extra nsd3_3.2.3-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqZqhQACgkQvGr7W6HudhwPtgCgqZS6s/RqXMsA2skd1So5m/jw
kxkAn2SldCdrtp4G/VZvvvKelky1MvZO
=DH9L
-----END PGP SIGNATURE-----
--- End Message ---
