The test failures are because there doesn't seem to be a python-cryptography version in F38 that can allow this be installed:
Error:
Problem: cannot install the best update candidate for package python3-pyOpenSSL-21.0.0-4.fc37.noarch
- nothing provides ((python3.11dist(cryptography) < 40 or python3.11dist(cryptography) > 40) with (python3.11dist(cryptography) < 40.0.1 or python3.11dist(cryptography) > 40.0.1) with python3.11dist(cryptography) < 42~~ with python3.11dist(cryptography) >= 38) needed by python3-pyOpenSSL-23.2.0-1.fc38.noarch from @commandline
However, more importantly, I think this update clearly goes against the updates policy:
"As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. The update rate for any given release should drop off over time, approaching zero near release end-of-life; since updates are primarily bugfixes, fewer and fewer should be needed over time."
This is a major version update with several backwards-incompatible changes compared to the current version in F38, which is 21.0.0. Per the upstream changelog, since 21.0.0, the package has "Remove[d] support for SSLv2 and SSLv3", "The OpenSSL.crypto.X509StoreContextError exception has been refactored, changing its internal attributes", and "Removed X509StoreFlags.NOTIFY_POLICY" (as well as some new deprecations). These do not seem like changes that ought to go into a stable release without substantial justification; the justification for this update is only "it's a new version!" The "XXX is available" bugs are meant to prompt you to update the package in Rawhide (and maybe Branched), not in stable releases.
The current python-cryptography in F38 is 37.0.2; this update would require it to be bumped to at least 38, which would be another major version change.
Problema: não é possível instalar o melhor candidato à atualização para o pacote python3-pyOpenSSL-21.0.0-4.fc37.noarch
- nothing provides ((python3.11dist(cryptography) < 40 or python3.11dist(cryptography) > 40) with (python3.11dist(cryptography) < 40.0.1 or python3.11dist(cryptography) > 40.0.1) with python3.11dist(cryptography) < 42~~ with python3.11dist(cryptography) >= 38) needed by python3-pyOpenSSL-23.2.0-1.fc38.noarch from updates-testing
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update has been submitted for testing by pwouters.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
The test failures are because there doesn't seem to be a python-cryptography version in F38 that can allow this be installed:
However, more importantly, I think this update clearly goes against the updates policy:
"As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. The update rate for any given release should drop off over time, approaching zero near release end-of-life; since updates are primarily bugfixes, fewer and fewer should be needed over time."
This is a major version update with several backwards-incompatible changes compared to the current version in F38, which is 21.0.0. Per the upstream changelog, since 21.0.0, the package has "Remove[d] support for SSLv2 and SSLv3", "The OpenSSL.crypto.X509StoreContextError exception has been refactored, changing its internal attributes", and "Removed X509StoreFlags.NOTIFY_POLICY" (as well as some new deprecations). These do not seem like changes that ought to go into a stable release without substantial justification; the justification for this update is only "it's a new version!" The "XXX is available" bugs are meant to prompt you to update the package in Rawhide (and maybe Branched), not in stable releases.
The current python-cryptography in F38 is 37.0.2; this update would require it to be bumped to at least 38, which would be another major version change.
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Broken dependencies
Same broken dependencies problem here:
This update has been obsoleted.