folly failed to build from source in Fedora rawhide/f36 https://koji.fedoraproject.org/koji/taskinfo?taskID=81460917 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild Please fix folly 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, folly will be orphaned. Before branching of Fedora 37, folly will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Created attachment 1853423 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1853424 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1853425 [details] state.log
*** Bug 2045554 has been marked as a duplicate of this bug. ***
*** Bug 2042690 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
FEDORA-2022-5852540ea0 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5852540ea0
FEDORA-2022-737d681400 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-737d681400
FEDORA-2022-737d681400 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-5852540ea0 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5852540ea0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5852540ea0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-5852540ea0 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.