What’s extra puzzling to me is that I had somehow managed to get DateTime::TimeZone installed, but:
[quote=“RytoEX, post:1, topic:62007”]I’ve just now managed to get the DateTime::TimeZone module installed, but Bugzilla’s checksetup.pl does not detect that it is installed. I’m very nearly about to just remove and reinstall Bugzilla from scratch, though I was hoping that I wouldn’t have to do this. Any thoughts?
I could think of two possibilities. One was this troubleshooting entry in Bugzilla’s documentation (I’ve excerpted the entry below):
[quote=‘The Bugzilla Guide’]A.3. I installed a Perl module, but checksetup.pl claims it’s not installed!
This could be caused by one of two things:
- You have two versions of Perl on your machine. You are installing modules into one, and Bugzilla is using the other.
- The permissions on your library directories are set incorrectly.
Though, I’m not sure how to address either of those possible problems.
The second possibility was that perhaps I needed to handle the installation of DateTime differently as suggested on the DH Wiki. Though, I don’t recall having to do that when I previously installed Bugzilla (which might have been in August 2013).
According to Bugzilla’s API documentation on install-module.pl:
[quote=‘Bugzilla API Documentation’]install-module.pl - Installs or upgrades modules from CPAN. This script does not run on Windows.
This makes install-module install modules globally for all applications, instead of just for Bugzilla.
So I would guess that it tries to install the modules locally to the Bugzilla installation instead of installing them to the user’s space or the system space for Perl modules.
If Bugzilla (and CPAN/Perl module) installations are doomed to fail on shared hosting and the recommended solution is to force CPAN to avoid default behavior (force it to not run tests during installation), then perhaps the instructions for installing Bugzilla on DreamHost need a good once over by people who have a good understanding of the process and caveats. Alternatively, maybe the procwatch daemon could be reconfigured to recognize Bugzilla’s installation scripts as installers and be more lenient with them.