Bug 1693151

Summary: glibc: The Japanese Era name will be changed on May 1, 2019 [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: RAD team bot copy to z-stream <autobot-eus-copy>
Component: glibcAssignee: DJ Delorie <dj>
Status: CLOSED ERRATA QA Contact: Sergey Kolosov <skolosov>
Severity: medium Docs Contact:
Priority: high    
Version: 7.7CC: andrew.schofield, ashankar, bgollahe, chorn, codonell, cww, dj, eng-i18n-bugs, fweimer, kkohata, mcermak, mfabian, mmatsuya, mnewsome, nyamashi, petersen, pfrankli, skolosov, toneata, yoguma
Target Milestone: rcKeywords: i18n, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.17-196.el7_4.3 Doc Type: Enhancement
Doc Text:
The GNU C Library now provides correct Japanese era name formatting for the REIWA era starting May 1st, 2019. The time handling API data has been updated including the data used by strftime and strptime. All APIs will correctly print the REIWA era including when strftime is used along with one of the era conversion specifiers e.g. %EC, %EY, or %Ey.
Story Points: ---
Clone Of: 1555189 Environment:
Last Closed: 2019-04-09 16:36:24 UTC Type: ---
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: 1555189    
Bug Blocks: 1688569    

Description RAD team bot copy to z-stream 2019-03-27 09:04:52 UTC
This bug has been copied from bug #1555189 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 3 Sergey Kolosov 2019-04-05 21:51:29 UTC
Verified,
glibc-2.17-196.el7_4.3 has new Japanise Era support

Comment 5 errata-xmlrpc 2019-04-09 16:36:24 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.

https://access.redhat.com/errata/RHBA-2019:0727