https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Bug ID: 1735216 Summary: fop: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: fop Assignee: rlandman@redhat.com Reporter: releng@fedoraproject.org QA Contact: extras-qa@fedoraproject.org CC: c.david86@gmail.com, java-sig-commits@lists.fedoraproject.org, mizdebsk@redhat.com, rhbugs@n-dimensional.de, rlandman@redhat.com Blocks: 1732841 Target Milestone: --- Classification: Fedora
fop failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36633336
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix fop at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, fop will be orphaned. Before branching of Fedora 32, fop will be retired, if it still fails to build.
For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1732841 [Bug 1732841] (F31FTBFS) - Fedora 31 FTBFS Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #1 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1596135 --> https://bugzilla.redhat.com/attachment.cgi?id=1596135&action=edit build.log
file build.log too big, will only attach last 32768 bytes
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #2 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1596136 --> https://bugzilla.redhat.com/attachment.cgi?id=1596136&action=edit root.log
file root.log too big, will only attach last 32768 bytes
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #3 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1596137 --> https://bugzilla.redhat.com/attachment.cgi?id=1596137&action=edit state.log
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1700317 (F31FTBFS)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1700317 [Bug 1700317] Fedora 31 FTBFS Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #5 from Ben Cotton bcotton@redhat.com --- This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
David GEIGER geiger.david68210@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |geiger.david68210@gmail.com
--- Comment #6 from David GEIGER geiger.david68210@gmail.com --- Created attachment 1607840 --> https://bugzilla.redhat.com/attachment.cgi?id=1607840&action=edit 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
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Fedora Release Engineering releng@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rlandman@redhat.c | |om)
--- Comment #7 from Fedora Release Engineering releng@fedoraproject.org --- 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_... [3] https://fedoraproject.org/wiki/Releases/32/Schedule
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #8 from Fedora Release Engineering releng@fedoraproject.org --- 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_... [3] https://fedoraproject.org/wiki/Releases/32/Schedule
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #9 from Fedora Release Engineering releng@fedoraproject.org --- 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_... [3] https://fedoraproject.org/wiki/Releases/32/Schedule
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #10 from Fedora Release Engineering releng@fedoraproject.org --- 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_... [3] https://fedoraproject.org/wiki/Releases/32/Schedule
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #12 from Fedora Release Engineering releng@fedoraproject.org --- 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_... [3] https://fedoraproject.org/wiki/Releases/32/Schedule
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #13 from Fedora Release Engineering releng@fedoraproject.org --- 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_... [3] https://fedoraproject.org/wiki/Releases/32/Schedule
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #14 from Fedora Release Engineering releng@fedoraproject.org --- 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_... [3] https://fedoraproject.org/wiki/Releases/32/Schedule
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Peter Lemenkov lemenkov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |lemenkov@gmail.com Assignee|rlandman@redhat.com |lemenkov@gmail.com
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Ruediger Landmann rlandman@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rlandman@redhat.c | |om) |
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
--- Comment #15 from Jan Pokorný [poki] jpokorny@redhat.com --- 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/...
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED
--- Comment #16 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-9e2c693a16 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9e2c693a16
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #17 from Fedora Update System updates@fedoraproject.org --- 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
https://bugzilla.redhat.com/show_bug.cgi?id=1735216
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |fop-2.4-1.fc31 Resolution|--- |ERRATA Last Closed| |2020-02-29 22:31:47
--- Comment #18 from Fedora Update System updates@fedoraproject.org --- 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.
java-sig-commits@lists.fedoraproject.org