On 18. 11. 18 1:21, Orion Poplawski wrote:
On 11/15/18 10:08 AM, Stephen John Smoogen wrote:
> I missed this in the last meeting from items that needed to be voted on.
> The changes would be to make epel macros to have
> %python3_pkgversion 36
> %python3_other_pkgversion 34
> This should allow for the build system to rebuild python3 items as
> default. Then we will need a tracking ticket and bump/rebuild the
Be aware that this will cause many current python34-* packages to disappear the
next time they are rebuilt for EPEL7.
This was the plan from the beginning and as long as we inform all the interested
parties (read: maintainers of such packages, users), we shall be good.
EPEL "officials" need to decide whether to do it now, or align the change with
the next RHEL 7.x release. As a Python Maintainer in Fedora and RHEL, I can say
that we would very much like to see this happen and preferably sooner than later
. We would like to add Python 3.6 to RHEL 7, but at this point we cannot make
any promises. If we add it, it will most likely own /usr/bin/python3 and
%__python3 will in all likelihood point to 3.6. We want to avoid as much
breakage in EPEL as possible.
* We change macros.python3  to 3.6.
* We change macros.python3_other  to 3.4.
* We rename the package to python-rpm-epel-macros (or whatever is the name
convention) and the subpackages to python-srpm-epel-macros etc. In case
python-rpm-macros comes to RHEL proper. Once (if) it does, we remove
macros.python3 from the EPEL package.
* We put this to all the announcement channels EPEL has.
Caveat: If a packager needs to rebuild their package without changing the Python
version, they need to invert the macros. This information needs to be part of