Your message dated Fri, 18 Mar 2005 03:32:49 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#263900: fixed in pyzor 1:0.4.0+cvs20030201-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; 6 Aug 2004 07:40:50 +0000
>From [EMAIL PROTECTED] Fri Aug 06 00:40:50 2004
Return-path: <[EMAIL PROTECTED]>
Received: from sideshowbarker.vm.bytemark.co.uk [212.13.211.65]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BszLO-0000zv-00; Fri, 06 Aug 2004 00:40:50 -0700
Received: from msmith by sideshowbarker.vm.bytemark.co.uk with local (Exim 4.34)
id 1BszLM-0000fV-I4
for [EMAIL PROTECTED]; Fri, 06 Aug 2004 16:40:48 +0900
Date: Fri, 6 Aug 2004 16:40:48 +0900
From: Michael Smith <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: pyzor: should install init script
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 2.63
User-Agent: Mutt/1.5.6i
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
X-SA-Exim-Scanned: No (on sideshowbarker.vm.bytemark.co.uk); SAEximRunCond
expanded to false
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(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_2004_03_25
X-Spam-Level:
Package: pyzor
Version: 0.4.0.0-8
Severity: wishlist
The package currently does not automatically start up pyzord on install.
Nor does it install and init script to be automatically run after
re-booting. So I need to manually start pyzord after I install the
package. And then if I reboot, I need to remember to manually re-start
pyzord. I'd rather not have to do that.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-bytemark-uml-20040706-1
Locale: LANG=C, LC_CTYPE=C
Versions of packages pyzor depends on:
ii python 2.3.4-1 An interactive high-level object-o
ii python-gdbm 2.3.4-1 GNU dbm database support for Pytho
-- no debconf information
---------------------------------------
Received: (at 263900-close) by bugs.debian.org; 18 Mar 2005 08:38:08 +0000
>From [EMAIL PROTECTED] Fri Mar 18 00:38:08 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 1DCCzf-0007NL-00; Fri, 18 Mar 2005 00:38:07 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DCCuX-00035y-00; Fri, 18 Mar 2005 03:32:49 -0500
From: Christopher Sacca <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#263900: fixed in pyzor 1:0.4.0+cvs20030201-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 18 Mar 2005 03:32:49 -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: pyzor
Source-Version: 1:0.4.0+cvs20030201-1
We believe that the bug you reported is fixed in the latest version of
pyzor, which is due to be installed in the Debian FTP archive:
pyzor_0.4.0+cvs20030201-1.diff.gz
to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-1.diff.gz
pyzor_0.4.0+cvs20030201-1.dsc
to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-1.dsc
pyzor_0.4.0+cvs20030201-1_all.deb
to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-1_all.deb
pyzor_0.4.0+cvs20030201.orig.tar.gz
to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201.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.
Christopher Sacca <[EMAIL PROTECTED]> (supplier of updated pyzor 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: Wed, 16 Mar 2005 12:54:45 -0500
Source: pyzor
Binary: pyzor
Architecture: source all
Version: 1:0.4.0+cvs20030201-1
Distribution: unstable
Urgency: low
Maintainer: Christopher Sacca <[EMAIL PROTECTED]>
Changed-By: Christopher Sacca <[EMAIL PROTECTED]>
Description:
pyzor - spam-catcher using a collaborative filtering network
Closes: 263900 295852 297922
Changes:
pyzor (1:0.4.0+cvs20030201-1) unstable; urgency=low
.
* New maintainer (Closes: #297922)
* Updated man pages to current documentation
* Documentation (pyzord.1) now clearly states that pyzord does not
daemonize itself (Closes: #263900)
* Caught IOErrors and propmts user to use correct syntax for stdin
(Closes: #295852)
Files:
a430d318aaf2c444df7796ebc60f1533 691 mail optional
pyzor_0.4.0+cvs20030201-1.dsc
21d192ae4827e1d8a218c19c1ea25b83 41827 mail optional
pyzor_0.4.0+cvs20030201.orig.tar.gz
d732587780c30746d368540569c7a667 13930 mail optional
pyzor_0.4.0+cvs20030201-1.diff.gz
fc13a8f230ba35ea32ef7b410d90fa84 35174 mail optional
pyzor_0.4.0+cvs20030201-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCOUI2eBwlBDLsbz4RAqJqAJ4nAa4D2Rc7/nMjEuYZnLG1mC9UVACdGtM8
VUhItJplZjQGIgD0efrQGuc=
=3qN7
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
