Please branch and build apache-ivy in epel10. If you do not wish to maintain apache-ivy in epel10, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/apache-ivy/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: salimma); please add me through https://src.fedoraproject.org/rpms/apache-ivy/adduser
So this is fun. JDK 11 is retired in Rawhide/F42+ - https://src.fedoraproject.org/rpms/java-11-openjdk/c/eef5cae1618adf22b43adb9e243580e26aaab57c?branch=rawhide - and of course RHEL 10 also only has JDK 21. And Ivy does not currently build against it [javac] /builddir/build/BUILD/apache-ivy-2.5.2-build/apache-ivy-2.5.2/src/java/org/apache/ivy/util/FileUtil.java:49: er ror: cannot find symbol [javac] import static java.util.jar.Pack200.newUnpacker; [javac] ^ [javac] symbol: class Pack200 [javac] location: package java.util.jar
Reported upstream: https://lists.apache.org/thread/9dfws64qkyoxbtk6474hpoyxxc2hncdv
The suggested fix in the thread upstream allows Ivy to compile, but fails generating javadoc Investigating further... Processing files: apache-ivy-javadoc-2.5.2-7.fc42.noarch RPM build errors: error: Could not open %files file /builddir/build/BUILD/apache-ivy-2.5.2-build/apache-ivy- 2.5.2/.mfiles-javadoc: No such file or directory Could not open %files file /builddir/build/BUILD/apache-ivy-2.5.2-build/apache-ivy-2.5 .2/.mfiles-javadoc: No such file or directory
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.