While looking into EPEL support for Openstack, we came across the issue
that EPEL ships with 1.2.7 and Openstack expects 1.3. Upon looking at
https://docs.djangoproject.com/en/1.3/releases/1.3/#backwards-incompatibl...
I see that one of the major differences is protection against XSRF.
This alone is sufficient reason to upgrade.
Installing an RPM from the Sourceforge site worked well with Openstack,
so it seems to fit our needs as well.
Are there any objections to upgrading EPEL's version of Django To the
latest?

Hi,
I'm trying to repackage a binary distribution of an application. The internal RPM dependency generator does pick up a few internal shared objects and adds them to 'Provides'; I don't like this provides in this specific case and would like to filter them out.
Currently this wiki page[1] only displays a method for perl; are there any other alternatives for example to filter provides (post-scan filtertering), for example a shared object in %{_libdir}/%{name} ?
[1] - http://fedoraproject.org/wiki/EPEL:Packaging#Perl_Provides_and_Requires_F...
Melhores cumprimentos,
Nelson M. Marques