Your message dated Sun, 25 Nov 2007 16:11:09 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#412976 acknowledged by developer (closing 412976)
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: mixmaster
Version: 3.0b2-3
Severity: minor

Mixmaster is unconditionally started at boot. The only way to 
disable it is to remove the startup scripts:

  $ find /etc/rc* -name "S*mix*" | xargs rm

SUGGESTION

Please add /etc/default/mixmaster with entry

  ENABLED=1

and "source" it in the /etc/init.d/mixmaster

  DESC="Mixmaster Remailer Daemon"

  ENABLED=""   # Default value
  test -f /etc/default/mixmaster && . /etc/default/mixmaster

  if [ "$ENABLED" = "1" ] || [ "$ENABLED" = "yes" ]; then
     :
  else
      echo "$DESC: disabled, see /etc/default/mixmaster"
      exit 0
  fi


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-3-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)


--- End Message ---
--- Begin Message ---
On Sun, 25 Nov 2007, Jari Aalto wrote:

> > The reason why this will not be implemented has already been explained.
> 
> There is no reply to the last BTS message.

The reason was explained before.  You need to configure mixmaster
anyway, so we use that file right there.

> The current setup does not follow the existing conventions. Also laid
> out in the policy manual; thus repoening the bug.

> !    changes.  To ease the burden on the system administrator, such
> !    configurable values should not be placed directly in the script.

This is not what is happening.  Read it again and maybe you'll
understand.

Peter
-- 
                           |  .''`.  ** Debian GNU/Linux **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/


--- End Message ---

Reply via email to