[Python-modules-team] Bug#863267: Bug#863267: Miscalculates MigrationHistory dependencies between multiple django apps - regression from 1.8

[Brian May]

On 2017-05-26 19:05, Neil Williams wrote:

> No. This is django making the wrong decision about problems it has
> previously supported when trying to include bug fixes for other
> problems. It is a regression in django 1.10

Feel free to argue this point in
https://code.djangoproject.com/ticket/28250 

Otherwise, I think we have three options. I recommend reading the Django
ticket in full before deciding. 

1. Apply work around from
https://code.djangoproject.com/ticket/28250#comment:1 by manually
recording that the database transaction has been applied. This could
potentially be automated as part of the postinst. 

2. Remove migration from postinst, and give instructions for manually
updating the database. Modify
/usr/share/doc/python-django/examples/migrate-south (maybe create new
file in Django package) so instead of installing Django 1.6.x in a
virtualenv and running migrations, it installs Django 1.8.x into
virtualenv and runs migrations. 

https://anonscm.debian.org/cgit/python-modules/packages/python-django.git/tree/debian/contrib/migrate-south


3. Drop lava-server from testing. 

Also it might be worth updating the migrate script in Django - as per
option 2 - even if you decide 1 is the best option. Would help in case
any similar problems are identified - maybe with packages not in Debian
- after the release.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20170529/9323446a/attachment-0001.html>