Your message dated Thu, 25 Aug 2005 13:32:29 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291616: fixed in snort 2.3.2-6
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Aug 2003 07:46:01 +0000
>From [EMAIL PROTECTED] Sat Aug 16 02:45:59 2003
Return-path: <[EMAIL PROTECTED]>
Received: from apate.telenet-ops.be [195.130.132.57] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 19nvl9-0002aO-00; Sat, 16 Aug 2003 02:45:59 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
        by apate.telenet-ops.be (Postfix) with SMTP
        id 74B8437EE8; Sat, 16 Aug 2003 09:45:58 +0200 (MEST)
Received: from hawking.home.de-brauwer.be (D5E06620.kabel.telenet.be 
[213.224.102.32])
        by apate.telenet-ops.be (Postfix) with ESMTP
        id 2535337E42; Sat, 16 Aug 2003 09:45:58 +0200 (MEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Elie De Brauwer <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: snort-mysql: Problem in installation scripts related to database 
creation
Reply-To: Elie De Brauwer <[EMAIL PROTECTED]>
X-Mailer: reportbug 2.22
Date: Sat, 16 Aug 2003 09:45:58 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-6.0 required=4.0
        tests=BAYES_30,HAS_PACKAGE
        version=2.53-bugs.debian.org_2003_8_15
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_15 
(1.174.2.15-2003-03-30-exp)

Package: snort-mysql
Version: 2.0.0-3.2
Severity: normal

When you apt-get install snort-mysql, you get a number of questions related to 
which database to use, which user, which password etc. The last of those 
questions is a remark stating the following:

Please create the database structure now using the following command
cd /usr/share/doc/snort-mysql/contrib 
 zcat create-mysql.gz | mysql -u <user> ....
After you created the database structure like this, press 'ok' to continue.

Now the problem is the following, this is a PRE installation script, so the
directory /usr/share/doc/snort-mysql/ doesn't exist yet on the system. In 
the post installation  script a /etc/init.d/snort restart occurs, but this 
can't possible work since no database is there yet. 

Maybe it would be a nice idea to let the installation script do the zcat itself.



-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux hawking 2.4.20 #19 Fri Jul 25 18:32:05 CEST 2003 i586
Locale: LANG=C, LC_CTYPE=C

Versions of packages snort-mysql depends on:
ii  adduser                       3.50       Add and remove users and groups
ii  debconf                       1.3.8      Debian configuration management sy
ii  libc6                         2.3.2-2    GNU C Library: Shared libraries an
ii  libmysqlclient10              3.23.56-2  LGPL-licensed client library for M
ii  libpcap0.7                    0.7.2-1    System interface for user-level pa
ii  logrotate                     3.6.5-2    Log rotation utility
ii  snort-common                  2.0.0-3.2  Flexible Network Intrusion Detecti
ii  snort-rules-default           2.0.0-3.2  Flexible Network Intrusion Detecti
ii  sysklogd [system-log-daemon]  1.4.1-11   System Logging Daemon
ii  zlib1g                        1:1.1.4-14 compression library - runtime

-- debconf information:
* snort-mysql/db_database: snort
  snort-mysql/options: 
  snort-mysql/stats_treshold: 1
* snort-mysql/interface: eth0
* snort-mysql/db_host: localhost
* snort-mysql/address_range: any
* snort-mysql/wait_for_db_config: 
  snort-mysql/reverse_order: false
  snort-mysql/please_restart_manually: 
* snort-mysql/configure_db: true
  snort-mysql/startup: boot
* snort-mysql/stats_rcpt: root
* snort-mysql/db_user: root
  snort-mysql/disable_promiscuous: false


---------------------------------------
Received: (at 291616-close) by bugs.debian.org; 25 Aug 2005 20:39:37 +0000
>From [EMAIL PROTECTED] Thu Aug 25 13:39:37 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1E8OOj-0004zR-00; Thu, 25 Aug 2005 13:32:29 -0700
From: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#291616: fixed in snort 2.3.2-6
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 25 Aug 2005 13:32:29 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 5

Source: snort
Source-Version: 2.3.2-6

We believe that the bug you reported is fixed in the latest version of
snort, which is due to be installed in the Debian FTP archive:

snort-common_2.3.2-6_all.deb
  to pool/main/s/snort/snort-common_2.3.2-6_all.deb
snort-doc_2.3.2-6_all.deb
  to pool/main/s/snort/snort-doc_2.3.2-6_all.deb
snort-mysql_2.3.2-6_i386.deb
  to pool/main/s/snort/snort-mysql_2.3.2-6_i386.deb
snort-pgsql_2.3.2-6_i386.deb
  to pool/main/s/snort/snort-pgsql_2.3.2-6_i386.deb
snort-rules-default_2.3.2-6_all.deb
  to pool/main/s/snort/snort-rules-default_2.3.2-6_all.deb
snort_2.3.2-6.diff.gz
  to pool/main/s/snort/snort_2.3.2-6.diff.gz
snort_2.3.2-6.dsc
  to pool/main/s/snort/snort_2.3.2-6.dsc
snort_2.3.2-6_i386.deb
  to pool/main/s/snort/snort_2.3.2-6_i386.deb



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.
Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated snort 
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.7
Date: Thu, 25 Aug 2005 14:59:29 +0200
Source: snort
Binary: snort-mysql snort-doc snort-rules-default snort-common snort-pgsql snort
Architecture: source i386 all
Version: 2.3.2-6
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description: 
 snort      - Flexible Network Intrusion Detection System
 snort-common - Flexible Network Intrusion Detection System [common files]
 snort-doc  - Documentation for the Snort IDS [documentation]
 snort-mysql - Flexible Network Intrusion Detection System [MySQL]
 snort-pgsql - Flexible Network Intrusion Detection System [PostgreSQL]
 snort-rules-default - Flexible Network Intrusion Detection System ruleset
Closes: 205683 219696 265735 265878 290104 291616 306269 310096 313906 318695 
321738
Changes: 
 snort (2.3.2-6) unstable; urgency=low
 .
   * Add Dependency on "debconf | debconf-2.0" as requested by Joey Hess
   * Use Debhelper compatibility version 4
   * New mechanism for database packages:
     - Introduce a mechanism to create /etc/snort/db-pending-config on
       initial installation of the database packages.
     - Have the init.d script abort the start attempt if the
       /etc/snort/db-pending-config file exists.
     - Describe how to setup the database support in README-database.Debian
       and install this document in the database packages.
       (Closes: #205683, #219696, #265735, #265878, #290104, #291616)
   * po-debconf changes:
     (still waiting a little bit before switching to dbconfig-common)
     - Sinchronise all the debconf templates of the different snort
       variants.
     - Change the wait_for_db_config message, now called 'needs_db_config'
       and provides slightly different information.
     - Fixed typos in German debconf translation courtesy of Jens Seidel
       (Closes: #313906)
     - Added Japanese translation contributed by Hideki Yamane
       (Closes: #310096)
     - Added Vietnamese translation contributed by Clytie Siddall
       (Closes: #318695)
     - Added Czech translation contributed by Jan Outrata (Closes: #321738)
     - Updated the Spanish translation.
     - Improve the debconf dialog with suggestions from Justin B Rye
       (Closes: #306269)
     - Fix the templates so that all the files use the same strings, that
       should reduce the workload of translating almost identical lines.
       (but also fuzzies more of the translations above)
Files: 
 a856fc800a40c3245b128b91b985c889 979 net optional snort_2.3.2-6.dsc
 b7bb24cfb278c1cff5040148f8fada18 254325 net optional snort_2.3.2-6.diff.gz
 3d9c9856325eabffff5b9602b23b6d21 91016 net optional 
snort-common_2.3.2-6_all.deb
 c07e11dde165eccbeeb369d173890660 1549160 doc optional snort-doc_2.3.2-6_all.deb
 2309f86029f1696603c3191db1720f95 227614 net optional 
snort-rules-default_2.3.2-6_all.deb
 854454f969f3e1e3ed3562349a778336 399378 net optional snort_2.3.2-6_i386.deb
 193a7d15ccb164339be6453a202808a2 405414 net extra snort-mysql_2.3.2-6_i386.deb
 1ffd542a77a8e6b3d76211a8060eff78 404292 net optional 
snort-pgsql_2.3.2-6_i386.deb

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

iQCVAwUBQw3wCftEPvakNq0lAQKU+QQAk8DNfhMvf+WZTDioPmz8eyU4snUuOR94
zBYrK5Omd4Y3o70M1FXDkTJi+hkwfdVCnrrfmxutcYtd4A71TGeuRYsdLefbqHzl
6IgX92to6+0jJAEFDYchGldxAtmN4nky9ADypbojmFaM2cMsQaYviNc0+Ib12ksD
Uc0C6ULMX4E=
=abab
-----END PGP SIGNATURE-----


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

Reply via email to