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 1136407 - Port DateTime-1.12 test changes to pass with 2014g time zone database
Summary: Port DateTime-1.12 test changes to pass with 2014g time zone database
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: perl-DateTime
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: perl-maint-list
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1101251 1465904
TreeView+ depends on / blocked
 
Reported: 2014-09-02 13:49 UTC by Petr Pisar
Modified: 2019-11-21 16:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1136263
Environment:
Last Closed: 2019-11-21 16:03:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Fix ported from upstream version 1.12. (2.31 KB, patch)
2014-09-02 13:50 UTC, Petr Pisar
no flags Details | Diff

Description Petr Pisar 2014-09-02 13:49:44 UTC
+++ This bug was initially created as a clone of Bug #1136263 +++
[...]
--- Additional comment from Petr Pisar on 2014-09-02 10:45:28 GMT ---

DateTime ≥ 1.11 requires DateTime-TimeZone ≥ 1.74.

[...]
--- Additional comment from Petr Pisar on 2014-09-02 12:44:52 GMT ---

(In reply to Petr Pisar from comment #1)
> DateTime ≥ 1.11 requires DateTime-TimeZone ≥ 1.74.

Actually not. The adjusted tests are compatible with old and updated DateTime-TimeZone data.

----

The tests change needed to keep this package buildable after rebasing perl-DateTime-TimeZone to 1.74.

Comment 1 Petr Pisar 2014-09-02 13:50:42 UTC
Created attachment 933778 [details]
Fix ported from upstream version 1.12.

Comment 3 Petr Pisar 2018-03-02 15:28:10 UTC
We rebased perl-DateTime-TimeZone to 1.70 with 2017b Olson database and perl-DateTime fail to build now as predicted:

t/33seconds-offset.t ............. ok

#   Failed test 'local day should be 25 (1934-02-25 23:59:59)'
#   at t/34set-tz.t line 32.
#          got: '26'
#     expected: '25'

#   Failed test 'local hour should be 23 (1934-02-25 23:59:59)'
#   at t/34set-tz.t line 33.
#          got: '1'
#     expected: '23'

#   Failed test 'offset should be -3600 (1934-02-25 23:59:59)'
#   at t/34set-tz.t line 38.
#          got: '3600'
#     expected: '-3600'
# Looks like you failed 3 tests of 12.
t/34set-tz.t .....................
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/12 subtests

Comment 5 Petr Pisar 2019-11-21 16:03:25 UTC
Red Hat does not plan to fix this issue in Red Hat Enterprise Linux 7.
We commend you trying Red Hat Enterprise Linux 8 that delivers perl-DateTime-1.50-1.el8 that does not suffer from this issue.


Note You need to log in before you can comment on or make changes to this bug.