Bug 1155783
| Summary: | Remove java-devel provides from java-1.8.0-openjdk [RHEL-6.7] | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Deepak Bhole <dbhole> | ||||||
| Component: | java-1.8.0-openjdk | Assignee: | jiri vanek <jvanek> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 6.6 | CC: | dgoodwin, iboverma, jherrman, jvanek, lzachar, salmy, sbaiduzh | ||||||
| Target Milestone: | rc | Keywords: | ZStream | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Prior to this update, the java-1.8.0-openjdk packages incorrectly provided "java-devel", which could lead to their inclusion in inappropriate builds. As a consequence, the "yum install java-devel" command in some cases installed java-1.8.0-openjdk-devel instead of the intended Java package. This update removes the providing configuration, and java-1.8.0-openjdk-devel can now be installed only by using the "yum install java-1.8.0-openjdk-devel" command.
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 1155786 1156375 (view as bug list) | Environment: | |||||||
| Last Closed: | 2015-07-22 07:44:34 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: | 1155786, 1156375 | ||||||||
| Attachments: |
|
||||||||
|
Description
Deepak Bhole
2014-10-22 19:43:50 UTC
On second thought, rather than replacing with java8*, we should just remove them altogether to prevent customers from depending on the provides that may end up getting removed in the future. Thanks to Omair for pointing this out. Hi! The packages are not providing java8 but have epoch set to 0. Actually the change from provides javaX to whatever was requested, so we (me, Omair and Lukas) have come out with epoch 0. This change was heavily tested and behaved correctly. The brew-root is *not* (as far as I'm aware, and I tried a lot) pulling jdk8 unless java-1.8.0-openjdk* or java >= 1.8.0 is explicitly requested. If you have found some case when openjdk8 was pulled instead of 6 or 7, then it would really mean devel x qa failure and I'm terribly sorry for that and will fix immediately. Otherwise this should be closed->not a bug >
> We should fix the packages asap to make them provide java8* much like
> OpenJDK7 RPMs provide java7*.
This java7* was causing a lot of problems, and once we swithced to java = 1.7.0... there was couple of bugs requesting it back. At the end we ended up with dual provides java7* and java* = 1.7.0...
For 8 better solution was about to be found. And this was an epoch.
Omair had, as always, very refreshing idea - to remove jpackages provides at all. This approach ahve +1 from me muh more likely then provides java8 +1 from me as well, already noted in comment #1 :) Created attachment 949960 [details]
list of packages built after openjdk8 appeared in brew buildroot for 6.6
Created attachment 949961 [details]
sucessfull verification that no built (except openjdk8) was build by openjdk8 for 6.6
Our candlepin buildroot inherits from RHEL 6.6.Z. Here is a scratch build where we require java-devel >= 1.6.0, and openjdk 1.8 is pulled in: http://download.devel.redhat.com/brewroot/work/tasks/5970/8155970/root.log Jiri could you advise if you can spot what we might be doing incorrectly? pushed and building Changing bug description as bug 1189853 requested to have "java" provides in java-1.8.0-openjdk. Only java-devel is excluded intentionally, so it does not pollute mock build root. 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://rhn.redhat.com/errata/RHBA-2015-1427.html |