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 packages
-- Stephen J Smoogen.
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 packages
Be aware that this will cause many current python34-* packages to disappear the next time they are rebuilt for EPEL7.
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 packages
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.
Proposal:
* We change macros.python3 [1] to 3.6. * We change macros.python3_other [2] 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 the announcement.
[1] https://src.fedoraproject.org/rpms/python-rpm-macros/blob/epel7/f/macros.pyt... [2] https://src.fedoraproject.org/rpms/python-rpm-macros/blob/epel7/f/macros.pyt...
On Tue, 22 Jan 2019 at 15:06, Miro Hrončok mhroncok@redhat.com wrote:
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 packages
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.
I would like to work with you this week if you are in Brno. I am wanting to see if we can do this first in a copr to show what will happen and then put in a flag day for it before that possible problem occurs.
Proposal:
- We change macros.python3 [1] to 3.6.
- We change macros.python3_other [2] 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 the announcement.
[1] https://src.fedoraproject.org/rpms/python-rpm-macros/blob/epel7/f/macros.pyt... [2]
https://src.fedoraproject.org/rpms/python-rpm-macros/blob/epel7/f/macros.pyt...
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@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...
epel-devel@lists.fedoraproject.org
-
Miro Hrončok -
Orion Poplawski -
Stephen John Smoogen