Your @INC looks a little unusual to me. Is this a custom built Perl or the system Perl? Are you setting PERL5LIB or similar?
Assuming this is the system Perl, my approach would be to pick apart which files in the @INC paths belong to packages managed by the system and delete the rest. "debsums" may be helpful here, along with forced reinstalls of the packages.
Then, once you've cleaned up the system Perl, only use the package manager to add or remove modules there. For custom built modules I would suggest building those in a local build of Perl (perlbrew), this eliminates the risk of messing up the system Perl.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.