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

[Brian May]

Some misconceptions resolved:

* This bug does not cause any data to be deleted.
* This bug does not cause any data to be currupted.
* This bug does not cause any data to be lost.
* This bug only affects one application. Out of many others that use Django.

The damage this bug does cause:

* If you try to upgrade the package in question, the migrations will run
  in the postinst script. These migrations will fail - before even
  touching the database. This is a pre-migration sanity check that
  fails. This in turn means the postinst script will fail and the
  package is marked as bad.

  All the data is still there, and it hasn't been touched. It may not be
  accessible to the application however, as it will depend on the
  migrations being run. The application may crash as the database schema
  is different from what it expects.

I do not believe this should be an RC bug against Django.
-- 
Brian May <bam at debian.org>