Learn more about these different git repos.
Other Git URLs
Causes python-sphinx to be FTI preventing builds of all packages depending on it.
Problem 1: conflicting requests DEBUG util.py:461: - nothing provides (python3.13dist(alabaster) >= 0.7.14 with python3.13dist(alabaster) < 0.8) needed by python3-sphinx-1:7.3.7-2.fc41.noarch from build DEBUG util.py:461: Problem 2: package python3-sphinxcontrib-log-cabinet-1.0.1-18.fc41.noarch from build requires python3.13dist(sphinx), but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:461: - nothing provides (python3.13dist(alabaster) >= 0.7.14 with python3.13dist(alabaster) < 0.8) needed by python3-sphinx-1:7.3.7-2.fc41.noarch from build DEBUG util.py:461: Problem 3: package python3-Pallets-Sphinx-Themes-2.1.3-2.fc41.noarch from build requires python3.13dist(sphinx) >= 3, but none of the providers can be installed DEBUG util.py:461: - package python3-Pallets-Sphinx-Themes-2.1.3-2.fc41.noarch from build requires python3-sphinx, but none of the providers can be installed DEBUG util.py:461: - conflicting requests DEBUG util.py:461: - nothing provides (python3.13dist(alabaster) >= 0.7.14 with python3.13dist(alabaster) < 0.8) needed by python3-sphinx-1:7.3.7-2.fc41.noarch from build DEBUG util.py:610: Child return code was: 1
@ksurma wrote:
It seems alabaster has been updated without checking compatibility with Sphinx
ASAP
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
Any package depending on python-sphinx will become FTBFS.
@jujens Please, coordinate next time 🙏
Related: https://bugzilla.redhat.com/show_bug.cgi?id=2307234
Metadata Update from @jnsamyak: - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
This has been untagged from f42 now, can you please check and close this? If nothing else is required?
Thu Aug 22 18:43:13 2024 python-sphinx-theme-alabaster-1.0.0-1.fc42 untagged from f42 by jnsamyak
Yes, seems alright now, thanks!
Metadata Update from @frantisekz: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@frantisekz it seemed like a minor upgrade I could easily squeeze in with other ones this morning :cry: I didn’t even know sphinx required it directly. Sorry for the mess that resulted from it. And thanks for solving this :raised_hands:
I’ve also just reverted the commit that made the update to avoid the package being updated again by mistake.
Log in to comment on this ticket.