cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8927) Mark libjna-java + libjna-jni as incompatible in debian package
Date Thu, 29 Oct 2015 19:58:27 GMT


Robert Stupp commented on CASSANDRA-8927:

Hm - yes, adding a package conflict might not be the best solution.
Need to reproduce it to see how it manifests and can be fixed (but need to rebuild my linux
box first).

> Mark libjna-java + libjna-jni as incompatible in debian package
> ---------------------------------------------------------------
>                 Key: CASSANDRA-8927
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: Debian
>            Reporter: Robert Stupp
>            Assignee: Michael Shuler
>             Fix For: 2.1.x
> Current Debian (Wheezy) might bring {{libjna-java}} in version 3.2.7-4, which has incompatible
{{}} because since C* 2.1 we use JNA 4.0.0 (the native stuff changed):
> jna.jar includes all binaries for all supported platforms - so there's no need for libjna
installed separately.
> Since CASSANDRA-8714 has been committed, the incompatibility manifests in {{java.lang.NoClassDefFoundError:
Could not initialize class com.sun.jna.Native}} (which is caused by outdated libjna-java installed
via apt).
> Note: Debian jessie adds new package {{libjna-jni}} (4.1.0-1) in addition to {{libjna-java}}
(4.1.0-1) - both contain the {{}}. Although these seem to work, we might
hit the same issue when there's a need to upgrade JNA to 4.2.x sometime.

This message was sent by Atlassian JIRA

View raw message