Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the DateTime-TimeZone CPAN distribution.

Report information
The Basics
Id: 5679
Status: resolved
Priority: 0/
Queue: DateTime-TimeZone

People
Owner: Nobody in particular
Requestors: slaven [...] rezic.de
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.26
Fixed in: 0.2601



Subject: Failure in t/11valid-name.t
This test fails with maintperl on a RedHat 8.0 machine: $ usr/perl5.8.4d/bin/perl -Mblib t/11valid-name.t 1..11 not ok 1 - America/Chicago is a valid timezone name # Failed test (t/11valid-name.t at line 17) ok 2 - UTC is a valid timezone name ok 3 - US/Eastern is a valid timezone name ok 4 - Europe/Paris is a valid timezone name ok 5 - Etc/Zulu is a valid timezone name ok 6 - Pacific/Midway is a valid timezone name ok 7 - America/Hell is not a valid timezone name ok 8 - FooBar is not a valid timezone name ok 9 - adhdsjghs;dgohas098huqjy4ily is not a valid timezone name ok 10 - EST is not a valid timezone name ok 11 - 1000:0001 is not a valid timezone name # Looks like you failed 1 tests of 11. Exit 1 /usr/share/zoneinfo/America/Chicago exists on this system, if this is the issue. Regards, Slaven
Date: Mon, 15 Mar 2004 18:51:52 -0600 (CST)
From: Dave Rolsky <autarch [...] urth.org>
To: Slaven_Rezic via RT <bug-DateTime-TimeZone [...] rt.cpan.org>
Subject: Re: [cpan #5679] Failure in t/11valid-name.t
RT-Send-Cc:
On Mon, 15 Mar 2004, Slaven_Rezic via RT wrote: Show quoted text
> $ usr/perl5.8.4d/bin/perl -Mblib t/11valid-name.t > 1..11 > not ok 1 - America/Chicago is a valid timezone name > # Failed test (t/11valid-name.t at line 17) > ok 2 - UTC is a valid timezone name > ok 3 - US/Eastern is a valid timezone name > ok 4 - Europe/Paris is a valid timezone name > ok 5 - Etc/Zulu is a valid timezone name > ok 6 - Pacific/Midway is a valid timezone name > ok 7 - America/Hell is not a valid timezone name > ok 8 - FooBar is not a valid timezone name > ok 9 - adhdsjghs;dgohas098huqjy4ily is not a valid timezone name > ok 10 - EST is not a valid timezone name > ok 11 - 1000:0001 is not a valid timezone name > # Looks like you failed 1 tests of 11. > Exit 1 > > /usr/share/zoneinfo/America/Chicago exists on this system, if this > is the issue.
That's not the issue. The validity of a name is determined by trying to create a new TZ object with that name. What happens when you do this: perl -Mblib -MDateTime::TimeZone -e 'DateTime::TimeZone->new( name => "America/Chicago" )' Does that error out with the latest version? -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
[autarch@urth.org - Mon Mar 15 19:52:02 2004]: Show quoted text
> On Mon, 15 Mar 2004, Slaven_Rezic via RT wrote: >
> > $ usr/perl5.8.4d/bin/perl -Mblib t/11valid-name.t > > 1..11 > > not ok 1 - America/Chicago is a valid timezone name > > # Failed test (t/11valid-name.t at line 17) > > ok 2 - UTC is a valid timezone name > > ok 3 - US/Eastern is a valid timezone name > > ok 4 - Europe/Paris is a valid timezone name > > ok 5 - Etc/Zulu is a valid timezone name > > ok 6 - Pacific/Midway is a valid timezone name > > ok 7 - America/Hell is not a valid timezone name > > ok 8 - FooBar is not a valid timezone name > > ok 9 - adhdsjghs;dgohas098huqjy4ily is not a valid timezone name > > ok 10 - EST is not a valid timezone name > > ok 11 - 1000:0001 is not a valid timezone name > > # Looks like you failed 1 tests of 11. > > Exit 1 > > > > /usr/share/zoneinfo/America/Chicago exists on this system, if this > > is the issue.
> > That's not the issue. The validity of a name is determined by trying > to > create a new TZ object with that name. > > What happens when you do this: > > perl -Mblib -MDateTime::TimeZone -e 'DateTime::TimeZone->new( name => > "America/Chicago" )' > > Does that error out with the latest version? >
Only if DateTime is not installed: /usr/perl5.8.4d/bin/perl5.8.3 -Mblib -MDateTime::TimeZone -e 'DateTime::TimeZone->new( name => "America/Chicago" )' Can't locate DateTime.pm in @INC (@INC contains: /home/slavenr/.cpan/build/DateTime-TimeZone-0.26/blib/arch /home/slavenr/.cpan/build/DateTime-TimeZone-0.26/blib/lib /usr/perl5.8.4d/lib/5.8.3/i686-linux /usr/perl5.8.4d/lib/5.8.3 /usr/perl5.8.4d/lib/site_perl/5.8.3/i686-linux /usr/perl5.8.4d/lib/site_perl/5.8.3 /usr/perl5.8.4d/lib/site_perl .) at /home/slavenr/.cpan/build/DateTime-TimeZone-0.26/blib/lib/DateTime/TimeZone/OlsonDB.pm line 485. BEGIN failed--compilation aborted at /home/slavenr/.cpan/build/DateTime-TimeZone-0.26/blib/lib/DateTime/TimeZone/OlsonDB.pm line 485. Compilation failed in require at /home/slavenr/.cpan/build/DateTime-TimeZone-0.26/blib/lib/DateTime/TimeZone/America/Chicago.pm line 15. BEGIN failed--compilation aborted at /home/slavenr/.cpan/build/DateTime-TimeZone-0.26/blib/lib/DateTime/TimeZone/America/Chicago.pm line 15. Compilation failed in require at (eval 2) line 3. Exit 2 After installing DateTime all tests pass. So another test which should be skipped if DateTime is not installed yet... Regards, Slaven