Re: [EPEL-devel] Moving EPEL7 to python3.6

2018-10-23 Thread Jason L Tibbitts III
> "NG" == Neal Gompa writes: NG> Wait, we can do that? I thought we couldn't use the exception NG> process for this? Well, the idea is that you don't need a separate review just to import a different version of the same package. So foo and foo1.2 (the 1.2 version) or python-abc and

Re: [EPEL-devel] Moving EPEL7 to python3.6

2018-10-23 Thread Neal Gompa
On Tue, Oct 23, 2018 at 1:28 PM Jason L Tibbitts III wrote: > > > "OP" == Orion Poplawski writes: > > OP> - Can we make epel7-py36 branches, and somehow have > OP> %python3_version, et. al. be 3.6 for those builds? > > I can't think of any way to do that without extra magic. And if you >

Re: [EPEL-devel] Moving EPEL7 to python3.6

2018-10-23 Thread Jason L Tibbitts III
> "OP" == Orion Poplawski writes: OP> - Can we make epel7-py36 branches, and somehow have OP> %python3_version, et. al. be 3.6 for those builds? I can't think of any way to do that without extra magic. And if you require something in the spec, you might as well just hardcode it. OP> - Can

Re: [EPEL-devel] Moving EPEL7 to python3.6

2018-10-22 Thread Orion Poplawski
On 10/19/2018 01:22 PM, Stephen John Smoogen wrote: Hi, EPEL is a set of packages which work for CentOS and RHEL versions 6 and 7. In the version 7, we are currently using python34 and would like to move this to python36. In doing so, we need help in both our packaging rules and in updating a