Bug 10662

Summary:	Non-existing JNI_LIBDIR in /etc/java/java.conf
Product:	Mageia	Reporter:	Hartmut Goebel <h.goebel>
Component:	RPM Packages	Assignee:	D Morgan <dmorganec>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	Keywords:	Junior_job, Triaged
Version:	3
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	jpackage-utils-1.7.5-20.mga3.src.rpm	CVE:
Status comment:

Description Hartmut Goebel 2013-06-30 17:48:24 CEST

In a Mageia 3 system, just upgraded from Mageia 2, JNI_LIBDIR is defined as beeing /usr/lib/java, but this path does not exit.

$ grep JNI_LIBDIR /etc/java/java.conf
JNI_LIBDIR=/usr/lib/java
JAVAJNI_LIBDIR=/usr/share/java-jni

$ ls -d /usr/*/java*
/usr/bin/java@          /usr/lib64/java/        /usr/share/java-1.6.0/
/usr/bin/java2groovy*   /usr/lib64/java-1.5.0/  /usr/share/java-1.7.0/
/usr/bin/javac@         /usr/lib64/java-1.6.0/  /usr/share/javadoc/
/usr/bin/javadoc@       /usr/lib64/java-1.7.0/  /usr/share/java-ext/
/usr/bin/javah@         /usr/lib64/java-ext/    /usr/share/javahelp2/
/usr/bin/javap@         /usr/lib/java/          /usr/share/java-jni/
/usr/bin/javaws@        /usr/share/java/        /usr/share/java-utils/
/usr/bin/javaws.itweb*  /usr/share/java-1.5.0/  /usr/share/javazi/

Interestingly, on another system, upgraded from Mageia 2 to 3, too, JNI_LIBDIR is correctly set to /usr/lib64/java .

Manuel Hiebel 2013-07-03 09:44:31 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => dmorganec

Hartmut Goebel 2013-07-26 09:52:25 CEST

Keywords: (none) => Junior_job

Comment 1 Marja Van Waes 2015-03-31 16:05:22 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD