Your message dated Mon, 14 Mar 2005 17:57:34 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Bug#240024: fixed in fcron 2.9.6-1
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; 25 Mar 2004 12:22:51 +0000
>From [EMAIL PROTECTED] Thu Mar 25 04:22:51 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mars.mj.nl [81.91.1.49] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1B6Tsp-0002sn-00; Thu, 25 Mar 2004 04:22:51 -0800
Received: (qmail 29635 invoked from network); 25 Mar 2004 12:22:20 -0000
Received: from 81-91-5-95-customer.mjdsl.nl (HELO thanatos) (81.91.5.95)
  by www.mj.nl with SMTP; 25 Mar 2004 12:22:20 -0000
Received: by thanatos (Postfix, from userid 1001)
        id 6654910D6AC; Thu, 25 Mar 2004 13:22:14 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Thomas Hood <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Init script message is nonstandard
X-Mailer: reportbug 2.48
Date: Thu, 25 Mar 2004 13:22:14 +0100
Message-Id: <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level: 

Package: fcron
Version: 2.9.4-3
Severity: minor

The initscripts startup message should have the form:

    Starting <description>: <binaryname>.

E.g.,

    Starting periodic command scheduler: cron.

Currently fcron's message is this:
    Starting fcron: fcron.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.24
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Versions of packages fcron depends on:
ii  adduser                     3.51         Add and remove users and groups
ii  debconf                     1.4.16       Debian configuration management sy
ii  dpkg                        1.10.20      Package maintenance system for Deb
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libpam0g                    0.76-15      Pluggable Authentication Modules l
ii  libselinux1                 1.6-1        SELinux shared libraries
ii  postfix [mail-transport-age 2.0.18-1     A high-performance mail transport 
ii  sysklogd [system-log-daemon 1.4.1-13     System Logging Daemon

-- debconf information:
* fcron/anacronwarn: 


---------------------------------------
Received: (at 240024-done) by bugs.debian.org; 14 Mar 2005 20:57:44 +0000
>From [EMAIL PROTECTED] Mon Mar 14 12:57:44 2005
Return-path: <[EMAIL PROTECTED]>
Received: from master.debian.org [146.82.138.7] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DAwdD-0001YY-00; Mon, 14 Mar 2005 12:57:44 -0800
Received: from rcm-200-220-132-60.nipnet.net.br (khazad-dum.debian.net) 
[200.220.132.60] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DAwdC-0005Es-00; Mon, 14 Mar 2005 14:57:43 -0600
Received: from localhost (localhost [127.0.0.1])
        by localhost.khazad-dum.debian.net (Postfix) with ESMTP id 1DB5C20025B
        for <[EMAIL PROTECTED]>; Mon, 14 Mar 2005 17:57:36 -0300 (BRT)
Received: from khazad-dum.debian.net ([127.0.0.1])
        by localhost (khazad-dum [127.0.0.1]) (amavisd-new, port 10024)
        with LMTP id 27260-02 for <[EMAIL PROTECTED]>;
        Mon, 14 Mar 2005 17:57:34 -0300 (BRT)
Received: by khazad-dum.debian.net (Postfix, from userid 1000)
        id 5D58D200409; Mon, 14 Mar 2005 17:57:34 -0300 (BRT)
Date: Mon, 14 Mar 2005 17:57:34 -0300
From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Bug#240024: fixed in fcron 2.9.6-1
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-GPG-Fingerprint: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04  3738 EE25 DE3F 1CDB 
0FE3
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at khazad-dum.debian.net
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: fcron
Source-Version: 2.9.6-1

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

fcron_2.9.6-1.diff.gz
  to pool/main/f/fcron/fcron_2.9.6-1.diff.gz
fcron_2.9.6-1.dsc
  to pool/main/f/fcron/fcron_2.9.6-1.dsc
fcron_2.9.6-1_i386.deb
  to pool/main/f/fcron/fcron_2.9.6-1_i386.deb
fcron_2.9.6.orig.tar.gz
  to pool/main/f/fcron/fcron_2.9.6.orig.tar.gz



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.
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> (supplier of updated fcron
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])

Format: 1.7
Date: Sun, 13 Mar 2005 18:33:44 -0300
Source: fcron
Binary: fcron
Architecture: source i386
Version: 2.9.6-1
Distribution: unstable
Urgency: low
Maintainer: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
Changed-By: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
Description: 
 fcron      - cron-like scheduler with extended capabilities
Closes: 193628 200114 248707 284036 292976
Changes: 
 fcron (2.9.6-1) unstable; urgency=low
 .
   * The long winter cleanup release
   * Adopt package (I STILL WANT TO HAND THIS TO SOMEONE ELSE), so that
     it makes my life easier with the BTS and other non-uploaders-aware
     scripts
   * New upstream source
   * Add watch file
   * Use make clean instead of inexistant distclean
   * Switch to po-debconf, thanks to Christian Perrier (closes: #200114)
   * Remove legacy suidregister/suidunregister crap (closes: #292976)
   * Fix regexp to move legacy root fcrontab entries on prerm (closes:
#248707)
   * Add a proper ego-inflated daemon description to fcron initscript
     messages (close: #240024)
   * Move fcronsighup to /usr/sbin (closes: #284036)
   * Switch to debhelper mode v4, and cleanup debian/rules accordingly
   * With this upload everything of use in the diff provided by the
     bug reporter has been addressed (closes: #193628)
   * Update debian/copyright
   * Update lintian overrides
   * Remove fcron 0.9.x cruft from maintainer scripts, we do not care about
     ancient sid -> current sarge/sid updates
Files: 
 bd7e30252739b260170f4c9c1dde33cc 950 admin extra fcron_2.9.6-1.dsc
 f3defb7a9ba178e013ebe5b31c692ae8 406243 admin extra fcron_2.9.6.orig.tar.gz
 2afa8830d81db044eeb6a12f3c8d1878 17110 admin extra fcron_2.9.6-1.diff.gz
 1b89604e29a79dbc53928edbe86dfa31 154130 admin extra fcron_2.9.6-1_i386.deb

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


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

Reply via email to