Your message dated Thu, 17 Mar 2005 03:47:02 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#299896: fixed in checksecurity 2.0.7-4
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; 17 Mar 2005 07:55:22 +0000
>From [EMAIL PROTECTED] Wed Mar 16 23:55:22 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dixsept.loria.fr [152.81.9.195] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DBpqj-0000XL-00; Wed, 16 Mar 2005 23:55:21 -0800
Received: from vlefevre by dixsept.loria.fr with local (Exim 4.50)
        id 1DBpqE-0004xs-1j; Thu, 17 Mar 2005 08:54:50 +0100
Date: Thu, 17 Mar 2005 08:54:50 +0100
From: Vincent Lefevre <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: checksecurity:6 unknown user 'snort' (logrotate)
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.8
X-Mailer-Info: http://www.vinc17.org/mutt/
User-Agent: Mutt/1.5.8-vl-20050311i
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: checksecurity
Version: 2.0.7-2
Severity: normal

I got the following error last night:

/etc/cron.daily/logrotate:
error: checksecurity:6 unknown user 'snort'
run-parts: /etc/cron.daily/logrotate exited with return code 1

/etc/logrotate.d/checksecurity contains:

/var/log/checksecurity.log /var/log/diskfree.log /var/log/setuid/setuid.changes
{
    weekly
    rotate 10
    compress
    missingok
    create 0640 snort adm
}

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages checksecurity depends on:
ii  cron                          3.0pl1-87  management of regular background p
ii  debconf                       1.4.46     Debian configuration management sy
ii  perl                          5.8.4-8    Larry Wall's Practical Extraction 

-- debconf information:
  checksecurity/oldconf:

---------------------------------------
Received: (at 299896-close) by bugs.debian.org; 17 Mar 2005 08:53:07 +0000
>From [EMAIL PROTECTED] Thu Mar 17 00:53:07 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DBqkc-0000uR-00; Thu, 17 Mar 2005 00:53:06 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DBqek-0000Dy-00; Thu, 17 Mar 2005 03:47:02 -0500
From: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#299896: fixed in checksecurity 2.0.7-4
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 17 Mar 2005 03:47:02 -0500
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-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-Spam-Level: 

Source: checksecurity
Source-Version: 2.0.7-4

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

checksecurity_2.0.7-4.diff.gz
  to pool/main/c/checksecurity/checksecurity_2.0.7-4.diff.gz
checksecurity_2.0.7-4.dsc
  to pool/main/c/checksecurity/checksecurity_2.0.7-4.dsc
checksecurity_2.0.7-4_all.deb
  to pool/main/c/checksecurity/checksecurity_2.0.7-4_all.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 
checksecurity 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, 17 Mar 2005 09:24:44 +0100
Source: checksecurity
Binary: checksecurity
Architecture: source all
Version: 2.0.7-4
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description: 
 checksecurity - basic system security checks
Closes: 299896
Changes: 
 checksecurity (2.0.7-4) unstable; urgency=low
 .
   * Use proper user for the logrotation facility (Closes: #299896)
Files: 
 9aecf6b74e124603e87a066e121e5d80 726 admin optional checksecurity_2.0.7-4.dsc
 30e70039d577ccc44386757b4fd54cf6 8786 admin optional 
checksecurity_2.0.7-4.diff.gz
 53bf98937bdb13ed311d2465d768dd98 20072 admin optional 
checksecurity_2.0.7-4_all.deb

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

iQCVAwUBQjk+5vtEPvakNq0lAQKptQP5AfaGsxS6rQ4egc622XZM/HlKUJ1MCCUI
ixxHDgIZRkn/X105akq1iRbIMb4HytVoL8+Ox9ZCdzBtMeNYiL6dm3XPOYDONJDo
cukS1JsWZ2ZuZ1Fh+C1hB0LkOxII1yJRHuAgAq/U2jOeEsMtwruD74BUMoWbH7WX
BIjPPzgiiN0=
=kwdx
-----END PGP SIGNATURE-----


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

Reply via email to