There have been a lot of changes to Mail::IMAPClient between 3.08 and 2.2.9. At least, search.cpan.org does not want to display the changes, but at least you can download them. My suggestion is that you read the documentation for both module versions and the Changes file and see if there are any hints on an API change or new requisites. You can of course also inspect /usr/share/perl5/Mail/IMAPClient.pm line 2168 on the production machine to see a propable cause for the error. That's why Perl tells you the information.
Normally, you can't expect that a new major version will be piece-by-piece identical to an older version, so developing for a newer version than you have in production is not a viable strategy.
If all else fails, Yes, even you can use CPAN and stray away from the walled garden that is Debian. Of course I as technical administrator would hit you over the head for not using a Debian package when everything else is available as a Debian package and the company rules are to use Debian packages.
In reply to Re: Mail::IMAPClient + Folder
by Corion
in thread Mail::IMAPClient + Folder
by Dawit
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |