Bug 662758
| Summary: | RFE: Add a python26-Django package to EPEL5 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Steve Traylen <steve.traylen> |
| Component: | Django | Assignee: | Steve Milner <smilner> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | el5 | CC: | dmalcolm, jflowers, michel, smilner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-03 12:51:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 573151, 662750 | ||
| Bug Blocks: | |||
|
Description
Steve Traylen
2010-12-13 19:37:46 UTC
Hey Steve, EPEL5 uses Python2.5 if I remember correctly. I'm not sure that a 2.6 specific package would be OK within EPEL5 itself. Are you looking to get a later version of Django in EPEL5 or do you need Python2.6 specifically? RHEL5 contains python2.4 EPEL5 contains a parallel installable python26 package. Yes I want Django as python26-Django package. There are now plenty of python26-* packages in EPEL5 python26.x86_64 2.6.5-5.el5 installed python26-devel.x86_64 2.6.5-5.el5 installed python26-distribute.noarch 0.6.10-4.el5 installed python26-libs.x86_64 2.6.5-5.el5 installed python26-tools.x86_64 2.6.5-5.el5 installed python26-PyXML.x86_64 0.8.4-23.el5 epel python26-devel.i386 2.6.5-5.el5 epel python26-dirq.noarch 0.0.5-3.el5.1 epel python26-dns.noarch 1.9.2-2.el5 epel python26-gdata.noarch 2.0.11-2.el5 epel python26-greenlet.x86_64 0.3.1-3.el5 epel python26-greenlet-devel.i386 0.3.1-3.el5 epel python26-greenlet-devel.x86_64 0.3.1-3.el5 epel python26-libs.i386 2.6.5-5.el5 epel python26-mod_python.x86_64 3.3.1-13.el5 epel python26-mod_wsgi.x86_64 3.3-1.el5 epel python26-nose.noarch 0.11.1-3.el5 epel python26-pbs.x86_64 4.3.0-5.el5 epel python26-simplejson.x86_64 2.1.1-1.el5 epel python26-sqlalchemy.noarch 0.6.4-1.el5 epel python26-test.x86_64 2.6.5-5.el5 epel and it is acceptable to add Django.... of course once all the dependencies are in place. Once they are I will return to this bug and try to provide a python26-Django .spec file suitable for EPEL5. Steve. OK, that works. Thank you very much Steve! Another issue on EPEL5 is that Django 1.1.x is no longer supported by upstream, and given that they just issued security updates for 1.2.x and 1.3.x, I wonder if it's time to get the EPEL5 package in sync with EPEL6. Steve (Milner), thoughts? note: there is no need to depend on python26-sphinx; sphinx is invoked as a binary, so you can just use python-sphinx10 instead. Is there any update on this issue, or an expected completion date. Thank you EPEL 5 only. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |