Bug 1287271
Summary: | Add the package to EPEL7 repos | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | fedora.dm0 |
Component: | python-django-debug-toolbar | Assignee: | Matthias Runge <mrunge> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | bkabrda, mrunge |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-02 11:53:04 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: | |
Embargoed: |
Description
fedora.dm0
2015-12-01 21:05:39 UTC
Oh yes, good catch! that if is wrong in spec. I'd fix that as soon as I can. I'm a bit hesitant to add this to epel7, in fact, it should be deprecated in epel6, since there is no supported Django version in epel6. The main reason is, django is a moving target, and it's moving a bit too fast for a long term supported release like RHEL For example, we currently can not upgrade from django-1.6 in epel7 to the recent long term supported version django-1.8, since we'd break current installations and a few packages in epel7. |