Bug 2433973

Summary: darktable: FTBFS in Fedora rawhide/f44
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: darktableAssignee: Germano Massullo (Thetra) <germano.massullo>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: aekoroglu, asn, germano.massullo, kalevlember
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: darktable-5.4.1-1.fc42 darktable-5.4.1-1.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-02-18 00:56:13 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: 2384424    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2026-01-28 17:11:32 UTC
darktable failed to build from source in Fedora rawhide/f44

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
Please fix darktable 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,
darktable will be orphaned. Before branching of Fedora 45,
darktable 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 2026-01-28 17:12:02 UTC
Created attachment 2124258 [details]
build.log

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

Comment 2 Fedora Release Engineering 2026-01-28 17:12:09 UTC
Created attachment 2124259 [details]
root.log

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

Comment 3 Fedora Release Engineering 2026-01-28 17:12:12 UTC
Created attachment 2124260 [details]
state.log

Comment 4 Miloš Komarčević 2026-01-29 11:00:09 UTC
I think this is a false positive and can be ignored:

1. The failure was due to a broken GCC during mass rebuild, see https://bugzilla.redhat.com/show_bug.cgi?id=2430184#c11
2. The more recent builds w/ fixed GCC are fine in https://koschei.fedoraproject.org/package/darktable

Comment 5 Fedora Update System 2026-02-10 00:01:23 UTC
FEDORA-2026-ccb28f7626 (darktable-5.4.1-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-ccb28f7626

Comment 6 Fedora Update System 2026-02-10 00:53:39 UTC
FEDORA-2026-729a48a231 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-729a48a231`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-729a48a231

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

Comment 7 Fedora Update System 2026-02-10 01:51:14 UTC
FEDORA-2026-ccb28f7626 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-ccb28f7626`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ccb28f7626

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

Comment 8 Fedora Update System 2026-02-18 00:56:13 UTC
FEDORA-2026-729a48a231 (darktable-5.4.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2026-02-18 04:25:30 UTC
FEDORA-2026-ccb28f7626 (darktable-5.4.1-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.