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.
.Date formatting updates for the Japanese Reiwa era
The GNU C Library now provides correct Japanese era name formatting for the Reiwa era starting on May 1st, 2019. The time handling API data has been updated, including the data used by the `strftime` and `strptime` functions. All APIs will correctly print the Reiwa era including when `strftime` is used along with one of the era conversion specifiers such as `%EC`, `%EY`, or `%Ey`.
Once we have released an errata including the new errata data, will there be anything left for customers to do?
For example, could there any relinking be required, or any recompilation of code which they use?
(In reply to Christian Horn from comment #11)
> Once we have released an errata including the new errata data, will there be
> anything left for customers to do?
No.
In fact we can write a kbentry *immediately* with steps to take to actually adjust the target system to handle the new era change.
The steps require compiling and installing a new locale.
> For example, could there any relinking be required, or any recompilation of
> code which they use?
No.
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/RHSA-2019:2118
Description of problem: We've opened this ticket for a new glibc package since 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. Checked the following thing: @yoguma src]$ ldd `which date` linux-vdso.so.1 => (0x00007ffedfffb000) libc.so.6 => /lib64/libc.so.6 (0x00007f11d5915000) /lib64/ld-linux-x86-64.so.2 (0x0000563a810a4000) @yoguma src]$ LC_TIME=ja_JP.utf8 ltrace date +'%EY' __libc_start_main(0x401ac0, 2, 0x7fffdea3ea58, 0x4096f0 <unfinished ...> strrchr("date", '/') = nil setlocale(LC_ALL, "") = "LC_CTYPE=en_US.utf8;LC_NUMERIC=e"... bindtextdomain("coreutils", "/usr/share/locale") = "/usr/share/locale" textdomain("coreutils") = "coreutils" __cxa_atexit(0x402c50, 0, 0, 0x736c6974756572) = 0 getopt_long(2, 0x7fffdea3ea58, "d:f:I::r:Rs:u", 0x60d2a0, nil) = -1 clock_gettime(0, 0x7fffdea3e890, 2, 0) = 0 localtime(0x7fffdea3e810) = 0x7f93fc125d40 strftime(" \345\271\263\346\210\22030\345\271\264", 1024, " %EY", 0x7f93fc125d40) = 12 fwrite("\345\271\263\346\210\22030\345\271\264", 11, 1, 0x7f93fc121400) = 1 __overflow(0x7f93fc121400, 10, 11, 1024平成30年 ) = 10 exit(0 <unfinished ...> __fpending(0x7f93fc121400, 0, 64, 0x7f93fc121eb0) = 0 fileno(0x7f93fc121400) = 1 __freading(0x7f93fc121400, 0, 64, 0x7f93fc121eb0) = 0 __freading(0x7f93fc121400, 0, 2052, 0x7f93fc121eb0) = 0 fflush(0x7f93fc121400) = 0 fclose(0x7f93fc121400) = 0 __fpending(0x7f93fc1211c0, 0, 0x7f93fc122a00, 0xfbad000c) = 0 fileno(0x7f93fc1211c0) = 2 __freading(0x7f93fc1211c0, 0, 0x7f93fc122a00, 0xfbad000c) = 0 __freading(0x7f93fc1211c0, 0, 4, 0xfbad000c) = 0 fflush(0x7f93fc1211c0) = 0 fclose(0x7f93fc1211c0) = 0 +++ exited (status 0) +++ @yoguma src]$ find glibc-2.17-c758a686 | grep ja glibc-2.17-c758a686/po/ja.po glibc-2.17-c758a686/localedata/locales/ja_JP Look at glibc-2.17-c758a686/localedata/locales/ja_JP: era "+:2:1990/01/01:+*:平成:%EC%Ey年";/ "+:1:1989/01/08:1989/12/31:平成:%EC元年";/ "+:2:1927/01/01:1989/01/07:昭和:%EC%Ey年";/ "+:1:1926/12/25:1926/12/31:昭和:%EC元年";/ "+:2:1913/01/01:1926/12/24:大正:%EC%Ey年";/ "+:2:1912/07/30:1912/12/31:大正:%EC元年";/ "+:6:1873/01/01:1912/07/29:明治:%EC%Ey年";/ "+:1:0001/01/01:1872/12/31:西暦:%EC%Ey年";/ "+:1:-0001/12/31:-*:紀元前:%EC%Ey年" Version-Release number of selected component (if applicable): glibc-2.17-196.el7_4.2 Additional information: https://en.wikipedia.org/wiki/Japanese_imperial_transition,_2019