> "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
Dear all,
You are kindly invited to the meeting:
EPEL Steering Co on 2018-10-24 from 17:00:00 to 18:00:00 GMT
At fedora-meet...@irc.freenode.net
The meeting will be about:
This is the weekly EPEL Steering Committee Meeting. Agenda is in the
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
>
> "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
On 10/23/18 10:30 AM, Neal Gompa wrote:
> 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
