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: 17832
Status: resolved
Priority: 0/
Queue: DateTime-TimeZone
People
Owner: Nobody in particular
Requestors: greg.s.skyles [...] intel.com
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Thu Feb 23 11:21:51 2006 Guest - Ticket created
Subject: Issue with Olson 2006b database?
I used the parse_olson script (from DateTime-TimeZone-0.36) against the latest Olson DB files (2006b); in lib/DateTime/TimeZone/Asia/Jerusalem.pm, the last span produced came out as: [ 64272092400, 1.#INF, 64272085200, 1.#INF, 7200, 0, 'IT' ] By comparison to the previous file, I'm guessing it should have been: [ 64272092400, DateTime::TimeZone::INFINITY, 64272085200, DateTime::TimeZone::INFINITY, 7200, 0, 'IT' ] I found DateTime-TimeZone-0.42, and it's parse_olson script did the same thing. Is this a problem with the Olson file, or does it point to something not set up correctly in my environment? perl -v This is perl, v5.8.4 built for MSWin32-x86-multi-thread (with 3 registered patches, see perl -V for more detail) Copyright 1987-2004, Larry Wall Binary build 810 provided by ActiveState Corp. http://www.ActiveState.com ActiveState is a division of Sophos. Built Jun 1 2004 11:52:21 uname -a CYGWIN_NT-5.1 gsskyles-mobl0 1.5.16(0.128/4/2) 2005-04-25 20:26 i686 unknown unknown Cygwin
  Thu Feb 23 11:24:42 2006 autarch [...] urth.org - Correspondence added
Subject: Re: [rt.cpan.org #17832] Issue with Olson 2006b database?
Date: Thu, 23 Feb 2006 10:24:30 -0600 (CST)
To: Guest via RT <bug-DateTime-TimeZone [...] rt.cpan.org>
From: Dave Rolsky <autarch [...] urth.org>
On Thu, 23 Feb 2006, Guest via RT wrote: Show quoted text
> I used the parse_olson script (from DateTime-TimeZone-0.36) against > the latest Olson DB files (2006b); in > lib/DateTime/TimeZone/Asia/Jerusalem.pm, the last span produced came > out as: > [ > 64272092400, > 1.#INF, > 64272085200, > 1.#INF, > 7200, > 0, > 'IT' > ] > > By comparison to the previous file, I'm guessing it should have been: > > [ > 64272092400, > DateTime::TimeZone::INFINITY, > 64272085200, > DateTime::TimeZone::INFINITY, > 7200, > 0, > 'IT' > ] > > I found DateTime-TimeZone-0.42, and it's parse_olson script did the > same thing. > > Is this a problem with the Olson file, or does it point to something > not set up correctly in my environment? > > perl -v > > This is perl, v5.8.4 built for MSWin32-x86-multi-thread > (with 3 registered patches, see perl -V for more detail)
Actually, it's probably a Win32 issue. On some platforms Perl's handling of infinity seems kind of broken. -dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
  Thu Feb 23 11:24:43 2006 The RT System itself - Status changed from 'new' to 'open'
  Fri Feb 24 06:37:33 2006 greg.s.skyles [...] intel.com - Correspondence added
Subject: RE: [rt.cpan.org #17832] Issue with Olson 2006b database?
Date: Fri, 24 Feb 2006 04:36:26 -0700
To: <bug-DateTime-TimeZone [...] rt.cpan.org>
From: "Skyles, Greg S" <greg.s.skyles [...] intel.com>
Dave: Thanks. A little post-processing with sed 's/-1\.#INF/DateTime::TimeZone::NEG_INFINITY/g; s/1\.#INF/DateTime::TimeZone::INFINITY/g' seems to have fixed things. -Greg "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there is less competition there." -Indira Gandhi (1917-1984) Show quoted text
-----Original Message----- From: autarch@urth.org via RT [mailto:bug-DateTime-TimeZone@rt.cpan.org] Sent: Thursday, February 23, 2006 09:25 To: Skyles, Greg S Subject: Re: [rt.cpan.org #17832] Issue with Olson 2006b database? On Thu, 23 Feb 2006, Guest via RT wrote:
> I used the parse_olson script (from DateTime-TimeZone-0.36) against > the latest Olson DB files (2006b); in > lib/DateTime/TimeZone/Asia/Jerusalem.pm, the last span produced came > out as: > [ > 64272092400, > 1.#INF, > 64272085200, > 1.#INF, > 7200, > 0, > 'IT' > ] > > By comparison to the previous file, I'm guessing it should have been: > > [ > 64272092400, > DateTime::TimeZone::INFINITY, > 64272085200, > DateTime::TimeZone::INFINITY, > 7200, > 0, > 'IT' > ] > > I found DateTime-TimeZone-0.42, and it's parse_olson script did the > same thing. > > Is this a problem with the Olson file, or does it point to something > not set up correctly in my environment? > > perl -v > > This is perl, v5.8.4 built for MSWin32-x86-multi-thread > (with 3 registered patches, see perl -V for more detail)
Actually, it's probably a Win32 issue. On some platforms Perl's handling of infinity seems kind of broken. -dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
  Sun May 18 11:55:18 2014 DROLSKY [...] cpan.org - Status changed from 'open' to 'stalled'
  Sat Aug 30 16:29:44 2014 DROLSKY [...] cpan.org - Correspondence added
On Fri Feb 24 06:37:33 2006, greg.s.skyles@intel.com wrote: Show quoted text
> Dave: > > Thanks. A little post-processing with > > sed 's/-1\.#INF/DateTime::TimeZone::NEG_INFINITY/g; > s/1\.#INF/DateTime::TimeZone::INFINITY/g' > > seems to have fixed things.
If you'd be willing to submit a patch that'd be great.
  Sat Aug 30 16:29:44 2014 The RT System itself - Status changed from 'stalled' to 'open'
  Sat Aug 30 16:30:08 2014 DROLSKY [...] cpan.org - Correspondence added
On Sat Aug 30 16:29:44 2014, DROLSKY wrote: Show quoted text
> On Fri Feb 24 06:37:33 2006, greg.s.skyles@intel.com wrote:
> > Dave: > > > > Thanks. A little post-processing with > > > > sed 's/-1\.#INF/DateTime::TimeZone::NEG_INFINITY/g; > > s/1\.#INF/DateTime::TimeZone::INFINITY/g' > > > > seems to have fixed things.
> > If you'd be willing to submit a patch that'd be great.
I should note that the patch needs to be against the code that generates the zone files, not against the generated files themselves.
  Wed Dec 03 18:18:07 2014 DROLSKY [...] cpan.org - Status changed from 'open' to 'stalled'
  Sat Nov 12 12:59:19 2016 DROLSKY [...] cpan.org - Correspondence added
Ticket migrated to GitHub as https://github.com/houseabsolute/DateTime-TimeZone/issues/15
  Sat Nov 12 12:59:19 2016 The RT System itself - Status changed from 'stalled' to 'open'
  Sat Nov 12 12:59:25 2016 DROLSKY [...] cpan.org - Status changed from 'open' to 'resolved'
  Sat Nov 12 13:04:05 2016 DROLSKY [...] cpan.org - Status changed from 'resolved' to 'new'
  Sun Nov 13 16:25:10 2016 DROLSKY [...] cpan.org - Status changed from 'new' to 'resolved'