[Django] #21901: Dependencies on unmigrated apps not always detected.

7 views
Skip to first unread message

Django

unread,
Jan 29, 2014, 11:07:45 AM1/29/14
to django-...@googlegroups.com
#21901: Dependencies on unmigrated apps not always detected.
-------------------------------------------+-----------------------------
Reporter: mjtamlyn | Owner:
Type: Bug | Status: new
Component: Migrations | Version: 1.7-alpha-1
Severity: Release blocker | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+-----------------------------
Related to the comment on
https://github.com/django/django/commit/941d23e54890bcc9e73734c5c1f3c82193fd97d6

I have seen this behaviour myself, with a custom user model using
`PermissionsMixin`. The necessary line in `dependencies` of `("auth",
"__first__"),` is not present. I'm not sure whether this is an issue with
it being a swappable model or not, but there's definitely a bug anyway.

The migration gets written out, but on running it you get a traceback
because the relations to auth cannot resolve (as the migration's limited
app cache ignores auth)

--
Ticket URL: <https://code.djangoproject.com/ticket/21901>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jan 29, 2014, 11:30:59 AM1/29/14
to django-...@googlegroups.com
#21901: Dependencies on unmigrated apps not always detected.
---------------------------------+---------------------------------------
Reporter: mjtamlyn | Owner:
Type: Bug | Status: closed
Component: Migrations | Version: 1.7-alpha-1
Severity: Release blocker | Resolution: duplicate

Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+---------------------------------------
Changes (by bmispelon):

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


Comment:

The same user who posted this comment also opened a ticket: #21872.

It should be fixed now. Do you still see this error on master?

--
Ticket URL: <https://code.djangoproject.com/ticket/21901#comment:1>

Reply all
Reply to author
Forward
0 new messages