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 1555930 - glibc: The Japanese Era name will be changed on May 1, 2019 [rhel-6.10.z]
Summary: glibc: The Japanese Era name will be changed on May 1, 2019 [rhel-6.10.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: glibc
Version: 6.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Florian Weimer
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On: 1555932 1693128
Blocks: ReiwaForGlibc 1693133 1693135
TreeView+ depends on / blocked
 
Reported: 2018-03-14 21:20 UTC by Carlos O'Donell
Modified: 2022-03-13 14:46 UTC (History)
23 users (show)

Fixed In Version: glibc-2.12-1.212.el6_10.2
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.
Clone Of: 1555189
: 1693133 1693135 (view as bug list)
Environment:
Last Closed: 2019-04-09 16:36:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1555189 0 high CLOSED glibc: The Japanese Era name will be changed on May 1, 2019 [rhel-7.7.0] 2023-09-07 19:05:24 UTC
Red Hat Bugzilla 1577438 1 None None None 2023-07-18 14:30:35 UTC
Red Hat Knowledge Base (Solution) 2749651 0 None None None 2018-03-14 21:20:36 UTC
Red Hat Product Errata RHBA-2019:0726 0 None None None 2019-04-09 16:36:26 UTC
Sourceware 22964 0 P2 RESOLVED The Japanese Era name will be changed on May 1, 2019 2020-02-11 19:27:40 UTC
Sourceware 24405 0 P2 RESOLVED New era for Japan 2020-02-11 19:27:42 UTC


Comment 2 Carlos O'Donell 2018-03-14 21:21:58 UTC 
The Japanese era name will be changed on May 1, 2019. According to the Japanese government, they are considering preliminary announcement around the spring/summer of 2018.

The glibc ja_JP locale must be updated to include the new era name for strptime/strftime support.
Comment 4 Carlos O'Donell 2018-03-27 16:15:16 UTC 
The Japanese government intends to release the era name in Spring/Summer 2018. We will be waiting for this information in order to update glibc.
Comment 7 Christian Horn 2019-03-08 09:07:29 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.
Comment 21 Oneata Mircea Teodor 2019-03-27 08:44:45 UTC 
BZ cloned to:
6.5.z #1693133
6.6.z #1693135
Comment 22 Christian Horn 2019-04-01 05:26:11 UTC 
The new era got known now, 令和, U+4EE4 and U+548C.
At first, the Kanji was just shown on by the government, leaving room for interpretation
of the Kanji.  The Kanji behind above 2 unicode codepoints seem the be the chosen ones.
Comment 23 Christian Horn 2019-04-01 06:04:36 UTC 
Upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=24405
Comment 24 Florian Weimer 2019-04-01 08:49:01 UTC 
(In reply to Christian Horn from comment #22)
> The new era got known now, 令和, U+4EE4 and U+548C.
> At first, the Kanji was just shown on by the government, leaving room for
> interpretation
> of the Kanji.  The Kanji behind above 2 unicode codepoints seem the be the
> chosen ones.

<https://www.kantei.go.jp/jp/tyoukanpress/201904/1_a.html> confirms this:

新しい元号は「令和」であります。
Comment 29 errata-xmlrpc 2019-04-09 16:36:19 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:0726
Note You need to log in before you can comment on or make changes to this bug.