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

Bug 1773370

Summary: graphite-api fails to build with Python 3.8 on Fedora 32+
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: graphite-apiAssignee: Piotr Popieluch <piotr1212>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: piotr1212
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-11 16:41:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1705705    
Bug Blocks: 1750908, 1750909, 1686977    

Description Miro Hrončok 2019-11-17 23:10:53 UTC
graphite-api fails to build with Python 3.8.0b4 in Fedora 32.

See the build failures at

DEBUG  Error: 
DEBUG   Problem: conflicting requests
DEBUG    - nothing provides python3.7dist(six) needed by python3-structlog-19.1.0-2.fc31.noarch
DEBUG    - nothing provides python(abi) = 3.7 needed by python3-structlog-19.1.0-2.fc31.noarch

It is not important whether the problem is caused by this package or another, this issue is blocking the Python 3.8 rebuild of this package.

If this package won't build with 3.8, it won't be installable, along with all its dependent packages, in Fedora 32 and further.

Furthermore, as it fails to install, its dependent packages will fail to install and/or build as well.

Please rebuild the package in Fedora 32 (rawhide).

Let us know here if you have any questions. Thank You!

Comment 1 Miro Hrončok 2019-11-25 10:27:12 UTC
What is the plan here? Do we try to keep the package or retire it?

Comment 2 Miro Hrončok 2019-12-10 16:36:32 UTC
Please respond.

Comment 3 Piotr Popieluch 2019-12-11 16:32:11 UTC
The upstream project seems inactive, better retire.