|
Bugzilla – Full Text Bug Listing |
| Summary: | LTC20610- IBM Java executable can't handle symbolic links deeper than 1 correctly | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Daniel Bornkessel <dbornkessel> |
| Component: | Java | Assignee: | Kevin Corry <corryk> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bugproxy, david_edwards |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Daniel Bornkessel
2005-11-14 16:57:27 UTC
Hi Daniel, I'm not involved in Java development. Did you simply want me to mirror this back to the IBM Bugzilla? The spec file now creates a wrapper script for each affected binary ... this is, however just a work around. ---- Additional Comments From chavez@us.ibm.com(prefers email via lnx1138@us.ibm.com) 2006-01-12 21:58 EDT ------- Received the following update from the Java team: Update: Action taken : Recreated the problem. Created the symlink /usr/bin/java-> -> /etc/alternatives/java ->/workarea/userlvl/cxia32142 -20050929/inst.images/x86_linux_2/sdk/jre/bin/java . got the following output lolo:/usr/bin # ./java -version .JVM not found: libjvm.so - libjvm.so Action Plan:investigate further Did this make it into SR4? See comment 28 in bug #117085 ... it seems to work. I would appreciate a short notice if this was taken care of in SR4. Thanks, Daniel ---- Additional Comments From chavez@us.ibm.com(prefers email via lnx1138@us.ibm.com) 2006-02-10 10:36 EDT ------- I requested an update after providing your comment to the Java engineer. This was the reply: \"I will provide a testfix to you by monday evening my time.\" ---- Additional Comments From chavez@us.ibm.com(prefers email via lnx1138@us.ibm.com) 2006-02-28 11:44 EDT ------- I sent an email to the Java engineer to confirm whether or not the problem was somehow fixed in SR4. changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |FIXEDAWAITINGTEST
Resolution| |FIX_BY_IBM
------- Additional Comments From chavez@us.ibm.com(prefers email via lnx1138@us.ibm.com) 2006-03-01 08:39 EDT -------
I received the following update from the Java engineer:
\"I checked it today and it found to be working with 142 SR4.
Therefore we can conclude that this problem is fixed in 142 Sr4.\"
She later looked through the bugs fixed and was able to confirm it was fixed and
supplied me a defect number through which the code fix was delivered. So, with
that, I am closing this bug as fixed.
(In reply to comment #4) > Did this make it into SR4? > See comment 28 in bug #117085 ... it seems to work. > I would appreciate a short notice if this was taken care of in SR4. > Thanks, > Daniel > Yes - so I think this can be closed here now, too. fixed, close |