I've been bitten twice at least by versions of Python packages not being determined correctly, leading to FTBFS/FTI of dependent packages. As an example take a look at the review.txt of the following build:

https://copr.fedorainfracloud.org/coprs/gui1ty/spyder/build/6421158/

First of all the build itself as well as the builds of dependent packages in the Copr repo succeeded. All is looking peachy. Checking the package's review.txt generated by fedora-review, I see:

Provides
--------
python3-lsp-server:
    pylsp
    python-lsp-server
    python3-lsp-server
    python3.12-lsp-server
    python3.12dist(python-lsp-server)
    python3dist(python-lsp-server)

However, querying the resulting RPM:

$ rpm -q --provides -p python3-lsp-server-1.8.0-1.fc40.noarch.rpm 
warning: python3-lsp-server-1.8.0-1.fc40.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID 41dcac2a: NOKEY
pylsp = 1.8.0-1.fc40
python-lsp-server = 1.8.0-1.fc40
python3-lsp-server = 1.8.0-1.fc40
python3.12-lsp-server = 1.8.0-1.fc40
python3.12dist(python-lsp-server) = 0.1~~dev2
python3dist(python-lsp-server) = 0.1~~dev2

I see that the last two lines are wrong. Somehow the Python internal versions were not determined correctly. That subsequently leads to problems when trying to build or install dependent packages that require a specific version of the package, e.g.:

No matching package to install: 'python3dist(python-lsp-server) >= 1.4.1'

Could fedora-review include the versions in the Provides section? That would be very helpful in determining that the package was indeed build correctly.