First time around, the reason was that the provider decided to fix the recent BSD security hole. By upgrading the OS, so I had to recompile four modules (DBI,DBD,SQL::Statement,Text::CSV). I had these modules in my own directory (included with -I on the bang line) since they weren't supplied. Also it was upgraded to Perl 5.6. They said "it was supposed to be compatible" but whatever.
Second time around (today), I found the provider had installed a later version of DBI than my own (1.13 to 1.18), which superseeded mine, so I got a DBI object version error. Fixed by using their modules, though I'm wondering if it will break again if they install SQL and Text later.
Is it possible that you have your own installation of Image Magick or truetype and it has been superseded by an installation recently made by the provider? I was thinking about how to guard against this in the future, and the only thing I came up with was having my own local Perl install. This is a pain and I'm starting to think that you just can't trust a provider not to break a system you're depending on.. hope this helps.
In reply to Re: A path with heart
by mattr
in thread A path with heart
by jeffpflueger
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |