On 11/10/20 8:21 PM, Miro Hrončok wrote:
On 11/10/20 6:22 PM, Mattia Verga via devel wrote:
Reading the python packaging guidelines [1] it says that "On releases
older than Fedora 33 [...] it is necessary to use %py_provides".
So I thought that %py_provides was necessary for EPEL7, but with that
macro set, the build fails with "Unknown tag: %py_provides
python3-calcephpy". In EPEL8 I get no errors and the build is completed.
Said that, should I use the old method ("Provides: python3-pkg_resources
= %{version}-%{release}") in EPEL7? Is it necessary?
Mattia
[1]
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_the_py_provides_macro
Hello. CCing the Python and EPEL lists.
You are correct. I can backport the macro to EPEL 7 if it makes your spec files
easier:
https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/26
Upgrade: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b03303e77c
Override: https://bodhi.fedoraproject.org/overrides/epel-rpm-macros-7-29
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
