Bug 2226387

Summary: rEFInd: FTBFS in Fedora rawhide/f39
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: rEFIndAssignee: Neal Gompa <ngompa13>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: davide, ngompa13
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rEFInd-0.14.2-1.fc40 rEFInd-0.14.2-1.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-15 01:28:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2168842, 2231791    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2023-07-25 20:01:34 UTC
rEFInd failed to build from source in Fedora rawhide/f39

https://koji.fedoraproject.org/koji/taskinfo?taskID=103701980


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
Please fix rEFInd 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,
rEFInd will be orphaned. Before branching of Fedora 40,
rEFInd 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 2023-07-25 20:01:38 UTC
Created attachment 1979543 [details]
build.log

Comment 2 Fedora Release Engineering 2023-07-25 20:01:41 UTC
Created attachment 1979544 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2023-07-25 20:01:44 UTC
Created attachment 1979545 [details]
state.log

Comment 4 Fedora Release Engineering 2023-08-16 08:04:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 5 Neal Gompa 2024-07-09 23:33:10 UTC
Working on it.

Comment 6 Fedora Update System 2024-07-13 17:57:48 UTC
FEDORA-2024-83d381847f (rEFInd-0.14.2-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-83d381847f

Comment 7 Fedora Update System 2024-07-13 17:57:51 UTC
FEDORA-2024-93375eeb4b (rEFInd-0.14.2-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-93375eeb4b

Comment 8 Fedora Update System 2024-07-14 02:23:20 UTC
FEDORA-2024-83d381847f has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-83d381847f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-83d381847f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2024-07-14 04:30:04 UTC
FEDORA-2024-93375eeb4b has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-93375eeb4b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-93375eeb4b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2024-07-15 01:28:55 UTC
FEDORA-2024-83d381847f (rEFInd-0.14.2-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2024-07-22 01:48:36 UTC
FEDORA-2024-93375eeb4b (rEFInd-0.14.2-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.