Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1923290 - nethack-vultures: FTBFS in Fedora rawhide/f34
Summary: nethack-vultures: FTBFS in Fedora rawhide/f34
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nethack-vultures
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bruno Wolff III
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F34FTBFS
TreeView+ depends on / blocked
 
Reported: 2021-02-01 16:24 UTC by Fedora Release Engineering
Modified: 2021-03-19 20:10 UTC (History)
1 user (show)

Fixed In Version: nethack-vultures-2.1.2-30.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-19 20:10:12 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2021-02-01 16:24 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2021-02-01 16:24 UTC, Fedora Release Engineering 		no flags Details
state.log (1023 bytes, text/plain)
2021-02-01 16:24 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2021-02-01 16:24:00 UTC 
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/
Comment 1 Fedora Release Engineering 2021-02-01 16:24:02 UTC 
Created attachment 1752946 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Fedora Release Engineering 2021-02-01 16:24:04 UTC 
Created attachment 1752947 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2021-02-01 16:24:05 UTC 
Created attachment 1752948 [details]
state.log
Comment 4 Ben Cotton 2021-02-09 15:46:09 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.
Comment 5 Fedora Release Engineering 2021-02-14 04:22:57 UTC 
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
Comment 6 Fedora Release Engineering 2021-02-14 04:22:57 UTC 
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
Comment 7 Fedora Release Engineering 2021-03-07 04:22:36 UTC 
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
Comment 8 Bruno Wolff III 2021-03-07 18:39:24 UTC 
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.
Comment 9 Fedora Update System 2021-03-10 03:41:31 UTC 
FEDORA-2021-f593e41d88 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f593e41d88
Comment 10 Fedora Update System 2021-03-10 18:51:53 UTC 
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.
Comment 11 Fedora Update System 2021-03-19 20:10:12 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.