Bug 1705328 - Update OpenJDK to 8u222 ahead of the July 2019 security update
Summary: Update OpenJDK to 8u222 ahead of the July 2019 security update
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: java-1.8.0-openjdk
Version: 7.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Andrew John Hughes
QA Contact: OpenJDK QA
Depends On:
Blocks: 1644888
TreeView+ depends on / blocked
Reported: 2019-05-02 03:25 UTC by Andrew John Hughes
Modified: 2021-06-07 16:17 UTC (History)
3 users (show)

Fixed In Version: java-1.8.0-openjdk-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-08-06 12:33:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2006 0 None None None 2019-08-06 12:34:15 UTC

Description Andrew John Hughes 2019-05-02 03:25:37 UTC
This is similar to previous bugs like 1649852, but reflects the new release process where Red Hat are also maintaining OpenJDK 8u upstream.

We have regular security updates of the OpenJDK packages every three months. At present, updates from one upstream version to another all end up going in during a short two week period before the release, because that's when we have the full set of security patches, and hence security bugs under which to commit them.

It would be preferable to avoid this bottleneck by updating to early builds of the next OpenJDK release in y-stream, so that the actual updates required for the security release is just the actual security patches.

Building in RHEL early enables us to avoid potential issues that are limited to certain architectures we support, but that aren't commonly used by developers (e.g. ppc64, ppc64le, s390 & s390x). This is why I've chosen RHEL 7 for this bug, as it has the full complement of architectures we need to build on.

Comment 8 errata-xmlrpc 2019-08-06 12:33:48 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.


Note You need to log in before you can comment on or make changes to this bug.