Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1735216
Summary: | fop: FTBFS in Fedora rawhide/f31 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||||
Component: | fop | Assignee: | Peter Lemenkov <lemenkov> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 31 | CC: | c.david86, geiger.david68210, java-sig-commits, jpokorny, lemenkov, mizdebsk, rhbugs, rlandman | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | fop-2.4-1.fc31 | Doc Type: | If docs needed, set a value | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2020-02-29 22:31:47 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: | 1700317, 1732841 | ||||||||||||
Attachments: |
|
Description
Fedora Release Engineering
2019-07-31 19:13:42 UTC
Created attachment 1596135 [details]
build.log
file build.log too big, will only attach last 32768 bytes
Created attachment 1596136 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1596137 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. Created attachment 1607840 [details] Update to newer batik 1.11 This upstream patch fixes build with new batik 1.11! http://svnweb.mageia.org/packages?view=revision&revision=1431926 Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 31 will be retired. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 31 will be retired. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 31 will be retired. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 31 will be retired. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages not successfully rebuilt at least on 30 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages not successfully rebuilt at least on 30 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages not successfully rebuilt at least on 30 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Dear Maintainer, your package has not been built successfully in 31. 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. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages not successfully rebuilt at least on 30 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Retaining information from the most recent mass rebuild[1], https://koji.fedoraproject.org/koji/taskinfo?taskID=41317181, that will probably dissappear in a while, from root.log: > DEBUG util.py:598: Last metadata expiration check: 0:00:01 ago on Sun Feb 2 01:08:34 2020. > DEBUG util.py:596: Error: > DEBUG util.py:596: Problem: conflicting requests > DEBUG util.py:596: - nothing provides mvn(avalon-logkit:avalon-logkit) needed by avalon-framework-4.3-24.fc31.noarch > DEBUG util.py:598: (try to add '--skip-broken' to skip uninstallable packages) Any idea what's going on with "mvn(avalon-logkit:avalon-logkit)" virtual provides/requires? Is it caused by avalon-framework failure to build as well? https://kojipkgs.fedoraproject.org/mass-rebuild/f32-failures.html Also for posterity, the current build from mass rebuild[1], https://koji.fedoraproject.org/koji/taskinfo?taskID=41315925, fails with this in root.log: > DEBUG util.py:598: Last metadata expiration check: 0:00:01 ago on Sun Feb 2 00:47:15 2020. > DEBUG util.py:596: No matching package to install: 'mvn(avalon-logkit:avalon-logkit)' > DEBUG util.py:596: Not all dependencies satisfied > DEBUG util.py:596: Error: Some packages could not be found.a It would be great to have these fixed so that publican, depending on fop, can actually work (currently blocks a rebuild of pacemaker, also currently listed in that f32-failures.html page because of that). [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/MZULCOMKMKXROVDSRKOXD4JY342GKBOH/ FEDORA-2020-9e2c693a16 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9e2c693a16 fop-2.4-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9e2c693a16 fop-2.4-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |