Summary: | mail-filter/spamassassin-3.2.x spamd dies on 'check_main' module | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Karel Hala <stripe> |
Component: | Current packages | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED WORKSFORME | ||
Severity: | critical | CC: | |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Karel Hala
2007-10-14 20:25:00 UTC
I have that, too maybe it has something to do with the emerge process, I get an error there: ... Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/share/man/man1/spamd.1 Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/share/man/man1/spamc.1 Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/share/man/man1/sa-update.1 Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/bin/sa-compile Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/bin/spamc Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/bin/sa-learn Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/bin/spamassassin Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/bin/spamd Installing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/usr/bin/sa-update Writing /var/tmp/portage/mail-filter/spamassassin-3.2.5/image//usr/lib/perl5/vendor_perl/5.8.8/i686-linux/auto/Mail/SpamAssassin/.packlist sed: can't read /var/tmp/portage/mail-filter/spamassassin-3.2.5/image//etc/mail/spamassassin/init.pre: No such file or directory cp: cannot create regular file `/var/tmp/portage/mail-filter/spamassassin-3.2.5/image//etc/mail/spamassassin/secrets.cf.example': No such file or directory chmod: cannot access `/var/tmp/portage/mail-filter/spamassassin-3.2.5/image//etc/mail/spamassassin/secrets.cf.example': No such file or directory /var/tmp/portage/mail-filter/spamassassin-3.2.5/temp/environment: line 2510: /var/tmp/portage/mail-filter/spamassassin-3.2.5/image//etc/mail/spamassassin/local.cf.example: No such file or directory /var/tmp/portage/mail-filter/spamassassin-3.2.5/temp/environment: line 2511: /var/tmp/portage/mail-filter/spamassassin-3.2.5/image//etc/mail/spamassassin/local.cf.example: No such file or directory /var/tmp/portage/mail-filter/spamassassin-3.2.5/temp/environment: line 2512: /var/tmp/portage/mail-filter/spamassassin-3.2.5/image//etc/mail/spamassassin/local.cf.example: No such file or directory /var/tmp/portage/mail-filter/spamassassin-3.2.5/temp/environment: line 2513: /var/tmp/portage/mail-filter/spamassassin-3.2.5/image//etc/mail/spamassassin/local.cf.example: No such file or directory >>> Completed installing spamassassin-3.2.5 into /var/tmp/portage/mail-filter/spamassassin-3.2.5/image/ strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment usr/bin/spamc ecompressdir: bzip2 -9 /usr/share/man >>> Installing mail-filter/spamassassin-3.2.5 * checking 110 files for package collisions --- /usr/ --- /usr/lib/ --- /usr/lib/perl5/ --- /usr/lib/perl5/vendor_perl/ --- /usr/lib/perl5/vendor_perl/5.8.8/ >>> /usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod --- /usr/lib/perl5/vendor_perl/5.8.8/Mail/ >>> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin.pm --- /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/ >>> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/AutoWhitelist.pm >>> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/BayesStore.pm ... I can also reproduce this with spamassassin-3.1.8-r1. $ perl --version This is perl, v5.8.8 built for i686-linux It seems to have something to do with the UTF8 thing in the merge message. When I call: $ echo $LANG en_US.utf8 $ LANG=en_US spamassassin -D --lint it works So, now I have it fixed and my spamassassin 3.2.1-r1 (patched ebuild) working. The problem for me was, that the ebuild didn't install the sys rules in /etc/mail/spamassassin/. With the proposed patch from: http://forums.gentoo.org/viewtopic-t-744239.html I got it working. Is this still a problem? 3.2.5-r1 seems to work fine here for me. I am going to close the bug but please reopen if needed. |