https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Bug ID: 1735162 Summary: eclipse-subclipse: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: eclipse-subclipse Assignee: mat.booth@redhat.com Reporter: releng@fedoraproject.org QA Contact: extras-qa@fedoraproject.org CC: eclipse-sig@lists.fedoraproject.org, krzysztof.daniel@gmail.com, mat.booth@redhat.com, robert@marcanoonline.com Blocks: 1732841 Target Milestone: --- Classification: Fedora
eclipse-subclipse failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36633209
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-subclipse 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, eclipse-subclipse will be orphaned. Before branching of Fedora 32, eclipse-subclipse 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=1735162
--- Comment #1 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595990 --> https://bugzilla.redhat.com/attachment.cgi?id=1595990&action=edit build.log
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
--- Comment #2 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595991 --> https://bugzilla.redhat.com/attachment.cgi?id=1595991&action=edit root.log
file root.log too big, will only attach last 32768 bytes
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
--- Comment #3 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595992 --> https://bugzilla.redhat.com/attachment.cgi?id=1595992&action=edit state.log
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
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=1735162
--- 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=1735162
Fedora Release Engineering releng@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mat.booth@redhat. | |com)
--- Comment #6 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=1735162
--- 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=1735162
--- 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=1735162
--- 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=1735162
--- Comment #11 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=1735162
--- 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=1735162
--- 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=1735162
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|mat.booth@redhat.com |extras-orphan@fedoraproject | |.org
--- Comment #14 from Miro Hrončok mhroncok@redhat.com --- This package is now orphaned according to the Fedora's Fails To Build From Source policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_...
The effort was coordinated in https://pagure.io/releng/issue/8917
If you believe this was done in an error, please describe why exactly is that so in the releng issue linked above this line.
If you want to unorphan the package, please do so via the process described in
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Cl...
Replying here is not a way to unorphan the package. This comment was mass posted to all the affected bugzillas and I am not subscribed to comments here. Note that this process is semi-automated and based on a policy, it is not my personal initiative.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Fedora Release Engineering releng@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |extras-orphan@fedoraproject | |.org Flags|needinfo?(mat.booth@redhat. |needinfo?(extras-orphan@fed |com) |oraproject.org)
--- Comment #15 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=1735162
--- Comment #16 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=1735162
--- Comment #17 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 Fedora 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=1735162
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|extras-orphan@fedoraproject |mat.booth@redhat.com |.org |
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Fedora Release Engineering releng@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(extras-orphan@fed |needinfo?(mat.booth@redhat. |oraproject.org) |com)
--- Comment #18 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 Fedora 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=1735162
--- Comment #19 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 Fedora 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=1735162
--- Comment #20 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 Fedora 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=1735162
Fedora Admin XMLRPC Client fedora-admin-xmlrpc@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|mat.booth@redhat.com |extras-orphan@fedoraproject | |.org
--- Comment #21 from Fedora Admin XMLRPC Client fedora-admin-xmlrpc@redhat.com --- This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Fedora Admin user for bugzilla script actions fedora-admin-xmlrpc@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|extras-orphan@fedoraproject |mat.booth@redhat.com |.org |
--- Comment #22 from Fedora Admin user for bugzilla script actions fedora-admin-xmlrpc@fedoraproject.org --- This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED
--- Comment #23 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-e152c0d083 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e152c0d083
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #24 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-e152c0d083 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e152c0d083` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e152c0d083
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
--- Comment #25 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-f6d9d81a11 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f6d9d81a11` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f6d9d81a11
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
--- Comment #26 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-ee2e3e5f03 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ee2e3e5f03` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee2e3e5f03
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
--- Comment #27 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-1eeed34db0 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-1eeed34db0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1eeed34db0
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |eclipse-subclipse-4.3.0-8.f | |c31 Resolution|--- |ERRATA Last Closed| |2020-09-03 16:26:28
--- Comment #28 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-1eeed34db0 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=1735162
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|eclipse-subclipse-4.3.0-8.f |eclipse-subclipse-4.3.0-8.f |c31 |c31 | |eclipse-subclipse-4.3.0-8.f | |c32
--- Comment #29 from Fedora Update System updates@fedoraproject.org --- FEDORA-2020-ee2e3e5f03 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
eclipse-sig@lists.stg.fedoraproject.org
-
bugzilla＠redhat.com