title: Django and South: using south makes syncdb show myapp as 'not synced (use migrations)'
body: <p>When I run ./manage.py syncdb it says not synced (use migrations).  However, when I run </p>
  
  <pre><code>$ ./manage.py schemamigration myapp --auto
  Nothing seems to have changed
  $ ./manage.py migrate
  blah blah, nothing to migrate
  </code></pre>
  
  <p>As per <a href="https://stackoverflow.com/questions/4625712/whats-the-recommended-approach-to-resetting-migration-history-using-django-sout">this thread</a>, I tried resetting south to fix the problem.  Here's what I did:</p>
  
  <pre><code>$ rm -r appname/migrations/ 
  $ ./manage.py reset south
  $ ./manage.py syncdb
      (at this point it shows all apps as synced)
  $ ./manage.py convert_to_south myapp
  blah blah, App 'blog' converted.
  $ ./manage.py syncdb
      (at this point it shows myapp as not synced)
  </code></pre>
  
  <p>Running schemamigration > migrate has the same effect as before (nothing, still not registering as synced).
  On the plus side, the app still seems to work fine, I'm just worried this could cause problems down the road.  Any idea what's going on and how I can fix it?  Is this even really a problem?  I'm using SQLite3 and Django 1.4.2 if that helps.</p>