Source: libisnativec-java
Version: 5.3.20100629+fix-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with javahelper
>    dh_update_autotools_config
>    dh_autoreconf
>    jh_linkjars
>    jh_build
> warning: [options] bootstrap class path not set in conjunction with -source 7
> ./src/de/intarsys/nativec/jna/JnaNativeHandle.java:129: error: incompatible 
> types: boolean cannot be converted to String
>               return getPointer().getString(index, true);
>                                                    ^
> ./src/de/intarsys/nativec/jna/JnaNativeHandle.java:184: error: incompatible 
> types: boolean cannot be converted to String
>               getPointer().setString(index, value, true);
>                                                    ^
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: ./src/de/intarsys/nativec/jna/JnaNativeFunction.java uses unchecked or 
> unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note: Some messages have been simplified; recompile with -Xdiags:verbose to 
> get full output
> 2 errors
> 1 warning
> jh_build: error: find ./src -name '*.java' -and -type f -print0 | xargs -s 
> 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp 
> /usr/share/java/jna.jar:/usr/share/java/isrt.jar:debian/_jh_build.isnativec 
> -d debian/_jh_build.isnativec -encoding ISO8859-1 -source 1.7 -target 1.7  
> returned exit code 123
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/06/20/libisnativec-java_5.3.20100629+fix-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to