Bug 838480
Summary: | perl-DateTime is too old | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Petr Pisar <ppisar> |
Component: | perl-DateTime | Assignee: | perl-maint-list |
Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.3 | CC: | ovasik, ppisar, psabata |
Target Milestone: | rc | Keywords: | Rebase |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://search.cpan.org/~drolsky/DateTime/ | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
Doc Text: | Story Points: | --- | |
Clone Of: | 838476 | Environment: | |
Last Closed: | 2013-06-27 08:56:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 947784 |
Description
Petr Pisar
2012-07-09 08:40:07 UTC
New versions are available. There is no big change except a little bit different rounding algorithm introduced in version 0.78: 1.03 2013-04-17 - The set_time_zone() method was not returning the object when caalled with a name that matched the current zone. Reported by Noel Maddy. RT #84699. 1.02 2013-04-15 - When a constructor method like new() or today() was called on an object, you'd get an error message like 'Can't locate object method "_normalize_nanoseconds" via package "2013-04-15T00:00:00"'. This has been fixed to provide a sane error message. Patch by Doug Bell. - When set_time_zone() is called with a name that matches the current time zone, DateTime now short circuits and avoids a lot of work. Patch by Mark Stosberg. 1.01 2013-04-01 - Fixed test failures on older Perls. 1.00 2013-03-31 - Bumped the version to 1.00. This is mostly because my prior use of both X.YY and X.YYYY versions causes trouble for some packaging systems. Plus after 10 years it's probably ready to be called 1.00. Requested by Adam. RT #82800. - The %j specifier for strftime was not zero-padding 1 and 2 digit numbers. Fixed by Christian Hansen. RT #84310. - The truncate method was sloppy about validating its "to" parameter, so you could pass things like "years" or "month whatever anything goes". The method would accept the parameter but then not actually truncate the object. RT #84229. - Previously, if a call to $dt->set_time_zone() failed it would still change the time zone of the object, leaving it in a broken state. Reported by Bill Moseley. RT #83940. - DateTime::Infinite objects should no longer die when methods that require a locale are called. Instead, these methods return undef for names and Inf/-Inf for numbers. This affects methods such as day_name() as well as CLDR and strftime formats. When a locale-specific format is used (like the "full" datetime format) it uses the en_US format. Reported by Paul Boldra. RT #67550. 0.78 2012-11-16 - Reverted the change to round nanoseconds up or down in various situtations. Now we always round down. This avoids the case where rounding up would require us to then increment the second value (which could then require us to increment the minute, which could then require us to increment the hour, which could then ...). In other words, we don't want to round 2011-12-31T23:59:59.999999 up to 2012-01-01T00:00:00, because that would be insane. This applies to the return values for ->microsecond, ->millisecond, and the %N specifier for strftime. Patch by Martin Hasch. RT #79845. 0.77 2012-09-25 - POD changes that should make the documentation look better, especially on the web. Versions after 1.00 requires Try::Tiny that is not packaged in RHEL-6.5 yet. If it's not possible to add it, DateTime can be easily patched (reverting upstream commit 1489430f). Version after 0.70 requires Test::Fatal for running tests. Test::Fatal is not yet in RHEL-6.5. Test::Fatal requires Try::Tiny. It would be possible to refactor the tests not to use Test::Fatal, but easier would be to add Test::Fatal. However as I can see, RHEL-6.5-current DateTime 0.53 bundles DateTime-0.53, DateTime-Locale-0.44, and DateTime-TimeZone-1.08. In this light, we had to package them too. Thus rebase is not good idea here. Patching leap second database is more feasible: diff --git a/leaptab.txt b/leaptab.txt index ef2ec12..f1c7f2e 100644 --- a/leaptab.txt +++ b/leaptab.txt @@ -22,3 +22,4 @@ 1999 Jan. 1 +1 2006 Jan. 1 +1 2009 Jan. 1 +1 +2012 Jul. 1 +1 Well, it's not literally bundled, but still it would require the Test::Fatal and Try::Tiny. Based on the latest Petr's findings about the dependencies, I'm going to NAK this request from development point of view. The primary issue with leap second will be addressed by #978360. Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |