ax25-tools failed to build from source in Fedora rawhide/f32 https://koji.fedoraproject.org/koji/taskinfo?taskID=41315951 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild Please fix ax25-tools 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, ax25-tools will be orphaned. Before branching of Fedora 33, ax25-tools 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 1658489 [details] build.log
Created attachment 1658490 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1658491 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Dear Maintainer, your package has not been built successfully in 32. 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 33 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 31 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_to_install/ [3] https://fedoraproject.org/wiki/Releases/33/Schedule
I'll work on it when I can.
Created attachment 1663791 [details] Proposed spec fix This is spec file patch. It seems that the patches were upstreamed and are not needed. Also it seems the FTBFS is not related to gcc-10.
Thanks for the patch. I had just verified with upstream that they no longer support the installconf target. That's the quick fix, however, I'm also considering moving back to the canonical upstream instead of this fork.