Bug 1823519 - python-sphinx-click fails to build with Sphinx 3.0.0
Summary: python-sphinx-click fails to build with Sphinx 3.0.0
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-sphinx-click
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1822901
Blocks: SPHINX3
TreeView+ depends on / blocked
 
Reported: 2020-04-13 20:58 UTC by Charalampos Stratakis
Modified: 2020-04-16 11:15 UTC (History)
4 users (show)

Fixed In Version: python-sphinx-click-2.3.2-1.fc33
Clone Of:
Environment:
Last Closed: 2020-04-16 11:15:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Charalampos Stratakis 2020-04-13 20:58:31 UTC
python-sphinx-click fails to build with Sphinx 3.0.0.

error: Could not find suitable distribution for Requirement.parse('sphinx<3.0,>=1.5')

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/cstratak/sphinx_3.0.0/fedora-rawhide-x86_64/01335472-python-sphinx-click/

For all our attempts to build python-sphinx-click with Sphinx 3.0.0, see:
https://copr.fedorainfracloud.org/coprs/cstratak/sphinx_3.0.0/package/python-sphinx-click/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Sphinx 3:
https://copr.fedorainfracloud.org/coprs/cstratak/sphinx_3.0.0/

Let us know here if you have any questions.

Sphinx 3 will be included in Fedora 33. To make that update smoother, we're building the dependent packages in Copr.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Miro Hrončok 2020-04-13 23:46:38 UTC
sphinx-click 2.3.2 might fix this.

Comment 2 Charalampos Stratakis 2020-04-14 23:38:51 UTC
Indeed, tested locally, the issue is fixed with the updated version.


Note You need to log in before you can comment on or make changes to this bug.