Bug 1555932
| Summary: | glibc: The Japanese Era name will be changed on May 1, 2019 [rhel-5-els] | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Carlos O'Donell <codonell> | |
| Component: | glibc | Assignee: | Florian Weimer <fweimer> | |
| Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 5.11 | CC: | ahogbin, ashankar, bgollahe, chorn, codonell, dj, eng-i18n-bugs, fweimer, glibc-bugzilla, kkohata, mcermak, mfabian, mnewsome, nyamashi, petersen, pfrankli, qe-baseos-tools-bugs, skolosov, toneata, yogsawan, yoguma | |
| Target Milestone: | rc | Keywords: | i18n | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glibc-2.5-123.el5_11.5 | 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 | |||
| : | 1693128 (view as bug list) | Environment: | ||
| Last Closed: | 2019-04-09 16:36:03 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: | 1555930, 1688569, 1693128, 1693133, 1693135 | |||
|
Comment 1
Carlos O'Donell
2018-03-14 21:25:13 UTC
Is there anything preventing dev_ack here? It is clear that the information - which kanji - and which name will become the new era name have to be known. dev_ack has been set for the rhel7 and rhel8 glibc bz, and would express that we think we can fix this bz. Our partners are also asking for z-stream errata. With the dev_ack, we can approach PM and ask for chances for the z-stream fixes. 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:0724 |