| Summary: | Update Mock for EPEL5 to mock-1.2.17-1 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Shatil Rafiullah <abd4arraafi> |
| Component: | mock | Assignee: | Miroslav Suchý <msuchy> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | el5 | CC: | jdisnard, mebrown, msimacek, msuchy, praiskup, williams |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-13 08:25:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Shatil Rafiullah
2016-04-12 21:01:30 UTC
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.
|