Package: nodm
Version: 0.2
Severity: important
Tags: patch

When I install nodm on a machine where sh == dash:
         
 Unpacking nodm (from .../apt/archives/nodm_0.2_i386.deb) ...
 Processing triggers for man-db ...
 Setting up nodm (0.2) ...
 [: 74: false: unexpected operator
 [: 74: false: unexpected operator
 Press return to continue.

And even though I've left it configured with the default
NODM_ENABLED value of "false", it starts.  This is caused by a
bashism in the initscript; checkbashisms says

  possible bashism in /etc/init.d/nodm line 52 (should be 'b = a'):
        if [ "$NODM_ENABLED" == "no" ] || [ "$NODM_ENABLED" == "false" ]

That is, it should be

        if [ "$NODM_ENABLED" = "no" ] || [ "$NODM_ENABLED" = "false" ]

This fails the Lenny release goal of dash-compatibility, so it should
probably count as release-critical, but I'll call it "important".

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages nodm depends on:
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  libc6                         2.9-4      GNU C Library: Shared libraries
ii  libpam0g                      1.0.1-9    Pluggable Authentication Modules l
ii  x11-common                    1:7.3+18   X Window System (X.Org) infrastruc
ii  xinit                         1.1.1-1    X server initialisation tool
ii  xterm [x-terminal-emulator]   242-1      X terminal emulator

nodm recommends no packages.

nodm suggests no packages.

-- debconf information:
  nodm/xinit: /usr/bin/xinit
  nodm/xsession: /etc/X11/Xsession
  nodm/x_options: vt7 -nolisten tcp
  nodm/min_session_time: 60
* nodm/enabled: false
  nodm/user: root

-- 
JBR
Ankh kak! (Ancient Egyptian blessing)



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to