First time here? Check out the FAQ!

Revision history  [back]

edited Please try the latest code from the repository, we might have fixed this issue.

edited Please try the latest code from the repository, we might have fixed this issue.You can do this:

python manage.py migrate askbot 0160 #migrate all up to one before the conflict
python manage.py migrate askbot 0161 --fake #fake the conflicting migration
python manage.py migrate askbot #continue with the rest

The issue is that django's auth app does not uses south so in syncdb it will create all the model's fields that it detects, when askbot migrations arrives this conflict happens.

You can do this:

python manage.py migrate askbot 0160 #migrate all up to one before the conflict
0160
python manage.py migrate askbot 0161 --fake #fake the conflicting migration
python manage.py migrate askbot #continue with the rest
--fake

The issue is that django's auth app does not uses south so in syncdb it will create all the model's fields that it detects, when askbot migrations arrives this conflict happens.