[EPEL-devel] Re: EPEL: Python34 moving to Python36
On 04. 04. 19 10:08, Phil Wyett wrote: Hi, Just performed migration from 34 to 36. After yum update to pull all packages and install, I proceeded to install 36 packages to match my current 34 install before removing 34 packages. The only issue in the whole process was the one below that required python34-pylint be removed before installing the 36 version. [philwyett@ks-kenobi ~]$ sudo yum install python36-pylint [sudo] password for philwyett: Loaded plugins: langpacks, product-id, search-disabled-repos, subscription- : manager Resolving Dependencies - --> Running transaction check - ---> Package python36-pylint.noarch 0:1.6.5-5.el7 will be installed - --> Processing Dependency: python36-setuptools for package: python36-pylint- 1.6.5-5.el7.noarch - --> Running transaction check - ---> Package python36-setuptools.noarch 0:39.2.0-3.el7 will be installed - --> Finished Dependency Resolution Dependencies Resolved PackageArch Version Repository Size Installing: python36-pylintnoarch1.6.5-5.el7 epel437 k Installing for dependencies: python36-setuptoolsnoarch39.2.0-3.el7epel631 k Transaction Summary Install 1 Package (+1 Dependent package) Total download size: 1.0 M Installed size: 5.7 M Is this ok [y/d/N]: y Downloading packages: (1/2): python36-pylint-1.6.5-5.el7.noarch.rpm | 437 kB 00:01 (2/2): python36-setuptools-39.2.0-3.el7.noarch.rpm | 631 kB 00:01 - Total 591 kB/s | 1.0 MB 00:01 Running transaction check Running transaction test Transaction check error: file /usr/bin/epylint-3 from install of python36-pylint-1.6.5-5.el7.noarch conflicts with file from package python34-pylint-1.6.5-4.el7.noarch file /usr/bin/pylint-3 from install of python36-pylint-1.6.5-5.el7.noarch conflicts with file from package python34-pylint-1.6.5-4.el7.noarch file /usr/bin/pyreverse-3 from install of python36-pylint-1.6.5-5.el7.noarch conflicts with file from package python34-pylint-1.6.5-4.el7.noarch file /usr/bin/symilar-3 from install of python36-pylint-1.6.5-5.el7.noarch conflicts with file from package python34-pylint-1.6.5-4.el7.noarch file /usr/share/man/man1/epylint-3.1.gz from install of python36-pylint-1.6.5- 5.el7.noarch conflicts with file from package python34-pylint-1.6.5-4.el7.noarch file /usr/share/man/man1/pylint-3.1.gz from install of python36-pylint-1.6.5- 5.el7.noarch conflicts with file from package python34-pylint-1.6.5-4.el7.noarch file /usr/share/man/man1/pylint-gui-3.1.gz from install of python36-pylint- 1.6.5-5.el7.noarch conflicts with file from package python34-pylint-1.6.5- 4.el7.noarch file /usr/share/man/man1/pyreverse-3.1.gz from install of python36-pylint- 1.6.5-5.el7.noarch conflicts with file from package python34-pylint-1.6.5- 4.el7.noarch file /usr/share/man/man1/symilar-3.1.gz from install of python36-pylint-1.6.5- 5.el7.noarch conflicts with file from package python34-pylint-1.6.5-4.el7.noarch Thanks for the report. A fix: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f076346dfb -- 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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 2019-04-02 at 07:18 -0700, Troy Dawson wrote: > On Wed, Mar 13, 2019 at 7:31 AM Stephen John Smoogen wrote: > > > > Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George, > > and several helpers have gotten nearly all of the python34 packages > > moves over to python36 in EPEL-7. They are being included in 6 Bodhi > > pushes because of a limitation in Bodhi for the text size of packages > > in an include. > > > > The current day for these package groups to move into EPEL regular is > > April 2nd. We would like to have all tests we find in the next week or > > so also added so that the updates can occur in a large group without > > too much breakage. > > > > > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581 > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d62608bce > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5be892b745 > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0f4cca7837 > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ed3564d906 > > > > Please heavily test them by doing the following: > > Stage 1 Testing > > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > > Install or enable the EPEL repository for this system > > Install various packages you would normally use > > yum --enablerepo=epel-testing update > > Report problems to epel-devel@lists.fedoraproject.org > > Stage 2 Testing > > Check for any updated testing instructions on this blog or EPEL-devel list. > > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > > Install or enable the EPEL repository for this system > > yum install python34 > > yum --enablerepo=epel-testing update > > Report problems to epel-devel@lists.fedoraproject.org > > Stage 3 Testing > > Check for any updated testing instructions on this blog or EPEL-devel list. > > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > > Install or enable the EPEL repository for this system > > yum install python36 > > yum --enablerepo=epel-testing update > > Report problems to epel-devel@lists.fedoraproject.org > > This should cover the three most common scenarios. Other scenarios > > exist and will require some sort of intervention to work around. We > > will outline them as they come up. > > > > Many Many Thanks go to Troy, Jeroen, Carl, and the many people on the > > python team who made a copr and did many of the initial patches to > > make this possible. > > -- > > Stephen J Smoogen > > Thank you to everyone for all the feedback, testing, fixes and discussion. > I believe all of the blocking problems have been worked out and that > we are ready to push these to stable. > > I will be doing the push to stable in 4 hours. > If you have something you think is a blocker, please let me know before then. > > We have found that there were some packages left off the list of > packages to rebuild. This is not a blocker, but please let me know > and I will get them rebuilt and they will have their own smaller bodhi > update. > > Troy Dawson > ___ > 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 Hi, Just performed migration from 34 to 36. After yum update to pull all packages and install, I proceeded to install 36 packages to match my current 34 install before removing 34 packages. The only issue in the whole process was the one below that required python34-pylint be removed before installing the 36 version. [philwyett@ks-kenobi ~]$ sudo yum install python36-pylint [sudo] password for philwyett: Loaded plugins: langpacks, product-id, search-disabled-repos, subscription- : manager Resolving Dependencies - --> Running transaction check - ---> Package python36-pylint.noarch 0:1.6.5-5.el7 will be installed - --> Processing Dependency: python36-setuptools for package: python36-pylint- 1.6.5-5.el7.noarch - --> Running transaction check - ---> Package python36-setuptools.noarch 0:39.2.0-3.el7 will be installed - --> Finished Dependency Resolution Dependencies Resolved PackageArch Version Repository Size Installing: python36-pylintnoarch1.6.5-5.el7 epel437 k Installing for dependencies: python36-setuptoolsnoarch39.2.0-3.el7epel631 k Transaction Summary ==
[EPEL-devel] Re: EPEL: Python34 moving to Python36
On Wed, Mar 13, 2019 at 7:31 AM Stephen John Smoogen wrote: > > Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George, > and several helpers have gotten nearly all of the python34 packages > moves over to python36 in EPEL-7. They are being included in 6 Bodhi > pushes because of a limitation in Bodhi for the text size of packages > in an include. > > The current day for these package groups to move into EPEL regular is > April 2nd. We would like to have all tests we find in the next week or > so also added so that the updates can occur in a large group without > too much breakage. > > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d62608bce > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5be892b745 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0f4cca7837 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ed3564d906 > > Please heavily test them by doing the following: > Stage 1 Testing > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > Install various packages you would normally use > yum --enablerepo=epel-testing update > Report problems to epel-devel@lists.fedoraproject.org > Stage 2 Testing > Check for any updated testing instructions on this blog or EPEL-devel list. > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > yum install python34 > yum --enablerepo=epel-testing update > Report problems to epel-devel@lists.fedoraproject.org > Stage 3 Testing > Check for any updated testing instructions on this blog or EPEL-devel list. > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > yum install python36 > yum --enablerepo=epel-testing update > Report problems to epel-devel@lists.fedoraproject.org > This should cover the three most common scenarios. Other scenarios > exist and will require some sort of intervention to work around. We > will outline them as they come up. > > Many Many Thanks go to Troy, Jeroen, Carl, and the many people on the > python team who made a copr and did many of the initial patches to > make this possible. > -- > Stephen J Smoogen Thank you to everyone for all the feedback, testing, fixes and discussion. I believe all of the blocking problems have been worked out and that we are ready to push these to stable. I will be doing the push to stable in 4 hours. If you have something you think is a blocker, please let me know before then. We have found that there were some packages left off the list of packages to rebuild. This is not a blocker, but please let me know and I will get them rebuilt and they will have their own smaller bodhi update. Troy Dawson ___ 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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
On 3/13/19 9:05 PM, Chris wrote: Amazing work! I just wanted to ask if it was a bug that the Python v2 branch provided the following RPMs, but the Python v3.6 did not: - python36-requests-oauthlib - python36-oauthlib The above python2 packages are in RHEL7, so new python3- packages will need to be created in Fedora for EPEL7. - python36-markdown - python36-pytest-runner These are now in epel-testing. Buildroot overrides would need to be created for them for them to be in the buildroot. Perhaps these ones just haven't been ported over yet? Thoughts? Here's the source of my prob: https://koji.fedoraproject.org/koji/taskinfo?taskID=33463886 Chris -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ ___ 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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
On 14. 03. 19 0:53, Orion Poplawski wrote: On 3/13/19 11:48 AM, Miro Hrončok wrote: On 13. 03. 19 18:42, Wart wrote: Transaction check error: file /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info from install of python34-six-1.11.0-2.el7.noarch conflicts with file from package python34-six-1.11.0-1.el7.noarch IS that a file to directory problem? Otherwise python34-six-1.11.0-2.el7.noarch should just replace python34-six-1.11.0-1.el7.noarch "naturally" without any specific conflict. I think I figured this out. During the install step if we didn't have a tests_require package installed we got: running install_egg_info Writing /builddir/build/BUILDROOT/python3-six-1.11.0-2.el7.noarch/usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info BUILDSTDERR: /usr/lib64/python3.4/distutils/dist.py:260: UserWarning: Unknown distribution option: 'tests_require' BUILDSTDERR: warnings.warn(msg) and ended up with a file egg-info instead of a directory. I've rebuilt python3-six with the test requirements installed for both versions now. I'll add python3-six-1.11.0-3.el7.src.rpm to the update. Thanks. -- 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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
On 3/13/19 11:48 AM, Miro Hrončok wrote: On 13. 03. 19 18:42, Wart wrote: Transaction check error: file /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info from install of python34-six-1.11.0-2.el7.noarch conflicts with file from package python34-six-1.11.0-1.el7.noarch IS that a file to directory problem? Otherwise python34-six-1.11.0-2.el7.noarch should just replace python34-six-1.11.0-1.el7.noarch "naturally" without any specific conflict. I think I figured this out. During the install step if we didn't have a tests_require package installed we got: running install_egg_info Writing /builddir/build/BUILDROOT/python3-six-1.11.0-2.el7.noarch/usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info BUILDSTDERR: /usr/lib64/python3.4/distutils/dist.py:260: UserWarning: Unknown distribution option: 'tests_require' BUILDSTDERR: warnings.warn(msg) and ended up with a file egg-info instead of a directory. I've rebuilt python3-six with the test requirements installed for both versions now. I'll add python3-six-1.11.0-3.el7.src.rpm to the update. -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ ___ 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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
On 3/13/19 9:46 AM, Dridi Boukelmoune wrote:
Hello,
On Wed, Mar 13, 2019 at 3:37 PM Stephen John Smoogen wrote:
Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George,
and several helpers have gotten nearly all of the python34 packages
moves over to python36 in EPEL-7. They are being included in 6 Bodhi
pushes because of a limitation in Bodhi for the text size of packages
in an include.
I was about to start a thread about this, so it saves me a fair amount of time.
I have been working on this today, so this is very fresh:
https://github.com/varnishcache/pkg-varnish-cache/pull/124
My complaint is that the current packages for
python34-{sphinx,docutils} don't seem to have provides with a
"python3-" prefix. So while I can live with that fact, I'm not happy
with the prospect of having to break the continuity soon and have to
move my BuildRequires to a python36- prefix.
That's a reasonable suggestion. I would suggest you file an RFE request
again python-rpm-macros in EPEL to have the %python_provide macro
produce a Provides: python3-%{name} for the "active" python3 version.
One more thing about those two specific packages, they also don't
provide binaries suffixed with "-3" so that means having to change
packaging again so that configures picks up rst2man-3.6 instead of
rst2man-3.4 and that's not a comfortable place to be in downstream.
The python3{4,6}-sphinx packages do provide /usr/bin/sphinx-build-3,
etc. In fact one reason why you currently cannot install both.
As for docutils, file a bug against python3-docutils in EPEL and we'll
get that fixed up.
The current day for these package groups to move into EPEL regular is
April 2nd. We would like to have all tests we find in the next week or
so also added so that the updates can occur in a large group without
too much breakage.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581
I'm a bit confused because it seems the update above contains both
builds for the packages I'm interested in, and seems to keep building
the 3.4 variant of the package in addition to the new 3.6 builds.
That means I should not worry about having to move away from today's
work, right?
Most EPEL python3 package will build for both python3 versions. We are
not (yet) dropping python34. It's just that the default
/usr/bin/python3 is switching to python 3.6, and packages that only
build for one python3 version are now shipping for 3.6.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
___
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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
On 3/13/19 11:48 AM, Miro Hrončok wrote: On 13. 03. 19 18:42, Wart wrote: Transaction check error: file /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info from install of python34-six-1.11.0-2.el7.noarch conflicts with file from package python34-six-1.11.0-1.el7.noarch IS that a file to directory problem? Otherwise python34-six-1.11.0-2.el7.noarch should just replace python34-six-1.11.0-1.el7.noarch "naturally" without any specific conflict. It appears to be a directory -> file problem. Why did this change? # ls -l /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info total 16 -rw-r--r--. 1 root root1 Sep 28 12:18 dependency_links.txt -rw-r--r--. 1 root root 1818 Sep 28 12:18 PKG-INFO -rw-r--r--. 1 root root 253 Sep 28 12:18 SOURCES.txt -rw-r--r--. 1 root root4 Sep 28 12:18 top_level.txt # repoquery --enablerepo=epel-testing -l python34-six-1.11.0-2.el7.noarch | grep egg /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ ___ 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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
On 13. 03. 19 18:42, Wart wrote: Transaction check error: file /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info from install of python34-six-1.11.0-2.el7.noarch conflicts with file from package python34-six-1.11.0-1.el7.noarch IS that a file to directory problem? Otherwise python34-six-1.11.0-2.el7.noarch should just replace python34-six-1.11.0-1.el7.noarch "naturally" without any specific conflict. -- 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
[EPEL-devel] Re: EPEL: Python34 moving to Python36
Attempts to upgrade python34-six fail with an unexpected file conflict. I didn't see any Conflicts: or Obsoletes: tags in the spec file, so I'm not sure where this conflict is coming from. # yum --enablerepo epel-testing-upstream upgrade python34-six Loaded plugins: langpacks, priorities 164 packages excluded due to repository priority protections Resolving Dependencies --> Running transaction check ---> Package python34-six.noarch 0:1.11.0-1.el7 will be updated ---> Package python34-six.noarch 0:1.11.0-2.el7 will be an update --> Finished Dependency Resolution Dependencies Resolved Package Arch VersionRepository Size Updating: python34-six noarch 1.11.0-2.el7 epel-testing-upstream 32 k Transaction Summary Upgrade 1 Package Total download size: 32 k Is this ok [y/d/N]: y Downloading packages: python34-six-1.11.0-2.el7.noarch.rpm | 32 kB 00:00 Running transaction check Running transaction test Transaction check error: file /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info from install of python34-six-1.11.0-2.el7.noarch conflicts with file from package python34-six-1.11.0-1.el7.noarch --Wart On 3/13/19 9:30 AM, Stephen John Smoogen wrote: > Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George, > and several helpers have gotten nearly all of the python34 packages > moves over to python36 in EPEL-7. They are being included in 6 Bodhi > pushes because of a limitation in Bodhi for the text size of packages > in an include. > > The current day for these package groups to move into EPEL regular is > April 2nd. We would like to have all tests we find in the next week or > so also added so that the updates can occur in a large group without > too much breakage. > > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d62608bce > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5be892b745 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0f4cca7837 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ed3564d906 > > Please heavily test them by doing the following: > Stage 1 Testing > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > Install various packages you would normally use > yum --enablerepo=epel-testing update > Report problems to epel-devel@lists.fedoraproject.org > Stage 2 Testing > Check for any updated testing instructions on this blog or EPEL-devel list. > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > yum install python34 > yum --enablerepo=epel-testing update > Report problems to epel-devel@lists.fedoraproject.org > Stage 3 Testing > Check for any updated testing instructions on this blog or EPEL-devel list. > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > yum install python36 > yum --enablerepo=epel-testing update > Report problems to epel-devel@lists.fedoraproject.org > This should cover the three most common scenarios. Other scenarios > exist and will require some sort of intervention to work around. We > will outline them as they come up. > > Many Many Thanks go to Troy, Jeroen, Carl, and the many people on the > python team who made a copr and did many of the initial patches to > make this possible. > ___ 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
