Bug 1370068 - typo in folder /usr/lib/jvm/ for jre symlink
Summary: typo in folder /usr/lib/jvm/ for jre symlink
Keywords:
Status: CLOSED DUPLICATE of bug 1285189
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: java-1.8.0-oracle
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: jiri vanek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 08:46 UTC by Oliver Ilian
Modified: 2016-08-25 09:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-25 09:00:50 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Oliver Ilian 2016-08-25 08:46:54 UTC
Description of problem:
One of the files in java-1.8.0-oracle-1.8.0.101-1jpp.1.el7.x86_64 has a "_" when it looks like it should be a "-"


Version-Release number of selected component (if applicable):
java-1.8.0-oracle-1.8.0.101-1jpp.1.el7.x86_64


Steps to Reproduce:
1. install java-1.8.0-oracle-1.8.0.101-1jpp.1.el7.x86_64
2. ll /usr/lib/jvm/


Actual results:
jre-1.8.0-openjdk-1.8.0.102-0.b14.el7.x86_64 -> java-1.8.0-openjdk-1.8.0.102-0.b14.el7.x86_64/jre
jre-1.8.0_oracle -> /etc/alternatives/jre_1.8.0_oracle
jre-1.8.0-oracle-1.8.0.101-1jpp.1.el7.x86_64 -> java-1.8.0-oracle-1.8.0.101-1jpp.1.el7.x86_64/jre

see the second line has a symlink "jre-1.8.0_oracle" when it looks like it should be "jre-1.8.0-oracle" (related to the naming of the other symlinks.

Comment 1 jiri vanek 2016-08-25 09:00:50 UTC
should be handled in 7.3

(btw, congratulations, you are probably the only user on the world of this symlink:)

Orale java do not have y stream udpates. So next z update for 7.3 will deliver this.

http://pkgs.devel.redhat.com/cgit/rpms/java-1.8.0-oracle/commit/?h=oracle-java-rhel-7.3&id=7dcad362f9781478ddc0b849314e560d51dce1b8

*** This bug has been marked as a duplicate of bug 1285189 ***

Comment 2 Jens Reimann 2016-08-25 09:26:53 UTC
Thanks for the congratulations, I guess you are right ;-)


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