I updated all perl modules in the Debian development system (as a test) to their latest versions. I wanted to see if it is safe to update modules on live servers. It seemed to work, except that I started getting an odd error in Imager (related to API version numbers, however this is not very important right now).
I tried reinstalling Imager and any libraries associated with it, however nothing fix the problem.
Later, I discovered that the development system in question has several perl directories, including:
/usr/lib/perl (which contains 5.14.2 and subdirs)
/usr/lib/perl5 (which contains a range of perl modules)
/usr/local/lib/perl (which contains another 5.14.2 and a set of modules)
and even /root/perl5 (which contains a small list of modules including i486-linux-gnu-thread-multi-64int)
it appears (although I'm not quite sure that I am reading it correctly) that the modules in the system were installed using all possible methods, apt-get, aptitude, cpan installed from the source and cpanminus, and that different modules end in different perl directories (I assume installations), mainly / usr / local / lib / perl or / usr / lib / perl5. I do not know how there are at least two different perl installations.
I think / usr / lib / perl is the one I want to save, so I tried to rename / usr / local / lib / perl to perl.save, then the related / usr / local / lib / perl / usr / lib / perl. Then I reinstalled all the missing packages.
Most packages seem to install, however for the number I get this sinister message;
Have / usr / local / lib / perl / 5.14.2
Do you want / usr / lib / perl / 5.14
perl Config.pm, ,
, .
Perl : [5.14.2]
Config : [i486-linux-gnu-thread-multi-64int]
. , perl
.
. , .
, , , - , dev- - (), ( ).
, perl, , .
?