On 1 July 2018 at 18:43, Miro Hrončok <mhroncok(a)redhat.com> wrote:
On 1.7.2018 23:14, Stephen John Smoogen wrote:
>
> On 1 July 2018 at 15:38, Miro Hrončok <mhroncok(a)redhat.com> wrote:
>>
>> On 1.7.2018 21:03, Stephen John Smoogen wrote:
>>>
>>>
>>> Epylog is a python27 program and I have not had the time to convert it
>>> to python3 and won't until later this fall. As I don't want this to
be
>>> a FTBFS during rebuilds.. I see the following:
>>>
>>> 1. Retire it in rawhide
>>> 2. Make it a python27 module?
>>>
>>> I am looking for advise on which people would recommend.
>>> Thank you
>>
>>
>>
>> Why would it FTBFS?
>>
>
> Yeah.. sorry.. what is the term for "Is packaged up but needs a python
> which we deprecated/stopped supporting?"
Well so far the only thing that happens is that the current maintainers will
orphan the python2 package. What happens next is, well.. unknown yet.
Well I am not planning to orphan the package as it is needed in EPEL-7
for a while.
Looking into porting stuff to python3 is a good idea, however I
don't
understand what would be the benefit of putting python2 in a module.
Somebody would still need to maintain in.
I was mistaken and thought there was a short lived python27 module.
Since there isn't.. I will just retire in master.
--
Stephen J Smoogen.