http://bugzilla.spamassassin.org/show_bug.cgi?id=3412
Summary: pyzor fails 2.63 -> 20040518 svn
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
Component: spamassassin
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
http://download3.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/
spamassassin-3.0-0.0.svn20040518.src.rpm
Fedora Core 2 plus this spamassassin package from rawhide. rawhide will be
tracking svn snapshots during the FC3 development cycle leading up to
spamassassin's 3.0 release. One of the two regressions in behavior I have
noticed since upgrading from spamassassin-2.63 that shipped in FC2 is pyzor
fails with a traceback when it is run during spam checking, or called during
reporting. I am unsure of how to get the full python tracebacks from this.
spamassassin -D output
======================
debug: Current PATH is: /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin
debug: executable for pyzor was found at /usr/bin/pyzor
debug: Pyzor is available: /usr/bin/pyzor
debug: entering helper-app run mode
debug: Pyzor: got response: Traceback (most recent call last):
debug: leaving helper-app run mode
debug: Pyzor: couldn't grok response "Traceback (most recent call last):"
spamassassin -r output
======================
debug: executable for pyzor was found at /usr/bin/pyzor
debug: Pyzor is available: /usr/bin/pyzor
debug: entering helper-app run mode
debug: raw exit code: 256
debug: leaving helper-app run mode
Pyzor -> report failed: Exited with non-zero exit code 1
debug: SpamAssassin: could not report spam to Pyzor.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
