Hey,
when RHEL 7.7 will be released, the following new components/packages will be provided (assuming from 7.7 beta):
python3 - the Python 3.6 package ================================
This new RHEL7 component builds several subpackages, all obsoleting the subpackages of epel7 python36 package. We will simply retire python36 from epel7.
python-rpm-macros =================
This new RHEL7 component is a drop-in replacement of python-rpm-macros from epel7, we will simply retire the package. python-epel-rpm-macros already provide the necessary macros for python34 in epel7.
python3-setuptools ==================
This new RHEL7 component produces the python3-setuptools package that obsoletes the python36-setuptools package (built from the python3-setuptools epel7 component).
We cannot simply retire python3-setuptools from epel7, as it also builds python34-setuptools in epel7 and there is no replacement for that in RHEL7.
Easiest thing would be to stop building python36-setuptools and only keep python34-setuptools in epel7, however IIRC we cannot have the same component name as in RHEL. If that is indeed the case, python3-setuptools needs to be retired and a new python34-setuptools component needs to be created in epel7. Is my assumption correct?
python-pip ==========
This new RHEL7 component produces the python3-pip package that obsoletes the python36-pip package (built from the python-pip epel7 component).
The python-pip epel7 component also produces python34-pip and python2-pip (neither available in RHEL 7.7).
If my previous assumption about components with RHEL names is correct, we need 1 or 2 new components for python34-pip and python2-pip - either we have each in a separate component or we create a new component that builds both (called python-pip-epel maybe?).
python-wheel ============
This new RHEL7 component produces the python3-wheel package.
The python-wheel epel7 component produced python-wheel package (Python 2).
The epel7 package was adapted to produce python2-wheel and python36-wheel, however there was no successful build of this in epel7.
If my previous assumption about components with RHEL names is correct, we need to add a new python2-wheel component to epel7.
------------
Are my assumptions correct?
If we indeed need new packages/components, I can help to create them, but I do not intent to maintain them. Any takers?
Hello.
On 7/17/19 12:00 AM, Miro Hrončok wrote:
Hey,
when RHEL 7.7 will be released, the following new components/packages will be provided (assuming from 7.7 beta):
python3 - the Python 3.6 package
This new RHEL7 component builds several subpackages, all obsoleting the subpackages of epel7 python36 package. We will simply retire python36 from epel7.
python-rpm-macros
This new RHEL7 component is a drop-in replacement of python-rpm-macros from epel7, we will simply retire the package. python-epel-rpm-macros already provide the necessary macros for python34 in epel7.
python3-setuptools
This new RHEL7 component produces the python3-setuptools package that obsoletes the python36-setuptools package (built from the python3-setuptools epel7 component).
We cannot simply retire python3-setuptools from epel7, as it also builds python34-setuptools in epel7 and there is no replacement for that in RHEL7.
Easiest thing would be to stop building python36-setuptools and only keep python34-setuptools in epel7, however IIRC we cannot have the same component name as in RHEL. If that is indeed the case, python3-setuptools needs to be retired and a new python34-setuptools component needs to be created in epel7. Is my assumption correct?
python-pip
This new RHEL7 component produces the python3-pip package that obsoletes the python36-pip package (built from the python-pip epel7 component).
The python-pip epel7 component also produces python34-pip and python2-pip (neither available in RHEL 7.7).
If my previous assumption about components with RHEL names is correct, we need 1 or 2 new components for python34-pip and python2-pip - either we have each in a separate component or we create a new component that builds both (called python-pip-epel maybe?).
python-wheel
This new RHEL7 component produces the python3-wheel package.
The python-wheel epel7 component produced python-wheel package (Python 2).
The epel7 package was adapted to produce python2-wheel and python36-wheel, however there was no successful build of this in epel7.
If my previous assumption about components with RHEL names is correct, we need to add a new python2-wheel component to epel7.
Are my assumptions correct?
If we indeed need new packages/components, I can help to create them, but I do not intent to maintain them. Any takers?
If none else raise their hand, I can help maintain these packages.
Lumír
"MH" == Miro Hrončok mhroncok@redhat.com writes:
MH> Are my assumptions correct?
Yes, unless some major changes happened of which I was not aware, you cannot have any package name in EPEL7 (including a source package) which duplicates a package name in RHEL7 _on a particular architecture_. (There are limited-arch packages as described at https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages).
In the cases you mention, I do believe you would need new source package repositories to avoid the conflict. Note that creating these does not require a package review as long as they are named properly.
- J<
python-devel@lists.fedoraproject.org
-
Jason L Tibbitts III -
Lumir Balhar -
Miro Hrončok