lasso fails to build with java-17-openjdk as sytem JDK. See https://fedoraproject.org/wiki/Changes/Java17 . See especially part about known failures: https://fedoraproject.org/wiki/Changes/Java17#common_issues_packagers_can_face_and_gathered_solutions For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=82430376 https://kojipkgs.fedoraproject.org/work/tasks/389/82430389/mock_output.log https://kojipkgs.fedoraproject.org/work/tasks/389/82430389/hw_info.log https://kojipkgs.fedoraproject.org/work/tasks/389/82430389/state.log https://kojipkgs.fedoraproject.org/work/tasks/389/82430389/build.log https://kojipkgs.fedoraproject.org/work/tasks/389/82430389/root.log We run the rebuild in side tag f36-java17, but as fail ratio was small, we expect this side tag to be merged into rawhide 7 or 8 of February 2022. To reproduce before this date simply: fedpkg clone lasso; cd lasso; fedpkg build --target f36-java17; #The target is crucial. After this date the usual fedpkg build in f36 and up should do. We run two reruns your package failed both. We had also run the mass rebuilds in copr since November. We keep all encountered failures. See them here: https://copr.fedorainfracloud.org/coprs/jvanek/java17//package/lasso You may find interesting additional informations here. Also we were spamming maintainers regualrly, check you spam folder. We had tried aprox 500 packages, and aprox 65 had failed, so the java-17-openjdk will be system JDK in f36, 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 f36 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.
Running automake-1.16 configure.ac:31: error: version mismatch. This is Automake 1.16.5, configure.ac:31: but the definition used by this AM_INIT_AUTOMAKE configure.ac:31: comes from Automake 1.16.3. You should recreate seems like unrelated to jdk17
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
The package was successfully built on 2022-01-20. Then there is your failure on 2022-02-05. After that there was no attempt. Koschei earliest F36 attempt is on 2022-05-21 and passing. No other failures. I sent F36 to rebuild <https://koji.fedoraproject.org/koji/taskinfo?taskID=94199334> and it passed. I guess the cause was some kind of temporary incompatibility in autotools. I will send the rebuild to updates.
FEDORA-2022-e1ce9d38d1 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e1ce9d38d1
FEDORA-2022-e1ce9d38d1 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e1ce9d38d1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e1ce9d38d1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e1ce9d38d1 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.