Actually, there would likely be a need for further changes as the django dependency of the binary packages is specified explicitly in debian/control so also needs an update to 1.8. I'm thinking that the changes need to include:
Depends: ${misc:Depends}, ${python:Depends}, python-django (>= 1.8)
Breaks: python-django (<= 1.7)
...
Depends: ${misc:Depends}, ${python3:Depends}, python3-django (>= 1.8)
Breaks: python3-django (<=1.7)
i.e. django-tables 1.1.6 reveals a "bug" in django 1.7 so django needs
to be updated to 1.8 before django-tables 1.1.6 can be
upgraded/installed.
This should cause python-django-tables2 to be updated to the backport
when python-django 1.8 is installed from backports. Otherwise, packages
using django-tables fail to start with a HTTP500 due to django-tables
1.1.6 failing to operate with django 1.7.
There are two other packages heading into backports-new, so I need to
wait for those to appear in jessie-backports before django-tables can
be backported. With these additional changes, it may be better for these
to be applied in unstable and then I can carry the changes into
jessie-backports?
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
pgpHJX9uqEi9k.pgp
Description: OpenPGP digital signature
