This is not defined until python3-devel is installed, so it has to be conditionally evaluated just like the previous python3_version example.
python3-devel
python3_version
ALso note that the comparison using python3_version does not work on EPEL 9 as well, and python3_version_nodots is required.
python3_version_nodots
Signed-off-by: Michel Alexandre Salim salimma@fedoraproject.org
@churchyard Not sure if you are still watching these; does this look OK to you?
For context, the EPEL 9 issue came up when working on a PR updating python-flit-core in EPEL 9:
https://src.fedoraproject.org/rpms/python-flit-core/pull-request/8#comment-148127
@churchyard commented pointing to an upstream RPM bug https://src.fedoraproject.org/rpms/python-flit-core/pull-request/8#comment-148677
rebased onto c009436ddd4b9a16dcf667cea7a95644db372bda
Hmm.
0%{?
310 > 38
As far as whether or not we say this is needed on EPEL 9: I am not sure. The given example works fine. RPM only breaks when the version thing is used in complex conditionals.
RPM only breaks when the version thing is used in complex conditionals.
This was finally reported to RHEL 9: https://issues.redhat.com/browse/RHEL-15688
Commit 4bae8db5 fixes this pull-request
Pull-Request has been merged by james
This is not defined until
python3-develis installed, so it has to beconditionally evaluated just like the previous
python3_versionexample.
ALso note that the comparison using
python3_versiondoes not work onEPEL 9 as well, and
python3_version_nodotsis required.Signed-off-by: Michel Alexandre Salim salimma@fedoraproject.org