Bug 977901 - java-service-wrapper: Wrong installation directory
java-service-wrapper: Wrong installation directory
Product: Fedora
Classification: Fedora
Component: java-service-wrapper (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Mikolaj Izdebski
Fedora Extras Quality Assurance
: Patch
Depends On:
Blocks: 855780
  Show dependency treegraph
Reported: 2013-06-25 10:42 EDT by Mikolaj Izdebski
Modified: 2013-06-26 03:59 EDT (History)
1 user (show)

See Also:
Fixed In Version: 3.2.5-11
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-06-26 03:59:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch (1.78 KB, patch)
2013-06-25 10:44 EDT, Mikolaj Izdebski
no flags Details | Diff

  None (edit)
Description Mikolaj Izdebski 2013-06-25 10:42:17 EDT
Description of problem:
java-service-wrapper installs its binary JAR file into %{_libdir}/%{name}.  This location is not correct.  According to Java packaging guidelines [1] JAR files using JNI or containing JNI shared objects themselves MUST be placed in %{_jnidir} and CAN BE symlinked to %{_libdir}/%{name}. 

Version-Release number of selected component (if applicable):

Additional info:
[1] http://fedoraproject.org/wiki/Packaging:Java#Packaging_JAR_files_that_use_JNI
Comment 1 Mikolaj Izdebski 2013-06-25 10:44:33 EDT
Created attachment 765118 [details]
Proposed patch
Comment 3 Fedora Admin XMLRPC Client 2013-06-25 11:17:05 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 4 Mikolaj Izdebski 2013-06-25 11:44:15 EDT
Fixed in java-service-wrapper-3.2.5-11
Comment 5 Mikolaj Izdebski 2013-06-26 03:59:07 EDT
I believe that this bug is fixed in java-service-wrapper-3.2.5-11,
which is available in Fedora Rawhide, so I am closing this bug now.

The build containing the fix can be found at Koji:

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