https://bugzilla.redhat.com/show_bug.cgi?id=1735146
Bug ID: 1735146 Summary: eclipse-m2e-tycho: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: eclipse-m2e-tycho Assignee: mat.booth@redhat.com Reporter: releng@fedoraproject.org QA Contact: extras-qa@fedoraproject.org CC: eclipse-sig@lists.fedoraproject.org, java-sig-commits@lists.fedoraproject.org, mat.booth@redhat.com, mizdebsk@redhat.com Blocks: 1732841 Target Milestone: --- Classification: Fedora
eclipse-m2e-tycho failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36633165
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-m2e-tycho 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-m2e-tycho will be orphaned. Before branching of Fedora 32, eclipse-m2e-tycho 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=1735146
--- Comment #1 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595942 --> https://bugzilla.redhat.com/attachment.cgi?id=1595942&action=edit build.log
https://bugzilla.redhat.com/show_bug.cgi?id=1735146
--- Comment #2 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595943 --> https://bugzilla.redhat.com/attachment.cgi?id=1595943&action=edit root.log
file root.log too big, will only attach last 32768 bytes
https://bugzilla.redhat.com/show_bug.cgi?id=1735146
--- Comment #3 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595944 --> https://bugzilla.redhat.com/attachment.cgi?id=1595944&action=edit state.log
https://bugzilla.redhat.com/show_bug.cgi?id=1735146
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=1735146
--- 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=1735146
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=1735146
--- 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=1735146
--- 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=1735146
--- 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=1735146
--- 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=1735146
--- 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=1735146
--- 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=1735146
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=1735146
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=1735146
--- 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=1735146
Mat Booth mat.booth@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |WONTFIX Flags|needinfo?(extras-orphan@fed | |oraproject.org) | Last Closed| |2019-11-26 11:55:29
--- Comment #17 from Mat Booth mat.booth@redhat.com --- This package was retired from master and is now modularity only.
eclipse-sig@lists.fedoraproject.org
-
bugzilla＠redhat.com