libreswan failed to build from source in Fedora rawhide/f32 https://koji.fedoraproject.org/koji/taskinfo?taskID=41318676 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild Please fix libreswan 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, libreswan will be orphaned. Before branching of Fedora 33, libreswan 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
Created attachment 1659538 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1659539 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1659540 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
FEDORA-2020-d98ffda239 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d98ffda239
libreswan-3.30-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-83ac43d977
libreswan-3.30-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d98ffda239
libreswan-3.30-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
libreswan-3.30-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.