Bug 2385493

Summary: python-moddb: FTBFS in Fedora rawhide/f43
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: python-moddbAssignee: Chris King <bunnyapocalypse>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bunnyapocalypse, steve
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-moddb-0.12.0-4.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-09-23 00:15:47 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: 2339432, 2373702    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2025-07-31 10:25:05 UTC
python-moddb failed to build from source in Fedora rawhide/f43

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
Please fix python-moddb 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,
python-moddb will be orphaned. Before branching of Fedora 44,
python-moddb 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 2025-07-31 10:25:10 UTC
Created attachment 2101384 [details]
build.log

Comment 2 Fedora Release Engineering 2025-07-31 10:25:16 UTC
Created attachment 2101385 [details]
root.log

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

Comment 3 Fedora Release Engineering 2025-07-31 10:25:20 UTC
Created attachment 2101386 [details]
state.log

Comment 4 Miro HronĨok 2025-08-26 11:08:43 UTC
Hello. This is a bulk comment.

This package still needs to be rebuilt and/or shipped with Python 3.14.0rc2+ bytecode in Fedora 43.

The Beta Freeze of Fedora 43 is scheduled to start today. Please prioritize this bugzilla accordingly.

Thanks.

Comment 5 Chris King 2025-09-12 14:55:00 UTC
looking into this.

Failing to build due to missing python-curl-adapter

I've just tired to build the curl-adapter library (https://pypi.org/project/curl-adapter/#files)


Turns out it depends on curl-cffi (https://github.com/lexiforest/curl_cffi/tree/main)


Which in turn depends on curl-impersonate (in fact, curl-cffi it tries to pull this from Github as a part of it's build script... https://github.com/lexiforest/curl_cffi/blob/1692142c499cd91b7f7528a823144d9758a5b34d/scripts/build.py#L64) (https://github.com/lexiforest/curl-impersonate)


Whereas the first two are python packages, and thus pretty easy to package (see attached specs), the third is a fork of Curl, as far as I can tell. I am thus expecting this will be a much bigger pain in the ass to package (I am a bit out of my depth with regards to packaging C stuff...)

Comment 6 Fedora Update System 2025-09-14 18:24:17 UTC
FEDORA-2025-853fc6b33f (Rolling back python-moddb to 0.12.0) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-853fc6b33f

Comment 7 Fedora Update System 2025-09-15 01:33:55 UTC
FEDORA-2025-853fc6b33f 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-2025-853fc6b33f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-853fc6b33f

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

Comment 8 Fedora Update System 2025-09-23 00:15:47 UTC
FEDORA-2025-853fc6b33f (Rolling back python-moddb to 0.12.0) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.