This bug is part of the non-responsive maintainer procedure for btashton, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/. Please respond if you are still active in Fedora and want to maintain jeuclid.
This package has been very neglected by upstream as well as me. Seems like I should move to this fork? https://github.com/rototor/jeuclid
Hi Brennan. Sure, if it works, that's great. If not, I took a look at the existing f32 branch earlier, and all that needs doing is: 1) updating the JEuclid source to 3.1.9, 2) Patching root build.xml with: diff --git a/build.xml b/build.xml index b3b126d..8ec8806 100644 --- a/build.xml +++ b/build.xml @@ -4,6 +4,8 @@ <property environment="env"/> <path id="libs-build-classpath"> + <pathelement location="/usr/share/java/xml-commons-apis.jar" /> + <pathelement location="/usr/share/java/batik-all.jar" /> <fileset dir="./lib"> <include name="*.jar"/> </fileset> 3) patching the sources to replace "org.w3c.dom.events.CustomEvent" with "org.apache.batik.w3c.dom.events.CustomEvent" (see https://www.mail-archive.com/fop-users@xmlgraphics.apache.org/msg21062.html). Thanks.
Sorry, one more! 4) Remove the BuildRequires on checkstyle (code style testing is not needed in Fedora, and checkstyle was retired).
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.