https://bugzilla.redhat.com/show_bug.cgi?id=1735152
Bug ID: 1735152 Summary: eclipse-nls: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: eclipse-nls Assignee: sean+rh@flanigan.org Reporter: releng@fedoraproject.org QA Contact: extras-qa@fedoraproject.org CC: i18n-bugs@lists.fedoraproject.org, petersen@redhat.com, sean+rh@flanigan.org Blocks: 1732841 Target Milestone: --- Classification: Fedora
eclipse-nls failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36633177
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-nls 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-nls will be orphaned. Before branching of Fedora 32, eclipse-nls 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=1735152
--- Comment #1 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595960 --> https://bugzilla.redhat.com/attachment.cgi?id=1595960&action=edit build.log
https://bugzilla.redhat.com/show_bug.cgi?id=1735152
--- Comment #2 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595961 --> https://bugzilla.redhat.com/attachment.cgi?id=1595961&action=edit root.log
file root.log too big, will only attach last 32768 bytes
https://bugzilla.redhat.com/show_bug.cgi?id=1735152
--- Comment #3 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1595962 --> https://bugzilla.redhat.com/attachment.cgi?id=1595962&action=edit state.log
https://bugzilla.redhat.com/show_bug.cgi?id=1735152
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=1735152
Ben Cotton bcotton@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|rawhide |31
https://bugzilla.redhat.com/show_bug.cgi?id=1735152
Fedora Release Engineering releng@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sean+rh@flanigan. | |org)
--- Comment #5 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=1735152
--- 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=1735152
--- 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=1735152
--- 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=1735152
--- 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 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=1735152
--- 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=1735152
--- 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=1735152
Miro Hrončok mhroncok@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|sean+rh@flanigan.org |extras-orphan@fedoraproject | |.org
--- Comment #13 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=1735152
Fedora Release Engineering releng@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |extras-orphan@fedoraproject | |.org Flags|needinfo?(sean+rh@flanigan. |needinfo?(extras-orphan@fed |org) |oraproject.org)
--- 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=1735152
--- 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=1735152
--- 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 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=1735152
--- 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=1735152
--- 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=1735152
--- 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=1735152
Parag Nemade pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |WONTFIX Last Closed| |2020-04-10 06:40:19
--- Comment #20 from Parag Nemade pnemade@redhat.com --- This got retired on 26th Dec 2019. Hence closing this bug.
i18n-bugs@lists.fedoraproject.org
-
bugzilla＠redhat.com