nethack-vultures failed to build from source in Fedora rawhide/f34 https://koji.fedoraproject.org/koji/taskinfo?taskID=60905414 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild Please fix nethack-vultures 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, nethack-vultures will be orphaned. Before branching of Fedora 35, nethack-vultures 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 1752946 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1752947 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1752948 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 34. 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. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2021-03-29). A week before the mass branching of Fedora 35 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 33 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
I took a look at this. My guess is that bison changed somehow so that the header file is used by the generated parser program now, when it wasn't before. Otherwise I don't see how it could have worked in the past. However the root cause seems to be some make shenanigans, possibly to help incremental builds after a bison failure. Bison is directed to output its files to temporary files and then they are moved back to where they are expected to be. This works for the flex file where the include file is manually named. But it doesn't work for the parser file where the name matches the name of the temporary output file automatically. We don't care about incremental builds, so changing this shouldn't cause a problem. I'll try to try this out soon. If there aren't other issues, this might be working again soon.
FEDORA-2021-f593e41d88 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f593e41d88
FEDORA-2021-f593e41d88 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f593e41d88` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f593e41d88 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-f593e41d88 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.