Bug 2105348

Summary: python-sphinxcontrib-httpdomain doesn't work with Sphinx 5+
Product: [Fedora] Fedora Reporter: Karolina Surma <ksurma>
Component: python-sphinxcontrib-httpdomainAssignee: Dan Callaghan <djc>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: djc, jkadlcik
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: 2023-12-05 21:10:51 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:    
Bug Blocks: 2082944, 2105943, 2113156    

Description Karolina Surma 2022-07-08 15:53:48 UTC
During the integration efforts of Sphinx 5 / docutils 0.18.1 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

The same package is affected - copr-keygen.

The upstream has released version 1.8.0 which should make this extension work with Sphinx 5 smoothly.
Please update the package to ensure that when we update the documentation stack, all works fine.


Version-Release number of selected component (if applicable):
1.7.0-15.fc37

Comment 1 Ben Cotton 2022-08-09 13:21:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 2 Jakub Kadlčík 2022-08-24 00:13:45 UTC
> The same package is affected - copr-keygen.
> The upstream has released version 1.8.0 which should make this extension work

When I made my personal build of python-sphinxcontrib-httpdomain-1.8.0
and tried to build copr-keygen against it. I got 

Exception occurred:
  File "/usr/lib/python3.11/site-packages/sphinxcontrib/autohttp/flask_base.py", line 27, in translate_werkzeug_rule
    from werkzeug.routing import parse_rule
ImportError: cannot import name 'parse_rule' from 'werkzeug.routing' (/usr/lib/python3.11/site-packages/werkzeug/routing/__init__.py)

There is an upstream issue and PR for this
https://github.com/sphinx-contrib/httpdomain/issues/60
so I guess we will need to wait for yet another release

Comment 3 Aoife Moloney 2023-11-23 00:15:14 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2023-12-05 21:10:51 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.