Bug 2300627
Summary: | dom4j: FTBFS in Fedora rawhide/f41 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
Component: | dom4j | Assignee: | Stuart D Gathman <stuart> | ||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | rawhide | CC: | hdegoede, mizdebsk, stuart | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | dom4j-2.1.4-1.fc42 | Doc Type: | If docs needed, set a value | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2025-02-03 14:00:33 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 2260875 | ||||||||||
Attachments: |
|
Description
Fedora Release Engineering
2024-07-29 17:55:13 UTC
Created attachment 2040968 [details]
build.log
file build.log too big, will only attach last 32768 bytes
Created attachment 2040969 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 2040970 [details]
state.log
Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 41. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2024-09-23). A week before the mass branching of Fedora 42 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 40 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 41. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2024-09-23). A week before the mass branching of Fedora 42 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 40 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 41. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2024-09-23). A week before the mass branching of Fedora 42 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 40 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html I am mockbuilding 2.1.4. The 2.0.3 version is for java 8+, and may have issues with latest java. I won't push util there is some checking of compatibility issues. (In reply to Stuart D Gathman from comment #7) > I am mockbuilding 2.1.4. The 2.0.3 version is for java 8+, and may have > issues with latest java. I won't push util there is some checking of > compatibility issues. Thank you for working on this. AFAICT the only user of dom4j is the bolzplatz2006 game. You can either try that yourself with the new build, or do a scratch-build and send me the link to the scratch-build and I can test. If you want to test bolzplatz2006 yourself, note that this is a X11 game which relies on a X-server keyboard grab for its input, which does not work under Wayland. As a workaround you can start the game from a xterm using "xterm -e bolzplatz2006". (the xterm will keep the wayland keyboard focus sending key events to Xwayland, which then sends them to the game because if the X-server kbd grab). The build failed test suite with missing classes. Hopefully these are in Fedora already. Otherwise, I can disable some test cases. Another user of dom4j was openas2 - which I need to get built again at some point. java.lang.NoClassDefFoundError: org/apache/xml/serializer/SerializerTrace java.lang.NoClassDefFoundError: org/apache/xml/serializer/OutputPropertiesFactory Stuart, January 25th, which is the deadline before we need to resolve this to avoid dom4j getting orphaned, is approaching fast. So I think we should just move forward with the new upstream version with the tests disabled for now. Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 41. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2024-09-23). A week before the mass branching of Fedora 42 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 40 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html Ok I have fixed the 2.1.4 testsuite issue by adding: @@ -50,6 +50,7 @@ BuildRequires: mvn(javax.xml.bind:jaxb-api) BuildRequires: mvn(org.testng:testng) BuildRequires: mvn(xerces:xercesImpl) BuildRequires: mvn(xalan:xalan) +BuildRequires: mvn(xalan:serializer) %description dom4j is an Open Source XML framework for Java. dom4j allows you to read, @@ -76,6 +77,7 @@ sed -i 's/runtime/compile/' pom.xml %pom_add_dep xalan:xalan::test %pom_add_dep org.testng:testng:6.8.21:test %pom_add_dep xerces:xercesImpl::test +%pom_add_dep xalan:serializer # Remove support for code which depends on ancient / deprecated classes # xpp2 (deprecated and not developed since 2003) And I have successfully tested the new package with bolzplatz2006. I'm going to commit + build this for F42 now, before the branching tomorrow, resolving this just in time to avoid dom4j getting retired because of it being FTBFS for too long. This has been fixed in the latest rawhide build: dom4j-2.1.4-1.fc42 closing. |