On Thu, 25 Apr 2019 at 13:35, Miro Hrončok <mhroncok@redhat.com> wrote:
On 25. 04. 19 18:38, Nico Kadel-Garcia wrote:
> On Thu, Apr 25, 2019 at 10:27 AM Miro Hrončok <mhroncok@redhat.com> wrote:
>>
>> On 25. 04. 19 9:22, Miroslav Suchý wrote:
>>> Dne 24. 04. 19 v 23:04 Ben Cotton napsal(a):
>>>> Removed packages that would block the upgrades to Fedora 32 will be
>>>> obsoleted from {{package|fedora-obsolete-packages}}.
>>>
>>> Which effectively means all python2-* packages. Right?
>>
>> Almost. The ones that stop requiring the automatic provides and get FESCo
>> exception to use python27 won't be obsoleted.
>>
>> Note that only "problematic on upgrade" packages should be obsoleted, but
>> anything that would require python(abi) = 2.7 or similar jumps to this category,
>> so yes, probably all of them.
>>
>> (I've previously forgot to reply to the list.)
>
> How much is going to be needed for "mock" to still work for older
> operating systems?

I'm confused. How is the change relevant for mock? I think I'm missing some
pieces of the thought process here, could you please elaborate on that?



In the past, changes where old versions of python were no longer supported in Fedora, then newer versions of mock/etc became dead in older OS's like RHEL-5's python24 and RHEL-6's python26. This would make compiling packages for certain versions of the OS impossible because the parent operating system didn't have a version of python it could use and you couldn't use newer source code on the older os.

The question is moot because you are the wrong person to ask. The person to ask is the owner of mock and I expect the answer will be... I don't have time to support N versions of python but you have the source code.. so do it yourself. [Probably nicer than that.. but the general effect.] 


--
Stephen J Smoogen.