Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 8854 - SpamAssassin won't run
Summary: SpamAssassin won't run
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-07 11:06 UTC by Berant Lemmenes
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Berant Lemmenes 2002-10-07 11:06:52 UTC
I've emerged Mail-SpamAssassin and I'm unable to run it.   
 
Here's what I get when I try to run /usr/bin/spamassassin: 
 
splat root # /usr/bin/spamassassin 
Can't locate Mail/SpamAssassin/NoMailAudit.pm in @INC (@INC contains: ../lib  
lib /usr/lib/perl5/5.6.1/i686-linux /usr/lib/perl5/5.6.1  
/usr/lib/perl5/site_perl/5.6.1/i686-linux /usr/lib/perl5/site_perl/5.6.1  
/usr/lib/perl5/site_perl . /usr/bin/lib /usr/bin/site_perl  
/usr/bin/../share/spamassassin/lib /usr/bin/../share/spamassassin/site_perl)  
at /usr/bin/spamassassin line 127. 
BEGIN failed--compilation aborted at /usr/bin/spamassassin line 127. 
 
NoMailAudit.pm is in /usr/lib/site_perl/5.6.1/Mail/SpamAssassin/ 
 
When I try to run spamd I get this: 
 
splat root # /etc/init.d/spamd start 
 * Starting spamd... 
Can't locate Mail/SpamAssassin.pm in @INC (@INC contains: ../lib  
/usr/lib/perl5/5.6.1/i686-linux /usr/lib/perl5/5.6.1  
/usr/lib/perl5/site_perl/5.6.1/i686-linux /usr/lib/perl5/site_perl/5.6.1  
/usr/lib/perl5/site_perl .) at /usr/bin/spamd line 16. 
BEGIN failed--compilation aborted at /usr/bin/spamd line 16. 
 
Which is in the same spot as the previous .pm. 
 
I'm using SpamAssassin 2.31-r3 and Perl 5.6.1-r7
Comment 1 Berant Lemmenes 2002-10-08 09:39:26 UTC
After looking at bug 8437 I re-emerged ExtUtils-MakeMaker and then unmerged 
spamassassin.  I then emerged Mail-SpamAssassin and that resolved the issue.