Mailinglist Archive: opensuse-security (256 mails)
| < Previous | Next > |
Re: [suse-security] latest Perl upgrade broke parts of Perl
- From: "Kai Schaetzl" <maillists@xxxxxxxxxxxxx>
- Date: Sun, 20 Feb 2005 14:31:30 +0100
- Message-id: <VA.00001bbb.0fdcfb85@xxxxxxxxxxxxxxxxxx>
I compared /usr/lib/perl5/5.8.1/i586-linux-thread-multi/auto/Storable/
with a new system where I applied the SuSE updates first and then used
CPAN to install any remaining prerequisites for sa (and was able to make
tests without problems). It turns out that the Storable.so (and other .so
files) is different. Seems that newer Perl versions install compiled API
libraries as .so files and don't use the .pm stuff anymore. That's
obviously good for performance. It seems the SuSE (or any other vendor
Perl update) just contains a lot of .so files and overwrites all those
coming with the standard distribution. Some of them are then not "in sync"
probably with some CPAN modules or whatever else.
This can either be cured by getting the respective .so file from a working
system or do a "force install" in the CPAN shell which forces a reinstall
and updates the .so file to a version that "fits". (There doesn't seem to
be a method to uninstall Perl modules?)
This means that whenever a vendor provides a Perl update the chance that
some of your installed modules get hosed is great.
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org
with a new system where I applied the SuSE updates first and then used
CPAN to install any remaining prerequisites for sa (and was able to make
tests without problems). It turns out that the Storable.so (and other .so
files) is different. Seems that newer Perl versions install compiled API
libraries as .so files and don't use the .pm stuff anymore. That's
obviously good for performance. It seems the SuSE (or any other vendor
Perl update) just contains a lot of .so files and overwrites all those
coming with the standard distribution. Some of them are then not "in sync"
probably with some CPAN modules or whatever else.
This can either be cured by getting the respective .so file from a working
system or do a "force install" in the CPAN shell which forces a reinstall
and updates the .so file to a version that "fits". (There doesn't seem to
be a method to uninstall Perl modules?)
This means that whenever a vendor provides a Perl update the chance that
some of your installed modules get hosed is great.
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org
| < Previous | Next > |