Re: [Django] #22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade

[Django]

#22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade
-+--
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by rockallite.wulf@…):

 Replying to [comment:2 bendavis78]:
 > [edit] sorry, just realized this was a dup. I'll post this in the main
 ticket.
 >
 > I got this same error when trying to migrate my own app when my project
 uses he django-taggit app. TaggedItem has a ForeignKey to ContentType, and
 when trying to makemigrations for one of my apps I get the following:
 >
 > {{{
 > ValueError: Lookup failed for model referenced by field
 taggit.TaggedItem.content_type: contenttypes.ContentType
 > }}}
 >
 > Is there a workaround?


 Just add the corresponding dependency in the migration file, like this:

 {{{
 dependencies = [
 (b'advperm', b'0001_initial'),
 (b'auth', b'__first__'),
 (b'contenttypes', b'__first__'),  # Add this line
 ]
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9dce6c51ac773227066c99c0b8576911%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade

[Django]

#22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade
-+--
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by bendavis78):

 * cc: bendavis78 (added)


Comment:

 I got this same error when trying to migrate my own app when my project
 uses he django-taggit app. TaggedItem has a ForeignKey to ContentType, and
 when trying to makemigrations for one of my apps I get the following:

 {{{
 ValueError: Lookup failed for model referenced by field
 taggit.TaggedItem.content_type: contenttypes.ContentType
 }}}

 Is there a workaround?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f8953daff71db980e9fbdf1e366c9b4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade

[Django]

#22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade
-+--
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by charettes):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Hi Karen,

 This is a duplicate of #22485 which is related to #21968 and #22397.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.8d71469e7a4b01906f84dc36b064bc30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade

[Django]

#22488: "ValueError: Lookup failed" on migrate after 1.7b2 upgrade
---+
   Reporter:  kmtracey |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  1.7-beta-2
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 I'm getting an error running migrate on a project after upgrading from
 1.7b1 to 1.7b2. Running tests produces same error (somewhat different
 traceback). Besides the error something weird I notice is that auth is
 listed in both the "unmigrated" and "migrated" apps...I have no idea why.
 The project does use a custom user model. auth is listed as both migrated
 and not for 1.7b1 and 1.7b2, but the error only occurs on 1.7b2.

 I am not sure what would be helpful to debug this. This is what I see:

 {{{
 (uncfm) kmtracey@caktus006 11:48:48: ~/projects/uncfm
 --> ./manage.py shell
 Python 3.3.5 (default, Mar 12 2014, 02:09:17)
 [GCC 4.6.3] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> import django
 >>> django.get_version()
 '1.7b1'
 >>> quit()

 (uncfm) kmtracey@caktus006 11:48:59: ~/projects/uncfm
 --> ./manage.py migrate --list
 core
  [X] 0001_initial
 m3app
  [X] 0001_initial
  [X] 0002_observer_active
  [X] 0003_auto_20140415_1317
 scribbler
  (no migrations)

 (uncfm) kmtracey@caktus006 11:49:02: ~/projects/uncfm
 --> ./manage.py migrate
 Operations to perform:
   Synchronize unmigrated apps: compressor, sitemaps, contenttypes,
 scribbler, sessions, auth, admin
   Apply all migrations: auth, core, m3app
 Synchronizing apps without migrations:
   Creating tables...
   Installing custom SQL...
   Installing indexes...
 Running migrations:
   No migrations needed.

 (uncfm) kmtracey@caktus006 11:49:08: ~/projects/uncfm
 --> pip install requirements/sdists/Django-1.7b2.tar.gz
 Unpacking ./requirements/sdists/Django-1.7b2.tar.gz
   Running setup.py (path:/tmp/pip-v_a8yl-build/setup.py) egg_info for
 package from
 file:///home/kmtracey/projects/uncfm/requirements/sdists/Django-1.7b2.tar.gz

 warning: no previously-included files matching '__pycache__' found
 under directory '*'
 warning: no previously-included files matching '*.py[co]' found under
 directory '*'
 Installing collected packages: Django
   Found existing installation: Django 1.7b1
 Uninstalling Django:
   Successfully uninstalled Django
   Running setup.py install for Django

 warning: no previously-included files matching '__pycache__' found
 under directory '*'
 warning: no previously-included files matching '*.py[co]' found under
 directory '*'
 changing mode of build/scripts-3.3/django-admin.py from 664 to 775
 changing mode of /home/kmtracey/.virtualenvs/uncfm/bin/django-admin.py
 to 775
 Installing django-admin script to
 /home/kmtracey/.virtualenvs/uncfm/bin
 Successfully installed Django
 Cleaning up...

 (uncfm) kmtracey@caktus006 11:49:36: ~/projects/uncfm
 --> ./manage.py migrate --list
 core
  [X] 0001_initial
 m3app
  [X] 0001_initial
  [X] 0002_observer_active
  [X] 0003_auto_20140415_1317
 scribbler
  (no migrations)

 (uncfm) kmtracey@caktus006 11:49:45: ~/projects/uncfm
 --> ./manage.py migrate
 Operations to perform:
   Synchronize unmigrated apps: sitemaps, contenttypes, scribbler, auth,
 compressor, sessions, admin
   Apply all migrations: auth, m3app, core
 Synchronizing apps without migrations:
   Creating tables...
   Installing custom SQL...
   Installing indexes...
 Running migrations:
   No migrations needed.
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/home/kmtracey/.virtualenvs/uncfm/lib/python3.3/site-
 packages/django/core/management/commands/migrate.py", line 140, in handle
 changes =