On Thu, 2016-02-25 at 10:10 +0100, Bjoern Voigt wrote:
Andreas Schwab wrote:
Bjoern Voigt
writes: Perl itself is version 5.22.1 (perl-5.22.1-1.1.x86_64). But the packages are still 5.22.0.
I which way is that a problem? Perl should still be able to use the modules.
Perl 5.22.0 does not find the modules compiled for 5.22.1, because Perl 5.22.0 does not search the 5.22.1 paths.
But you were going the other way: perl 5.22.1 should find the 5.22.0 moduldes (it's backwards compatible. not forward compatible)
2014-12-23T10:18:05.644476+01:00 mybox spamd[1900]: Can't locate File/Scan/ClamAV.pm in @INC (you may need to install the File::Scan::ClamAV module) (@INC contains: /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.20.1 /usr/lib/perl5/site_perl/5.20.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.20.1 /usr/lib/perl5/5.20.1/x86_64-linux- thread-multi /usr/lib/perl5/5.20.1 /usr/lib/perl5/site_perl) at /etc/mail/spamassassin/clamav.pm line 17.
Where are perl 5.20 paths coming from there! We were discussing 5.22.0 to 5.22.1 upgrade issues... But yes, in December 2014 we might have switched from 5.20 a notch up :) (check the date/timestamp of that log extract) Probably there was no problem to start with? Other than you seeing directories you expected to disappear? Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org