SpamBayes 1.1a6 not working since upgrade Debian Lenny -> Squeeze (with Python 2.6.6)
A couple of days ago I upgraded my server from Debian Lenny to Debian Squeeze. Since then I'm seeing these lines in my procmail.log: Traceback (most recent call last): File "/usr/bin/sb_filter.py", line 4, in <module> import pkg_resources File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 2671, in <module> working_set.require(__requires__) File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 654, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 552, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: spambayes==1.1a6 procmail: Program failure (1) of "/usr/bin/sb_filter.py" procmail: Rescue of unfiltered data succeeded My best guess is that the Debian upgrade included an upgrade of Python, and that this is related to the messages that I'm seeing. This is my current version of Python: $ python --version Python 2.6.6 According to the 1.0.4 release notes, the 1.1 version is built with Python 2.4. According to the 1.1a6 release notes, Python >= 2.4 is required. (your work, Skip) My questions are: * is SpamBayes 1.1a6 compatible with Python 2.6.6? * if yes: what is my next course of action to make it work again? * if no: how can I help? I have never written anything in Python but how hard can it be? -- Amedee
I don't use procmail, so my error messages were different, but I was not able to make the latest Debian 2.6.* work with 1.1a6. When I was using Squeeze, I had to run against python 2.5 to make 1.1a6 work. That trick no longer works in Wheezy, but I have had success with Skip's latest 1.1b1 found at http://pypi.python.org/pypi?:action=display&name=spambayes <http://pypi.python.org/pypi?:action=display&name=spambayes> testing against python 2.5, 2.6, and 2.7. The 1st thread is the Squeeze thread and the 2nd is the Wheezy thread. http://mail.python.org/pipermail/spambayes/2011-January/022942.html http://mail.python.org/pipermail/spambayes/2011-May/023004.html Dale On 06/15/2011 10:49 AM, Amedee Van Gasse wrote:
A couple of days ago I upgraded my server from Debian Lenny to Debian Squeeze. Since then I'm seeing these lines in my procmail.log:
Traceback (most recent call last): File "/usr/bin/sb_filter.py", line 4, in<module> import pkg_resources File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 2671, in <module> working_set.require(__requires__) File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 654, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 552, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: spambayes==1.1a6 procmail: Program failure (1) of "/usr/bin/sb_filter.py" procmail: Rescue of unfiltered data succeeded
My best guess is that the Debian upgrade included an upgrade of Python, and that this is related to the messages that I'm seeing. This is my current version of Python:
$ python --version Python 2.6.6
According to the 1.0.4 release notes, the 1.1 version is built with Python 2.4. According to the 1.1a6 release notes, Python>= 2.4 is required. (your work, Skip)
My questions are: * is SpamBayes 1.1a6 compatible with Python 2.6.6? * if yes: what is my next course of action to make it work again? * if no: how can I help? I have never written anything in Python but how hard can it be?
On Wed, June 15, 2011 20:49, Dale Schroeder wrote:
I don't use procmail, so my error messages were different, but I was not able to make the latest Debian 2.6.* work with 1.1a6. When I was using Squeeze, I had to run against python 2.5 to make 1.1a6 work.
That trick no longer works in Wheezy, but I have had success with Skip's latest 1.1b1 found at http://pypi.python.org/pypi?:action=display&name=spambayes <http://pypi.python.org/pypi?:action=display&name=spambayes> testing against python 2.5, 2.6, and 2.7.
The 1st thread is the Squeeze thread and the 2nd is the Wheezy thread.
http://mail.python.org/pipermail/spambayes/2011-January/022942.html http://mail.python.org/pipermail/spambayes/2011-May/023004.html
Dale
I *think* I fixed it. I downloaded 1.1a6 from SF, untarred it, cd'ed into the directory, and entered this command: amedee@intrepid:~/download/spambayes-1.1a6$ sudo python setup.py install Since then I'm no longer seeing errors in my procmail.log and my ham/unsure/spam folders get populated again with mails that have a X-Spambayes-Classification header. I didn't know about the 1.1b1 version, I'll have to look into that. -- Amedee
Amedee> I *think* I fixed it. Amedee> I downloaded 1.1a6 from SF, untarred it, cd'ed into the Amedee> directory, and entered this command: Amedee> amedee@intrepid:~/download/spambayes-1.1a6$ sudo python setup.py install Amedee> Since then I'm no longer seeing errors in my procmail.log and my Amedee> ham/unsure/spam folders get populated again with mails that have Amedee> a X-Spambayes-Classification header. The only problem with this approach is that you may now have files installed into the space where Debian rules things. It might get confused if you later go to install or upgrade SpamBayes packages from Debian. Skip
On 06/16/2011 6:59 AM, skip@pobox.com wrote:
Amedee> I *think* I fixed it.
Amedee> I downloaded 1.1a6 from SF, untarred it, cd'ed into the Amedee> directory, and entered this command:
Amedee> amedee@intrepid:~/download/spambayes-1.1a6$ sudo python setup.py install
Amedee> Since then I'm no longer seeing errors in my procmail.log and my Amedee> ham/unsure/spam folders get populated again with mails that have Amedee> a X-Spambayes-Classification header.
The only problem with this approach is that you may now have files installed into the space where Debian rules things. It might get confused if you later go to install or upgrade SpamBayes packages from Debian.
Skip _______________________________________________ SpamBayes@python.org http://mail.python.org/mailman/listinfo/spambayes Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
That's the primary reason I chose python-stdeb to build a new Debian package for SpamBayes.. I can install, uninstall, reinstall as needed. That's very convenient since there is no indication when Debian might upgrade the official package. Dale
On Thu, June 16, 2011 13:59, skip@pobox.com wrote:
Amedee> I *think* I fixed it.
Amedee> I downloaded 1.1a6 from SF, untarred it, cd'ed into the Amedee> directory, and entered this command:
Amedee> amedee@intrepid:~/download/spambayes-1.1a6$ sudo python setup.py install
Amedee> Since then I'm no longer seeing errors in my procmail.log and my Amedee> ham/unsure/spam folders get populated again with mails that have Amedee> a X-Spambayes-Classification header.
The only problem with this approach is that you may now have files installed into the space where Debian rules things. It might get confused if you later go to install or upgrade SpamBayes packages from Debian.
Spambayes is one of the very few packages where I won't rely on Debian's package manglement, so I don't see that as a problem. But thanks for letting me know. -- Amedee
Amedee> A couple of days ago I upgraded my server from Debian Lenny to Amedee> Debian Squeeze. Since then I'm seeing these lines in my Amedee> procmail.log: ... Amedee> raise DistributionNotFound(req) Amedee> pkg_resources.DistributionNotFound: spambayes==1.1a6 Amedee> procmail: Program failure (1) of "/usr/bin/sb_filter.py" Amedee> procmail: Rescue of unfiltered data succeeded I have no direct experience with the pkg_resources module. Amedee> My best guess is that the Debian upgrade included an upgrade of Amedee> Python, and that this is related to the messages that I'm Amedee> seeing. This is my current version of Python: 1.1b1 is out: http://pypi.python.org/pypi/spambayes/ Is there a reason not to use that? Amedee> My questions are: Amedee> * is SpamBayes 1.1a6 compatible with Python 2.6.6? I run SpamBayes from my sandbox with the bleeding edge of Python 2.7. I have no doubt it will work with Python 2.6.x. Amedee> * if yes: what is my next course of action to make it work again? Convince the Debian folks to update their SpamBayes package perhaps? (Or update your installed package to what the Debian folks are distributing.) Amedee> * if no: how can I help? I have never written anything in Python Amedee> but how hard can it be? Not hard, but this doesn't look like a coding problem to me. It looks like a packaging problem. I suspect the Debian maintainers will be much more helpful than I can be. Skip
On Wed, June 15, 2011 22:37, skip@pobox.com wrote:
1.1b1 is out:
http://pypi.python.org/pypi/spambayes/
Is there a reason not to use that?
Except the fact that until a couple of hours ago I wasn't aware that 1.1b1 existed? No, not a reason at all. :) -- Amedee
participants (3)
-
Amedee Van Gasse -
Dale Schroeder -
skip＠pobox.com