javamail 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=47152758
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 javamail; cd javamail; 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/javamail
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.
Changes to a dependency were made to fix this build failure:
When I try to reproduce/test I see:
$ fedpkg build --target f33-java11
Could not execute build: Package javamail-1.5.2-13.fc33 has already been built
Note: You can skip this check with --skip-nvr-check. See help for more info.
Should I add --skip-nvr-check? Is that safe?
mock now uses java11 to build javamail, and it succeeds (with some warnings about implementing deprecated APIs).
(In reply to Jie Kang from comment #2)
> When I try to reproduce/test I see:
> $ fedpkg build --target f33-java11
> Could not execute build: Package javamail-1.5.2-13.fc33 has already been
> Note: You can skip this check with --skip-nvr-check. See help for more info.
> Should I add --skip-nvr-check? Is that safe?
No. A single build can only exist once. The release would have to be bumped. Note that mbooth built it in f33 here:
Mind you, its hard-coding to use java-1.8.0-openjdk for building. See below.
If you want to reproduce the failure you'd likely need to revert this:
and rebuild with --scratch (and possibly --srpm). Note: The --target f33-java11 is no longer needed as the f33-java11 builds got merged into f33.
(In reply to Stuart D Gathman from comment #3)
> mock now uses java11 to build javamail, and it succeeds (with some warnings
> about implementing deprecated APIs).
Are you sure it's using JDK 11 to build? https://src.fedoraproject.org/rpms/javamail/c/63f97136fecf964e791a9ad65604e28899b29526?branch=master and https://koji.fedoraproject.org/koji/buildinfo?buildID=1540254 suggests it's building with java-1.8.0-openjdk (hard coded). The logs indicate both JDKs are installed. JDK 8 is being selected as build JDK.
Scratch build for latest master works:
As expected it's using JDK 8 to build:
+ export JAVA_HOME=/usr/lib/jvm/java-1.8.0
+ /usr/bin/python3 /usr/share/java-utils/mvn_build.py --xmvn-javadoc -- -Dmaven.test.failure.ignore=true
Getting in to build without hard-coding is another matter. Closing this bug, though.