Bug 2105943

Summary:	copr-keygen won't build with Sphinx 5+ in Rawhide
Product:	[Fedora] Fedora	Reporter:	Karolina Surma <ksurma>
Component:	copr-keygen	Assignee:	Copr Team <copr-team>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	clime7, copr-team, imvalgo, jkadlcik, msuchy, praiskup, turecek.dominik
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:	2022-09-07 06:28:00 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:
Embargoed:
Bug Depends On:	2105348
Bug Blocks:	2082944

Description Karolina Surma 2022-07-11 09:49:18 UTC

Description of problem:

During the integration efforts of Sphinx 5 / docutils 0.18.1 to Fedora Rawhide we were hit again by the same issue:

ImportError: cannot import name 'force_decode' from 'sphinx.util' (/usr/lib
/python3.10/site-packages/sphinx/util/__init__.py)
https://bugzilla.redhat.com/show_bug.cgi?id=1975260

This is a problem of python-sphinxcontrib-httpdomain but I'm creating this BZ to raise visibility.

How reproducible:
Always

Steps to Reproduce:
$ mock -r fedora-rawhide-x86_64 --addrepo=https://download.copr.fedorainfracloud.org/results/ksurma/sphinx-5/fedora-rawhide-x86_64/ --no-clean <your.src.rpm>
$ mock -r fedora-rawhide-x86_64 --addrepo=https://download.copr.fedorainfracloud.org/results/ksurma/sphinx-5/fedora-rawhide-x86_64/ shell

Comment 1 Ben Cotton 2022-08-09 13:21:56 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 2 Pavel Raiskup 2022-09-07 06:28:00 UTC

Thank you for the early report, Karolina!  We did not have a chance to take 
a look at this until now.

I'm closing this bug as duplicate because the other one has had more updates recently (even though this one is actually the older one).

*** This bug has been marked as a duplicate of bug 2113156 ***