Package: libjna-java
Version: 3.2.7-2
Severity: important
The Maven jar artefact that this package deploys is no longer correct; it should
link to jna.jar but it currently links to jna-platform.jar.
Looking at the package the following in debian/rules is causing this issue:
# install. using platform.jar is a silly idea in /usr/share/java/ as it's bound
to collide
override_dh_auto_install:
mh_installjar -plibjna-java -l --usj-name=jna pom.xml build/jna.jar
mh_installjar -plibjna-java -l --usj-name=jna-platform pom.xml
build/platform.jar
The second mh_installjar command incorrectly references the pom.xml for jna NOT
platform.
This overwrites in the links created by the first command.
This will break any Maven based build process that depends on this package as
platform.jar
does not contain the expected classes.
The -3 package in experimental has the same bug.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-8-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libjna-java depends on:
ii libc6 2.13-4 Embedded GNU C Library: Shared lib
ii libffi5 3.0.9-4 Foreign Function Interface library
libjna-java recommends no packages.
Versions of packages libjna-java suggests:
pn libjna-java-doc <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
