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.
On Wed, Apr 24, 2019 at 6:23 AM Miro Hrončok mhroncok@redhat.com 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.
That would actually be great, since it simplifies how people can use it.
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.
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
On 30. 04. 19 10:50, Miro Hrončok wrote:
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
Note that it currently only works for Python 3 only SRPMS as python-devel from RHEL7 overrides the macro with its original version. We plan to change the macro on RHEL7 side as well, but (business as usual) we cannot do it right away.
python-devel@lists.fedoraproject.org
-
Miro Hrončok -
Neal Gompa