On 04. 11. 21 12:49, Miro Hrončok wrote:
After some recent improvements in the Python RPM dependency generators,
a regression was discovered .
Turns out the error happened when the upstream metadata contained a
requirement with a PEP 440  incompatible version. A fix is pending
and only one package in Fedora was affected.
- there might be cases where legacy versions are needed
- but in most cases, they should be avoided
Hence, I propose we do the following in Rawhide:
We turn LegacyVersions to failures, but we provide a stop-gap measure,
such as (%global python_dependency_allow_legacy_version_provides 1 /
%global python_dependency_allow_legacy_version_requires 1 ) for packages
that need to override this. When pypa/packaging actually drops
LegacyVersion, this stop-gap measure will no longer work.
I suggest removing LegacyVersion support without replacement. I think
neither creating nor using
"python_dependency_allow_legacy_version_requires" would be worth the
All the uses of it that we've seen were mistakes, and since upstream
tools are removing support for it, the stop-gap is just delaying the
If we find an actual use case for it, it can always be added.