Overview
Request 900810 accepted
- provide python3*dist(six): work around boo#1186870
- Created by bnavigator
- In state accepted
- Supersedes 900629
I have just written email how confused I am about this all stuff, but if we want to at least harmonize with other packages, then those provide:
~stitny$ rpm -qp --provides /var/tmp/build-root/openSUSE_Tumbleweed-x86_64/home/abuild/rpmbuild/RPMS/noarch/python39-crayons-0.4.0-0.noarch.rpm python3.9dist(crayons) = 0.4 python39-crayons = 0.4.0-0 python3dist(crayons) = 0.4 ~stitny$
This package seems to provide:
python3-six = 1.16.0-107.1 python3.8dist(six) = 1.16.0-107.1 python38-six = 1.16.0-107.1 python3dist(six) = 1.16.0-107.1
It seems to me that other package provide with python*dist macros only major.minor version, not inclduing the patch version and the release number.
Did I miss anything?
[ben@skylab:…nguages:python]% rpm -q --provides python38-pytest [1] python3-pytest = 6.2.4-1.2 python3.8dist(pytest) = 6.2.4 python38-pytest = 6.2.4-1.2 python3dist(pytest) = 6.2.4
According to the Fedora docs linked on the Github discussion, they remove the .0 from the version: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_automatically_generated_dependencies
Note that any .0 suffixes are removed from version numbers to match the behavior of Python tools. (PEP 440 specifies that X.Y and X.Y.0 are treated as equal.)
I don't think that it matters for rpm. But I can remove the %{release} if you insist.
I don’t want to be nitpicky about it, just when we do it, we should probably do it right.
Request History
bnavigator created request
- provide python3*dist(six): work around boo#1186870
mcepl accepted request
