Bug 2329888

Summary: python-packvers fails to build with sphinx 8.x: ERROR: Invalid value `None` in intersphinx_mapping['https://docs.python.org/'].
Product: [Fedora] Fedora Reporter: Tomáš Hrnčiar <thrnciar>
Component: python-packversAssignee: Robert-André Mauchin 🐧 <eclipseo>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: eclipseo, ksurma, mhroncok, python-packagers-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-packvers-21.5-10.fc43 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-08-27 21:39:26 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: 2300528, 2322407, 2339432, 2275375    

Description Tomáš Hrnčiar 2024-12-02 11:10:27 UTC 
python-packvers fails to build with sphinx 8.x in Fedora 42 (currently Rawhide).

The issue detected:
```
ERROR: Invalid value `None` in intersphinx_mapping['https://docs.python.org/']. Expected a two-element tuple or list.

Configuration error:
Invalid `intersphinx_mapping` configuration (1 error).
```

The intersphinx_mapping error can be easily fixed by adjusting conf.py.
You can take an inspiration from this PR: https://github.com/jupyterlab/jupyterlab/pull/14423

Please work with upstream on this issue, I plan to ship sphinx 8 in two weeks.


For the logs from testing build attempts, see:
https://copr.fedorainfracloud.org/coprs/thrnciar/python-sphinx/package/python-packvers/

You can test you package in mock running:

$ mock -r fedora-rawhide-x86_64
--addrepo=https://download.copr.fedorainfracloud.org/results/thrnciar/python-sphinx/fedora-rawhide-x86_64/ --no-clean your.src.rpm
$ mock -r fedora-rawhide-x86_64
--addrepo=https://download.copr.fedorainfracloud.org/results/thrnciar/python-sphinx/fedora-rawhide-x86_64/ shell

We'd like to include Sphinx 8 in Fedora 42.
Let us know here if you have any questions. Thank you!
Comment 1 Aoife Moloney 2025-02-26 13:18:53 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.
Comment 2 Fedora Release Engineering 2025-06-01 04:22:25 UTC 
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2025-01-27).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html
Comment 3 Fedora Release Engineering 2025-06-22 04:22:24 UTC 
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2025-01-27).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html
Comment 4 Fedora Release Engineering 2025-07-13 04:22:19 UTC 
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2025-01-27).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html
Comment 5 Fedora Release Engineering 2025-08-03 04:22:12 UTC 
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2025-01-27).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html
Comment 6 Fedora Release Engineering 2025-08-24 04:22:09 UTC 
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2025-01-27).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html