RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 978360 - perl-DateTime 0.5300 has out-dated leap second database
Summary: perl-DateTime 0.5300 has out-dated leap second database
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: perl-DateTime
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Pisar
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-26 12:56 UTC by Petr Pisar
Modified: 2013-11-21 07:27 UTC (History)
4 users (show)

Fixed In Version: perl-DateTime-0.5300-2.el6
Doc Type: Bug Fix
Doc Text:
Cause: Computing time duration through 2012-06-30T23:59:60 second. Consequence: The duration won't be accurate. Fix: A leap second appended in the end of 2012-06-30 has been added to perl-DateTime leap second database. Result: Time arithmetic using Perl modules DateTime and DateTime::Duration recognize 2012-06-30 leap second correctly.
Clone Of:
Environment:
Last Closed: 2013-11-21 07:27:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Reproducer (518 bytes, text/plain)
2013-06-26 13:08 UTC, Petr Pisar 		no flags Details
Fix (1.58 KB, patch)
2013-06-26 13:37 UTC, Petr Pisar 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 838480 0 high CLOSED perl-DateTime is too old 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2013:1566 0 normal SHIPPED_LIVE perl-DateTime bug fix update 2013-11-20 21:40:07 UTC

Internal Links: 838480

Description Petr Pisar 2013-06-26 12:56:22 UTC 
perl-DateTime-0.5300 does not recognize leap second on 2012-07-01 because the leap second database compiled into DateTime is too old.

I propose updating the database and rebuild perl-DateTime

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
Comment 1 Petr Pisar 2013-06-26 13:08:01 UTC 
Created attachment 765575 [details]
Reproducer
Comment 2 Petr Pisar 2013-06-26 13:37:40 UTC 
Created attachment 765591 [details]
Fix
Comment 11 errata-xmlrpc 2013-11-21 07:27:12 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1566.html
Note You need to log in before you can comment on or make changes to this bug.