You can't depends on table with migrations enabled if you don't enable them yourself…
When you use migrate on a brand new empty database, it will create non-migrations tables first, as you rely on content type, you should make a (non south) migration file…
easy work-around, you can disable app, migrate and re-enable app… but for fully automated deployment it's not practical…
Here how error message looks like:
django.db.utils.ProgrammingError: relation "django_content_type" does not exist
You can't depends on table with migrations enabled if you don't enable them yourself…
When you use migrate on a brand new empty database, it will create non-migrations tables first, as you rely on content type, you should make a (non south) migration file…
easy work-around, you can disable app, migrate and re-enable app… but for fully automated deployment it's not practical…
Here how error message looks like: django.db.utils.ProgrammingError: relation "django_content_type" does not exist