Description of problem:
The Japanese Era name will be changed on 2019-05-01 / component icu / rhel5
openjdk code is referring to the japanese era name.
All openjdk versions are affected.
The upcoming era name should properly be dealed with.
- the new era name has not yet been announced.
- We also have to modify glibc (for example bz1555189) and icu.
- openjdk upstream seems to have implemented the new era now, with name NEWERA, which they
intend to replace then later. I guess they wanted to be sure to have time to debug
issues they might have with the change itself now that there is time, and later just
want to replace the era.
We are not necessarily requesting this in-between-step, the request of our customers is to have openjdk eventually deal with the new era name.
We seem to be missing one of these bugs for the java-1.7.0-openjdk & RHEL 7 combination.
(In reply to Andrew John Hughes from comment #1)
> We seem to be missing one of these bugs for the java-1.7.0-openjdk & RHEL 7
Sorry, I do not understand this, can you be more verbose?
Are there additional issues to be solved to solve this one here? If so, are these reported as bz's already or not?
partially covered by tck
bz1687324 - The Japanese Era name will be changed on 2019-05-01 / component java-1.7.0-openjdk / rhel7
Yes, that's what I meant, sorry for the confusion and thanks Christian for creating the missing bug.
Resolved in https://access.redhat.com/errata/RHSA-2019:0775 . Should we close this bz CURRENTRELEASE?
Can we get the release notes updated for this ERRATA if the patch for this was included? The release notes do not include anything regarding updates for the Era change.
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.