Your message dated Wed, 9 Aug 2006 00:53:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing ancient (tagged woody) bugs
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: snort
Version: 1.8.4beta1-3
Severity: important

In the /etc/snort/snort.conf the section on databases says....
# See the README.database file for more information about configuring
# and using this plugin.

But README.database does not exist

-- System Information
Debian Release: 3.0
Kernel Version: Linux stolberg 2.4.19 #3 SMP Sun Oct 27 09:25:06 NZDT 2002 i686 
unknown

Versions of the packages snort depends on:
ii  adduser        3.47           Add and remove users and groups
ii  debconf        1.0.32         Debian configuration management system
ii  libc6          2.2.5-11.5     GNU C Library: Shared libraries and Timezone
ii  libpcap0       0.6.2-2        System interface for user-level packet captu
ii  snort-common   1.8.4beta1-3   Flexible NIDS (Network Intrusion Detection S
ii  sysklogd       1.4.1-10       System Logging Daemon
        ^^^ (Provides virtual package syslogd)
ii  sysklogd       1.4.1-10       System Logging Daemon
        ^^^ (Provides virtual package system-log-daemon)
ii  snort-rules-de 1.8.4beta1-3   Flexible NIDS (Network Intrusion Detection S
        ^^^ (Provides virtual package snort-rules)


--- End Message ---
--- Begin Message ---
Hi,

This bug has been open for quite a long time and it is tagged 'woody'. As the
latest Debian release 3.1 'sarge' has been available since last year and this
bugs do not seem to be present there I'm closing this bug.

Please reopen the bug if you have evidence that this bug is still present in
newer versions of the package. Any additional information would also be
really useful.

Thanks

Javier

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to