Installing Catalyst on production server yesterday…
I’ve installed Catalyst via CPAN a few times before and never had a problem. However yesterday did take me a while on a clients hosted server ;-(
Problem was with other CPAN modules. The two culprits were Module::Build & Test::WWW::Mechanize::Catalyst.
Module::Build failed one test in compat.t….
# Failed test 'Should be non-verbose'
# at t/compat.t line 146.
# '# make test TEST_VERBOSE=0
# # make: Entering directory `/home/jkellehe/.cpan/build/Module-Build-0.2808-gC4gPU/t/_tmp/Simple'
# # /clear/local/bin/perl Build --makefile_env_macros 1 test
# # t/basic.t....ok
# # All tests successful.
# # Files=1, Tests=1, 0 wallclock secs ( 0.01 usr 0.00 sys + 0.02 cusr 0.01 csys = 0.04 CPU)
# # Result: PASS
# # make: Leaving directory `/home/jkellehe/.cpan/build/Module-Build-0.2808-gC4gPU/t/_tmp/Simple'
# doesn't match '(?-xism:(?:# .+basic\.+ok\s+(?:[\d.]+\s*m?s\s*)?)# All tests)'
This looked like it was something wrong with test... so I decided to force the install (oh heavens forbid!).
I found the problem on web (think RT) about what was wrong with Test::WWW::Mechanize::Catalyst. I just need to downgrade LWP to 5.808 & Test::WWW::Mechanize::Catalyst to 0.40 and all tests passed.
NB. On a non Catalyst sidenote.... I also had problem installing DateTime from CPAN. Needed DateTime::Locale & DateTime::TimeZone installing first.
Update: I think DateTime problem was probably associated with locale settings. Setting "export LANG=C" first think gets around above problem.