Closed Bug 437458 Opened 17 years ago Closed 17 years ago

IST timezone not supported.

Categories

(Bugzilla :: Administration, task)

All
Linux
task
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: sloan.looney, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_3; en-us) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.1 Safari/525.20 Build Identifier: 3.0.4 The timezone parameter cannot be set to IST, the timezone in India. Bugzilla complains that "The new value for timezone is invalid: must be empty or a legal timezone name, such as PDT or JST." IST is a valid timezone identifier. I have users in a number of timezones and the server is in India, so this is a real pain. Reproducible: Always Steps to Reproduce: 1. Login as administrator 2. Click on Parameters link. 3. Set "timezone" parameter to IST. 4. Click "save" Actual Results: "The new value for timezone is invalid: must be empty or a legal timezone name, such as PDT or JST." Expected Results: Times should be displayed indicating that they are in IST. Of course, the real fix is to remove this parameter altogether and store all timestamps in UTC, converting them the appropriate timezone for display. That is mentioned in various other bugs.
IST is commented out in /usr/lib/perl5/vendor_perl/5.8.8/Time/Zone.pm, which is why it's not seen as a valid timezone: # "ist" => +5*3600+1800,# Indian Standard Bugzilla is not the one storing the list of valid timezones. It queries Time::Zone for that, which is a module external to Bugzilla. If you have access to the server, all you have to do is to edit the file above and activate the line mentioning "ist".
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
FWIW, RedHat does not appear to have modified this in their RPM, the upstream version in CPAN has it that way, too. Bug reports for the upstream version of Time::Zone can be filed at http://rt.cpan.org/Public/Bug/Report.html?Queue=TimeDate
I have reported this bug to CPAN via email. Thanks for your help!
You need to log in before you can comment on or make changes to this bug.