python-django update to Django-1.6
mrunge at matthias-runge.de
Tue Nov 26 11:02:37 UTC 2013
On 11/25/2013 06:51 PM, Simo Sorce wrote:
> On Mon, 2013-11-25 at 11:24 -0500, Stephen Gallagher wrote:
>> This is kind of why I keep coming back to: "Why do we have
>> python-django at all?" I don't really see any reason why we shouldn't
>> kill off the python-django package and just carry 'python-django15'
>> and 'python-django16' packages with a conflict.
>> The number of incompatibilities between releases is such that I don't
>> think we really want to be forcing upgrades on other packages at all.
>> We should just be carrying whichever two versions are supported by
>> upstream at any given time. Upstream is very good about maintaining
>> bugfixes and security fixes in both supported streams.
> +1 by changing version the current way, the only ting we can guarantee
> is a lot of broken packages all the time.
I see your points here and thank you for the feedback!
>From my experience, it was just a pain to have python-django14 and
python-django. Introducing one or two other packages python-django15
and python-django16 will make it more difficult for users to update
django. How should packages require Django? Just require python-django?
Sadly, yum can not handle that properly.
When dropping python-django as provides/requires, we'd have the
situation packages will require a specific version. That's rather
unfortunate, because combination of packages requiring some other
python-django-foo package might require a different django version.
At least for OpenStack Horizon I can say, we're up to fix compatibility
issues with Django-1.6 upstream.
More information about the devel