Bug 62105
Summary: | New version 1.3.1-2 has broken /etc/profile.d/java_jre.csh | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Nils Philippsen <nphilipp> |
Component: | IBMJava2-JRE | Assignee: | Karen Bennet <bennet> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | geoff.dolman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:48:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nils Philippsen
2002-03-27 15:48:09 UTC
fixed in 1.3.1-3 and later. Not really fixed (in 1.3.1-3): --- 8< --- [root@ls3130 i386]# head -n 1 /etc/profile.d/java_*csh ==> /etc/profile.d/java_jre.csh <== root = /opt/IBMJava2-131 ==> /etc/profile.d/java_sdk.csh <== root = /opt/IBMJava2-131 [root@ls3130 i386]# rpm -Vf /etc/profile.d/java_*csh [root@ls3130 i386]# rpm -qf /etc/profile.d/java_*csh IBMJava2-JRE-1.3.1-3 IBMJava2-SDK-1.3.1-3 --- >8 --- *** Bug 64929 has been marked as a duplicate of this bug. *** *** Bug 69643 has been marked as a duplicate of this bug. *** PS: As you can see above, the same bug exists in IBMJava2-SDK-1.3.1-3. Shall I open an own bug for it? An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2002-199.html *** Bug 98926 has been marked as a duplicate of this bug. *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |