#28250: migration depending on non-existing legacy migration
-------------------------------+------------------------------------------
Reporter: Brian May | Owner: Marten Kenbeek
Type: Uncategorized | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------------
Comment (by Marten Kenbeek):
Replying to [comment:11 Raphaël Hertzog]:
> Thanks Marten for that work. I asked the lava-server maintainer to test
this patch, unfortunately the "migrate" call is still failing for him,
albeit with another error further down the road:
That seems to be because the project state generated for the `pre_migrate`
signal only includes state changes of migrations that are applied. Since
the initial migration is still marked as not applied, its state changes
are not propagated to the project state. I've updated the PR to fix this
issue as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/28250#comment:12>
Django <https://code.djangoproject.com/>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.4b4d3890400692dbcb32963230c941ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
