https://bugzilla.redhat.com/show_bug.cgi?id=1736707
Bug ID: 1736707 Summary: springframework-social-twitter: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: springframework-social-twitter Assignee: extras-orphan@fedoraproject.org Reporter: releng@fedoraproject.org QA Contact: extras-qa@fedoraproject.org CC: extras-orphan@fedoraproject.org, java-sig-commits@lists.fedoraproject.org, puntogil@libero.it Blocks: 1732841 Target Milestone: --- Classification: Fedora
springframework-social-twitter failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36637717
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix springframework-social-twitter 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, springframework-social-twitter will be orphaned. Before branching of Fedora 32, springframework-social-twitter 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=1736707
--- Comment #2 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1599347 --> https://bugzilla.redhat.com/attachment.cgi?id=1599347&action=edit root.log
file root.log too big, will only attach last 32768 bytes
https://bugzilla.redhat.com/show_bug.cgi?id=1736707
--- Comment #1 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1599346 --> https://bugzilla.redhat.com/attachment.cgi?id=1599346&action=edit build.log
https://bugzilla.redhat.com/show_bug.cgi?id=1736707
--- Comment #3 from Fedora Release Engineering releng@fedoraproject.org --- Created attachment 1599348 --> https://bugzilla.redhat.com/attachment.cgi?id=1599348&action=edit state.log
https://bugzilla.redhat.com/show_bug.cgi?id=1736707
--- 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=1736707
Fedora Release Engineering releng@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(extras-orphan@fed | |oraproject.org)
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- 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=1736707
--- Comment #20 from Ben Cotton bcotton@redhat.com --- This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1736707
Ben Cotton bcotton@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2020-11-24 16:04:38
--- Comment #21 from Ben Cotton bcotton@redhat.com --- Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
java-sig-commits@lists.fedoraproject.org
-
bugzilla＠redhat.com