On 3/22/2010 11:20 AM, Clayton Keller wrote:
On 3/22/2010 10:29 AM, Steve Huff wrote:
On Mar 22, 2010, at 11:26 AM, Clayton Keller wrote:
I have attempted to upgrade the SpamAssassin package this morning and
received the following error upon doing so:
spamassassin-3.3.1-1.el5.rf.i386 from rpmforge has depsolving problems
--> Missing Dependency: perl(Razor2)>= 2.61 is needed by package
spamassassin-3.3.1-1.el5.rf.i386 (rpmforge)
Error: Missing Dependency: perl(Razor2)>= 2.61 is needed by package
spamassassin-3.3.1-1.el5.rf.i386 (rpmforge)
Clayton,
Thanks for the report! This is a known issue; the fix is already in
place, and you should see a spamassassin-3.3.1-2 package in the repo
that fixes the problem no later than tomorrow.
-steve
Steve,
Thank you for the info.
I had one other thought. I believe amavisd-new 2.6.2 or later is now a
requirement for SpamAssassin 3.3.x.
Taken from the SpamAssassin release announcement
(http://svn.apache.org/repos/asf/spamassassin/branches/3.3/build/announcements/3.3.0.txt):
...
- versions of amavisd-new between 2.5.2 and 2.6.1 (inclusive) are
incompatible with SpamAssassin 3.3; please upgrade amavisd to 2.6.2 or
later, or apply a workaround
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6257
...
I'm not sure if you need to take that into consideration with this build
as well but thought I'd pass it along.
Clay
I have found another oddity with the build, the newly added requirement
for perl-Mail-SPF is now conflicting with a python-pyspf package that is
being used by pypolicyd-spf from http://www.openspf.org/Software for our
frontline SPF checking.
---
Transaction Check Error:
file /usr/bin/spfquery from install of
perl-Mail-SPF-2.006-1.el5.rf.noarch conflicts with file from package
python-pyspf-2.0.4-2.el5.noarch
---
With previous releases we added the following to our local.cf file:
do_not_use_mail_spf 1
This allows it to fallback to the Mail::SPF::Query rather than Mail::SPF
for the lookups. Which we have installed.
It was also my uderstanding that the SPF plugin in SpamAssassin would
use any exisitng SPF headers which were already present to help prevent
additonal DNS queries, which the openspf software should be creating for us.
I wanted to again pose the question regarding the requirement of the
package as I am unable to install at the present time because of the
conflict. Is this requirement for Mail::SPF really needed to be included
at this time? I am no means authority on this just providing feedback
with our current implementation.
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
