Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ 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.
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
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.