|
Bugzilla – Full Text Bug Listing |
| Summary: | LTC20605- IBMJava2-SDK-AMD64-142 misses a file | ||
|---|---|---|---|
| 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: | x86-64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Daniel Bornkessel
2005-11-14 16:30:54 UTC
Hi Daniel, I'm not involved in Java development. Did you simply want me to mirror this back to the IBM Bugzilla? I took the file from another IBM 64 Bit SDK, which seems to work. However, this is just a hack and shouldn't be the way to handle that problem. I am trying to mirror this through IBM's LTC bugzilla for which I already opened a bug for since I verified the missing file/broken symlink and went ahead and reported it to Java support. Hopefully, I'll get the two bugs synched up soon. Thanks for your patience. ---- Additional Comments From chavez@us.ibm.com(prefers email via lnx1138@us.ibm.com) 2006-01-12 22:00 EDT ------- I received the following update from Java support: The utetcf file is not actually required on the Java 1.4.2 Linux AMD64 build (but it is required for the other Linux 1.4.2 builds). The symlink is therefore extraneous and not required. I\'ll look at altering the packaging to remove the symlink for the AMD64 builds. Ok, good to know. Adjusted spec file to delete symbolic link. ---- Additional Comments From chavez@us.ibm.com(prefers email via lnx1138@us.ibm.com) 2006-02-06 16:23 EDT ------- The correction to the dangling symlink apperently did not make the Java 1.4.2 SR4 release that was made public at the end of last month. Though I see that you have already marked the Novell bug as RESOLVED. Yes, because I am just deleting the symlink when building the package as it is not needed. |