Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 343321

Summary: Error starting MailScanner after perl update
Product: Gentoo Linux Reporter: George Papadopoulos <divined2004>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description George Papadopoulos 2010-10-30 07:01:07 UTC
After updating perl and running perl-cleaner --all, I get this error when trying to start MailScanner :

 /etc/init.d/MailScanner start
 * Starting MailScanner ...
Can't load '/usr/lib/perl5/5.12.2/i686-linux/auto/Compress/Raw/Zlib/Zlib.so' for module Compress::Raw::Zlib: /usr/lib/perl5/5.12.2/i686-linux/auto/Compress/Raw/Zlib/Zlib.so: undefined symbol: deflateTune at /usr/lib/perl5/5.12.2/i686-linux/DynaLoader.pm line 200.
 at /usr/lib/perl5/vendor_perl/5.12.2/Archive/Zip.pm line 12
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.12.2/Archive/Zip.pm line 12.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.12.2/Archive/Zip.pm line 12.
Compilation failed in require at /usr/lib/MailScanner/MailScanner/Message.pm line 48.
BEGIN failed--compilation aborted at /usr/lib/MailScanner/MailScanner/Message.pm line 48.
Compilation failed in require at /usr/sbin/MailScanner line 108.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 108.      [ !! ]

My gentoo kernel version is :

Linux t-rex 2.6.35-gentoo-r4 #4 PREEMPT Sun Aug 29 19:36:27 EEST 2010 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux





Reproducible: Always

Steps to Reproduce:
1.Install MailScanner 4.81.4.1
2.Update to perl 5.12.2-r1
3./etc/init.d/MailScanner restart or reboot




Same thing happened with older version of MailScanner whick worked just before updating to the new perl version.
Comment 1 Samuli Suominen (RETIRED) gentoo-dev 2010-10-30 07:39:10 UTC

*** This bug has been marked as a duplicate of bug 343319 ***