Bjoern Voigt writes:
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.
If you use such a module, you will see errors like this (it's from my logs and an own package perl-File-Scan-ClamAV; I already downgraded, so I am unable to show an other example without much upgrade/downgrade work):
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.
It seems you are having modules that search for a 5.20.1 module path or you somehow manage to modify @INC in other ways. This has nothing to do whatsoever with the upgrade of 5.22.0 to 5.22.1.
I not sure, how Tumbleweed build system handles Perl updates. In other rolling release distributions all dependent Perl packages (and packages using Perl) have to be re-compiled after Perl version updates.
No, only major releases are binary incompatible. A minor update liek the one from 5.22.0 to 5.22.1 is binary compatible as long as the configuration is not changed. And seeing that 5.22.1 does look for modules from 3.22.0, is a good indication that these two versions are in fact binary compatible: Built under linux Compiled at Feb 17 2016 09:49:09 @INC: /usr/lib/perl5/site_perl/5.22.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.22.1 /usr/lib/perl5/vendor_perl/5.22.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.22.1 /usr/lib/perl5/5.22.1/x86_64-linux-thread-multi /usr/lib/perl5/5.22.1 /usr/lib/perl5/site_perl/5.22.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.22.0 /usr/lib/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.22.0 /usr/lib/perl5/site_perl . I'd rather put everything under 5.22 and drop the sub-release entirely, but the way things are configured is correct.
E.g. in FreeBSD you have such instructions for Perl updates:
That's for a major version upgrade.
I wonder, why nobody else seems to have Perl problems with the latest Tumbleweed snapshot 20160222?
Because they don't have old Perl modules installed that are still assuming 5.20.1? How did you end up with @INC containing 5.20.1 anyway? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org