[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-04-04 Thread Miro Hrončok
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

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-04-04 Thread Phil Wyett
-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 py

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-04-02 Thread Troy Dawson
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

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-03-13 Thread Orion Poplawski
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 nee

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-03-13 Thread Miro Hrončok
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 pyth

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-03-13 Thread Orion Poplawski
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 fil

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-03-13 Thread Orion Poplawski
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

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-03-13 Thread Orion Poplawski
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 fil

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-03-13 Thread Miro Hrončok
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

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-03-13 Thread Wart
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 pack