On Thu, Apr 25, 2019 at 3:20 PM Miro Hrončok mhroncok@redhat.com wrote:
On 25. 04. 19 20:35, Stephen John Smoogen wrote:
> 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.]
mock in EPEL 6 is already "dead" in that matter:
https://bugzilla.redhat.com/show_bug.cgi?id=1694159
mock in EPEL 7 can run on Python 3.6:
Which could make sense, but makes mock more awkward to install. I recognize that it's not Fedora's task to be completely compatible with RHEL, but it's an important downstream community to keep in mind. It's already making some work I do with Samba to activate domain controller features a bit more awkward.