South doesn't work with Django 1.7

Bug #1430324 reported by Raphaël Badin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Unassigned

Bug Description

Django 1.7 is in Vivid so we need to support the new migration system.

South is EOL (a better version of it has been included in Django 1.7) and the db migrations from MAAS should be upgraded (see https://docs.djangoproject.com/en/dev/topics/migrations/#upgrading-from-south).

description: updated
Changed in maas:
milestone: none → next
Changed in maas:
status: Triaged → Fix Released
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.