title: django south: models are shown as not synced even if they are (or should be)
body: <p>I am getting this after syncdb:</p>
  
  <pre><code>clime@den /var/www/loserti $ ./manage.py syncdb
  Syncing...
  Creating tables ...
  Creating table tagging_tag
  Creating table tagging_taggeditem
  Installing custom SQL ...
  Installing indexes ...
  Installed 0 object(s) from 0 fixture(s)
  
  Synced:
   &gt; django.contrib.auth
   &gt; django.contrib.contenttypes
   &gt; django.contrib.sessions
   &gt; django.contrib.sites
   &gt; django.contrib.messages
   &gt; django.contrib.staticfiles
   &gt; django.contrib.admin
   &gt; django.contrib.admindocs
   &gt; django.contrib.flatpages
   &gt; debug_toolbar
   &gt; filebrowser
   &gt; grappelli
   &gt; tagging
   &gt; south
  
  Not synced (use migrations):
   - photologue
   - web
  (use ./manage.py migrate to migrate these)
  </code></pre>
  
  <p>So I run migrate:</p>
  
  <pre><code>clime@den /var/www/loserti $ ./manage.py migrate
  Running migrations for photologue:
  - Nothing to migrate.
   - Loading initial data for photologue.
  Installed 0 object(s) from 0 fixture(s)
  Running migrations for web:
  - Nothing to migrate.
   - Loading initial data for web.
  Installed 0 object(s) from 0 fixture(s)
  </code></pre>
  
  <p>But the result of syncdb is still the same:</p>
  
  <pre><code>clime@den /var/www/loserti $ ./manage.py syncdb
  Syncing...
  Creating tables ...
  Installing custom SQL ...
  Installing indexes ...
  Installed 0 object(s) from 0 fixture(s)
  
  Synced:
   &gt; django.contrib.auth
   &gt; django.contrib.contenttypes
   &gt; django.contrib.sessions
   &gt; django.contrib.sites
   &gt; django.contrib.messages
   &gt; django.contrib.staticfiles
   &gt; django.contrib.admin
   &gt; django.contrib.admindocs
   &gt; django.contrib.flatpages
   &gt; debug_toolbar
   &gt; filebrowser
   &gt; grappelli
   &gt; tagging
   &gt; south
  
  Not synced (use migrations):
   - photologue
   - web
  (use ./manage.py migrate to migrate these)
  </code></pre>
  
  <p>How is that possible and how to fix it?</p>
  
  <p>EDIT: Here is a faint idea. Could it be that I used ./manage.py syncdb at some point to create new tables for these apps and I should have used migrations instead?</p>