Hide Forgot
Description of problem: Please update Mock in EPEL5 to mock-1.2.17-1. Mock available in EPEL5 (mock-1.0.37-1.el5) is out of date compared to Mock from upstream. EPEL6 and EPEL7 currently ship mock-1.2.17-1. I've asked the upstream Mock project to publish that version to EPEL5, but they said it's up to you folks. Version-Release number of selected component (if applicable): Currently: mock-1.0.37-1.el5 Requesting: mock-1.2.17-1 (same as el5 and el6)
Who told you that it is possible to publish current version to EPEL5? It is not technically possible. On EPEL5 there is python2.4, which is soooo old. Current code is targeting python3. We still try to be compatible with python2, but only with 2.7. Being compatible with python2.4 will be so hard, that it is not worth the work. Sorry.
EPEL5 ships python26, which is the same major version as EL6. EL6 ships Mock 1.2.17-1, which is the same version EL7 does, so that version should at least work with Python 2.6. Is there a reason Mock is tied to Python 2.4 and cannot use the EPEL5-provided 2.6? I see Mock 1.2 also requires a newer automake than EL5 has, sadly. Sorry, I misspoke about what upstream said, and confused Mock with Koji. I'll file a separate request for that.
> Is there a reason Mock is tied to Python 2.4 and cannot use the EPEL5-provided 2.6? Mainly rpm-python which mock use (and it was missing in spec file - I just added it now) It is not available under python2.6 in EPEL5. I really do not think it is wise to spend development cycles on platform which will be EOLed in 11 months. You should really move to EL7. You can still build packages for EL5 there.