Your message dated Tue, 30 Oct 2007 23:33:25 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448564: nfs-common: Bashism in init 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: nfs-common
Version: 1:1.1.1-4
Severity: normal
Tags: patch

Hi

there is a bashism in new init script for nfs-common, attached patch
fixes it.

-- 
        Michal Čihař | http://cihar.com | http://blog.cihar.com


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-common depends on:
ii  adduser               3.105              add and remove users and groups
ii  initscripts           2.86.ds1-38.1      Scripts for initializing and shutt
ii  libc6                 2.6.1-6            GNU C Library: Shared libraries
ii  libcomerr2            1.40.2-1           common error description library
ii  libevent1             1.3d-1             An asynchronous event notification
ii  libgssglue1           0.1-1              mechanism-switch gssapi library
ii  libkrb53              1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries
ii  libnfsidmap2          0.20-0             An nfs idmapping library
ii  librpcsecgss3         0.17-1             allows secure rpc communication us
ii  libwrap0              7.6.dbs-14         Wietse Venema's TCP wrappers libra
ii  lsb-base              3.1-24             Linux Standard Base 3.1 init scrip
ii  netbase               4.30               Basic TCP/IP networking system
ii  portmap               6.0-4              The RPC portmapper
ii  ucf                   3.003              Update Configuration File: preserv

nfs-common recommends no packages.

-- no debconf information
--- /etc/init.d/nfs-common.orig 2007-10-30 11:34:52.000000000 +0900
+++ /etc/init.d/nfs-common      2007-10-30 11:34:59.000000000 +0900
@@ -198,7 +198,7 @@
                 exit $?
             fi
        fi
-       if ["$NEED_STATD" = yes ]
+       if [ "$NEED_STATD" = yes ]
        then
            log_progress_msg "statd"
            start-stop-daemon --stop --oknodo --quiet \

--- End Message ---
--- Begin Message ---
Version: 1:1.1.1-5

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

Format: 1.7
Date: Tue, 30 Oct 2007 22:41:12 +1100
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source amd64
Version: 1:1.1.1-5
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description: 
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 448538 448607
Changes: 
 nfs-utils (1:1.1.1-5) unstable; urgency=low
 .
   * Fixed syntax error in nfs-common. Closes: #448538, #448607.
     Patch by Alban Browaeys <[EMAIL PROTECTED]>
Files: 
 5e0fddb7ebf2098f19ca8715dc6e8bde 860 net standard nfs-utils_1.1.1-5.dsc
 4eaa6a9eb68456e0497e41720fac881e 31294 net standard nfs-utils_1.1.1-5.diff.gz
 92f9d6f192b0833aa48d193db50a831d 330498 net optional 
nfs-kernel-server_1.1.1-5_amd64.deb
 6ec56f75e7a9ef10478b10312d3c7170 413040 net standard 
nfs-common_1.1.1-5_amd64.deb

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

iD8DBQFHJx2egY5NIXPNpFURAjhZAJ9wI1g4ep65gUd+GgwltRBfeQVpMgCgj+/+
amYL2EJ4gNdpJ+Ff5N3Ng0E=
=YLWL
-----END PGP SIGNATURE-----

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to