Your message dated Tue, 10 Jan 2006 14:19:14 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#335424: fixed in pyzor 1:0.4.0+cvs20030201-5
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; 23 Oct 2005 21:39:34 +0000
>From [EMAIL PROTECTED] Sun Oct 23 14:39:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from basalt.geos.vt.edu (basalt.geol.vt.edu) [128.173.184.181]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ETnZ0-0003uz-00; Sun, 23 Oct 2005 14:39:34 -0700
Received: from root by basalt.geol.vt.edu with local (Exim 4.54)
id 1ETnYt-0001XY-6m; Sun, 23 Oct 2005 17:39:27 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: root <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: pyzor: check failed: internal error
X-Mailer: reportbug 3.17
Date: Sun, 23 Oct 2005 17:39:27 -0400
Message-Id: <[EMAIL PROTECTED]>
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: pyzor
Version: 1:0.4.0+cvs20030201-4
Severity: important
-- System Information:
Debian Release: testing/unstable
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'),
(500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.26
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages pyzor depends on:
ii python 2.3.5-3 An interactive high-level object-o
ii python-gdbm 2.3.5-3 GNU dbm database support for Pytho
pyzor recommends no packages.
-- no debconf information
when running pyzor and spamd, I get
Oct 23 17:14:58 basalt spamd[5282]: spamd: processing message <[EMAIL
PROTECTED]> for mgi:105
Oct 23 17:14:59 basalt spamd[5282]: internal error
Oct 23 17:14:59 basalt spamd[5282]: pyzor: check failed: internal error
Oct 23 17:15:04 basalt spamd[5282]: spamd: identified spam (37.1/5.0) for
mgi:105 in 6.6 seconds, 2590 bytes.
the problem has been reported upstreams and apparently, a fix exists.
---------------------------------------
Received: (at 335424-close) by bugs.debian.org; 10 Jan 2006 22:27:09 +0000
>From [EMAIL PROTECTED] Tue Jan 10 14:27:09 2006
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EwRpi-0005Ts-MP; Tue, 10 Jan 2006 14:19:14 -0800
From: Christopher Sacca <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#335424: fixed in pyzor 1:0.4.0+cvs20030201-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 10 Jan 2006 14:19:14 -0800
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: pyzor
Source-Version: 1:0.4.0+cvs20030201-5
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-5.diff.gz
to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-5.diff.gz
pyzor_0.4.0+cvs20030201-5.dsc
to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-5.dsc
pyzor_0.4.0+cvs20030201-5_all.deb
to pool/main/p/pyzor/pyzor_0.4.0+cvs20030201-5_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.
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: Tue, 10 Jan 2006 02:33:21 -0500
Source: pyzor
Binary: pyzor
Architecture: source all
Version: 1:0.4.0+cvs20030201-5
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: 309469 324682 335096 335424
Changes:
pyzor (1:0.4.0+cvs20030201-5) unstable; urgency=low
.
* Cleaned up all the patches so that they're more condolidated
and apply cleaner
* Updated python deps to include both 2.3 and 2.4
* Tracked down the last reference to FileDigestor in client.py
that caused an error (Closes: #335096)
* Added patches from the BTS that were long overdue to be
incorperated. These patches help handle unknown encoding
types and deal with internal short comings in the mime
decryption (Closes: #309469, #324682)
According to the SpamAssassin BTS, these patches should
also solve the weird "internal error" issue
(Closes: #335424)
Files:
6dfb1a954a56e6b4073f5e36b0311a3f 691 mail optional
pyzor_0.4.0+cvs20030201-5.dsc
5369311d871224dea24f8ad1fb67c8ff 14480 mail optional
pyzor_0.4.0+cvs20030201-5.diff.gz
2c9accf4f364154fcc1553e6e46fed09 36514 mail optional
pyzor_0.4.0+cvs20030201-5_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD4DBQFDxBAseBwlBDLsbz4RAjT8AJsH3RP3ci08E2HjvkF6LmV8EnHNegCY+dP8
KnlyOmmH/UcGq9NyqZuQFg==
=aKnc
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
