xbean fails to build with java-11-openjdk as sytem JDK. See https://fedoraproject.org/wiki/Changes/Java11 .
See especially part about known failures: https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_face_and_gathered_solutions
For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=47163984
We run the rebuild longer then 10days ago. Log may be gone. Also your package may be passing in regular rawhide.
To reproduce, simply: fedpkg clone xbean; cd xbean; fedpkg build --target f33-java11; #The target is crucial.
We run two reruns your package failed both.
Surprisingly, your package is passing in our initial copr - https://copr.fedorainfracloud.org/coprs/jvanek/java11/package/xbean
That usually mean that it is jdk11 independent error, or platform (non-intel) specific failure. Good luck.
We had tried 650 packages, and 500 had passed, so the java-11-openjdk will be system JDK in f33, and you should fix your package if you want to keep it alive. Usually the fix is simple, and best is to update the package to latest upstream version.
There will be usual mass rebuild once f33 branches. You may got another FTBFS bug.
Let us know here if you have any questions, here in bug, or at java-devel.org .
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side if needed.
highlight: This was rebuild in sidetag f33-java11. Thus --target is really necessary to reproduce failure.
please note: This side tag, f33-java11, will be merged to main f33 buildroot in aprox 14 days.
PS: Turns out, I was wrong, xbean 4.16 requires a newer version of objectweb-asm, not a newer version of the JDK.
The previous fix (to pin xbean java-1.8.0-openjdk) works but was broken by a dependency that was compiled with Java 11 bytecode (apache-commons-compress), which was fixed in the meantime.
Another build submitted today finished successfully:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1540797