Your message dated Sat, 03 Sep 2005 06:32:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#122691: fixed in logrotate 3.7.1-2
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 maintonly) by bugs.debian.org; 2 Jun 2003 11:00:36 +0000
>From [EMAIL PROTECTED] Mon Jun 02 06:00:32 2003
Return-path: <[EMAIL PROTECTED]>
Received: from pd9e1416a.dip.t-dialin.net [217.225.65.106] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 19Mn3I-00073z-00; Mon, 02 Jun 2003 06:00:32 -0500
Received: from wu by strcmp with local (masqmail 0.2.19) id
 19Mn3G-398-00; Mon, 02 Jun 2003 13:00:30 +0200
From: Ralf Neubauer <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: logrotate: please give a hint, which log-file caused an error message
X-Mailer: reportbug 1.50
Date: Mon, 02 Jun 2003 13:00:30 +0200
Message-ID: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-9.2 required=4.0
        tests=BAYES_01,HAS_PACKAGE,QUOTED_EMAIL_TEXT
        version=2.53-bugs.debian.org_2003_05_24
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_24 
(1.174.2.15-2003-03-30-exp)

Package: logrotate
Version: 3.5.9-8
Severity: wishlist

Hi,

I recently got daily mails from anacron, which i cite here:

>       Envelope-to: <[EMAIL PROTECTED]>
>       From: root (Anacron)
>       To: root
>       Subject: Anacron job 'cron.daily'
>       
>       /etc/cron.daily/logrotate:
>       error running prerotate script --
>                                       leaving old log in place
>       run-parts: /etc/cron.daily/logrotate exited with return code 1

So I knew: the is a bug _somewhere in one_ of the logrotate-scripts in
/etc/logrotate.d et al.

It would be more helpful, if logrotate would tell me the name of the
failed log file here.

-- System Information
Debian Release: 3.0-bunk-1
Architecture: i386
Kernel: Linux strcmp.libc 2.4.20.strcmp.5 #2 Tue May 6 15:54:24 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages logrotate depends on:
ii  anacron          2.3-6                   a cron-like program that doesn't g
ii  base-passwd      3.4.1                   Debian Base System Password/Group 
ii  cron             3.0pl1-72               management of regular background p
ii  libc6            2.3.1-16                GNU C Library: Shared libraries an
ii  libpopt0         1.6.4-2                 lib for parsing cmdline parameters
ii  mailx            1:8.1.2-0.20020411cvs-1 A simple mail user agent.


---------------------------------------
Received: (at 122691-close) by bugs.debian.org; 3 Sep 2005 13:39:50 +0000
>From [EMAIL PROTECTED] Sat Sep 03 06:39:50 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EBY7u-0005DY-00; Sat, 03 Sep 2005 06:32:10 -0700
From: Paul Martin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#122691: fixed in logrotate 3.7.1-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 03 Sep 2005 06:32:10 -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

Source: logrotate
Source-Version: 3.7.1-2

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

logrotate_3.7.1-2.diff.gz
  to pool/main/l/logrotate/logrotate_3.7.1-2.diff.gz
logrotate_3.7.1-2.dsc
  to pool/main/l/logrotate/logrotate_3.7.1-2.dsc
logrotate_3.7.1-2_i386.deb
  to pool/main/l/logrotate/logrotate_3.7.1-2_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.
Paul Martin <[EMAIL PROTECTED]> (supplier of updated logrotate 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: Sat,  3 Sep 2005 13:37:53 +0100
Source: logrotate
Binary: logrotate
Architecture: source i386
Version: 3.7.1-2
Distribution: unstable
Urgency: low
Maintainer: Paul Martin <[EMAIL PROTECTED]>
Changed-By: Paul Martin <[EMAIL PROTECTED]>
Description: 
 logrotate  - Log rotation utility
Closes: 122691 195790 222050 286957 306020 320331
Changes: 
 logrotate (3.7.1-2) unstable; urgency=low
 .
   * Patches:
     + 40-compressutime: Preserve mtime/atime on compression.
       (Closes: #286957)
     + 40-scripterrors: Give error messages identifying log file on
       script errors. (Closes: #122691, #195790, #222050, #306020)
 .
   * Patch debian/control to fix FTBFS on kfreebsd-i386. (Closes:
     #320331).
Files: 
 d0946125e17dc545130ceaec4d93550d 625 admin important logrotate_3.7.1-2.dsc
 5820ec74ff1d2c4ff634222d9d7dcad6 21120 admin important 
logrotate_3.7.1-2.diff.gz
 0c2e5a4376d7de7a710064d2c816dd9a 34328 admin important 
logrotate_3.7.1-2_i386.deb

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

iD8DBQFDGaDa+gi+rt7UWRIRAswvAJ94T4q7/AxdUohZ/nvn0I4C5t9ZrgCfaQDa
rD63zcfEKvjnV3tZ42W6f14=
=eBVM
-----END PGP SIGNATURE-----


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

Reply via email to