On 25. 04. 19 16:43, Miro Hrončok wrote:
On 24. 04. 19 12:23, Miro Hrončok wrote:
Hey,
since the plan is to have some python3-... packages in RHEL proper, should we
adapt the %python_provide macro to provide python3-... when it gets python36-...?
%{python_provide python36-foo} currently does nothing.
I propose to change it to do: Provides: python3-foo = %{version}-%{release}.
Note: %{python_provide python2-foo} currently adds obsoletes, let's not add
them for the python36 case (there is nothing to obsolete here, quite the
opossite - python3-foo from RHEL would in theory obsolete python36-foo from
EPEL).
Arguably, this discussion should have happened before we did the mass rebuild
for 3.4 -> 3.6 transition, however I don't consider such provides essential.
The idea is to change the macro, but don't mass rebuild - instead start
providing the provides gradually.
Note that not all EPEL7 Python 3 packages use this macro, but many do.
A PR is here:
https://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/18
I'd appreciate feedback from EPEL packagers.
Update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dad4eed6b7
Override: https://bodhi.fedoraproject.org/overrides/python-rpm-macros-3-24.el7
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
