Bug 848733 - Update Django to 1.4.1 on el6
Summary: Update Django to 1.4.1 on el6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: Django
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Runge
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 864481
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-16 10:14 UTC by Massimo Paladin
Modified: 2012-11-06 11:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-06 11:31:41 UTC
Type: Bug


Attachments (Terms of Use)

Description Massimo Paladin 2012-08-16 10:14:19 UTC
Hello,

could Django be updated to 1.4.1 on el6?

Is there any problem blocking the update?

Cheers,
-Massimo

Comment 1 Matthias Runge 2012-08-22 18:50:58 UTC
As much as I can understand your wish to update, there are some reasons not to do so:
From django-1.2 to django 1.3 some instructions and features were deprecated, but still worked in 1.3. They have been removed in django-1.4
I currently know at least two applications, which still don't support django-1,4, both used also at fedora infrastructure. Further more, django developer discontinued support for older python-versions. (imho, for django-1.4 is python 2.5 is required.)

EL6 should be a stable distribution. Details regarding updates may be found here:
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#A_major_version_update

One solution is to create a dedicate django-1.4 package for epel6. Currently, I'm not really decided, what to do.

Comment 2 Matthias Runge 2012-10-10 08:06:06 UTC
OK, I can't update, there are too many blockers. 

So, I created a new request for review for a dedicated Django14 package for EPEL6.

Comment 3 Massimo Paladin 2012-10-10 08:48:56 UTC
Ok, thank you very much.

Comment 4 Matthias Runge 2012-10-10 08:54:18 UTC
Massimo, are you interested in doing a review? Basically, this is derived from the other two (python-)Django packages. So nothing really serious. I'd even trade...

Comment 5 Massimo Paladin 2012-10-10 15:58:52 UTC
Matthias, I can review it, just leave me a couple of days.

You don't need to review one of mine but in case you have spare time I've got one waiting (very basic one), actually someone assigned it to himself but didn't do anything so far: 853124.

Comment 6 Matthias Runge 2012-11-06 11:31:41 UTC
since Django14 hit epel6 stable, I'll close this ticket.


Note You need to log in before you can comment on or make changes to this bug.