| Summary: | Java JDK/JRE installation | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Graeme Gemmill <grimble00060> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | geiger.david68210, luigiwalser, pterjan |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Graeme Gemmill
2015-05-09 16:53:58 CEST
The jvm-common misspelling is actually from javapackages-tools, and is an upstream (Fedora) problem, so it needs to be fixed there. It's incorrect in this file:
javapackages-4.1.0/macros.d/macros.jpackage
it happens in three places:
%_jvmcommonlibdir %{_prefix}/lib/jvm-commmon
%_jvmcommondatadir %{_datadir}/jvm-commmon
%_jvmcommonsysconfdir %{_sysconfdir}/jvm-commmon
This needs to be reported to RedHat's bugzilla and/or to their packager.
As for libjpnp2.so, that file does not exist in OpenJDK, so that's not a bug. I guess if you need that file, you need Oracle Java, which we can't provide.
As for it not working with the plugin tests, that is not true; it does work. In each instance you'll have to click something to allow it to run the plugin, for security reasons.
So, in summary, the jvm-commmon thing needs to be reported upstream and the rest is INVALID, so I'll mark this as such.Status:
NEW =>
RESOLVED Oh, our javapackages-tools in Mageia 5 is from Fedora 21, BTW. |