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 1977664

Summary:	waiverdb fails to build with Sphinx 4.0.2
Product:	[Fedora] Fedora	Reporter:	Karolina Surma <ksurma>
Component:	waiverdb	Assignee:	gnaponie
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	djc, gnaponie, lholecek, lucarval, mjia, mprahl, rbean, thrnciar, vmaljuli
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
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:	1975260
Bug Blocks:	1890881, 1927309, 1973718

Description Karolina Surma 2021-06-30 08:53:20 UTC

waiverdb fails to build with Sphinx 4.0.2 in Fedora 35 (currently Rawhide).

+ make -C docs html man text
make: Entering directory '/builddir/build/BUILD/waiverdb-1.3.0/docs'
Running Sphinx v4.0.2
Extension error:
Could not import extension sphinxcontrib.autohttp.flask (exception: cannot import name 'force_decode' from 'sphinx.util' (/usr/lib/python3.10/site-packages/sphinx/util/__init__.py))
make: *** [Makefile:20: html] Error 2

For the logs from testing build attempts, see:
https://copr.fedorainfracloud.org/coprs/ksurma/pygments-2.9.0/package/waiverdb/

You can test you package using Koji scratch build
koji build --scratch <srpm>

Sphinx 4.0.2 will be included in Fedora 35.
Let us know here if you have any questions. Thank you!

Comment 1 Lukas Holecek 2021-07-13 09:27:57 UTC

This is caused by a bug in Sphinx (https://github.com/sphinx-contrib/httpdomain/issues/46) and it looks like it has been already fixed in upstream recently.