Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

2017-08-12 Thread Django
#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+
 Reporter:  Daniel Hahler  |Owner:  Windson yang
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:  needsinfo
 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 Tim Graham):

 * status:  assigned => closed
 * resolution:   => needsinfo


-- 
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/065.681286c65d1fe012523a685722f82420%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

2017-08-08 Thread Django
#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+
 Reporter:  Daniel Hahler  |Owner:  Windson yang
 Type:  Bug|   Status:  assigned
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Windson yang):

 I need more details to fix this bug.

-- 
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/065.d8b45ebd00e50699244495ce4393b6b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

2017-07-04 Thread Django
#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+
 Reporter:  Daniel Hahler  |Owner:  Windson yang
 Type:  Bug|   Status:  assigned
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:
 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 Windson yang):

 * status:  new => assigned
 * owner:  nobody => Windson yang


-- 
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/065.ce76e2c7bee373b88817d9e80adeecf2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

2017-06-30 Thread Django
#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+
 Reporter:  Daniel Hahler  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:
 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 Tim Graham):

 * stage:  Unreviewed => Accepted


Comment:

 Tentatively accepting. Might be difficult to proceed without steps to
 reproduce unless you plan to offer a patch.

--
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/065.2b6307beda3abf2888a6833cc1ef817a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

2017-06-30 Thread Django
#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+--
 Reporter:  Daniel Hahler  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:
 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 Daniel Hahler):

 Not currently.

 I think a fix might be to move over the `replaces` from the node that gets
 replaced, and/or only to replace up to the parent that got applied in
 
https://github.com/django/django/blob/a6756195c1a11eee10c16c96fe95d52e22e1d9ba/django/db/migrations/graph.py#L243-L245.

--
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/065.923b5748d5d5871cc6f7ab862d6e843b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

2017-06-30 Thread Django
#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
---+--
 Reporter:  Daniel Hahler  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:
 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 Tim Graham):

 Can you provide more explicit steps to reproduce the problematic
 situation?

--
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/065.3e3d17fbb687d87a70130a765defeed3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


[Django] #28351: "Conflicting migrations detected" CommandError due to replacement Migration being removed

2017-06-30 Thread Django
#28351: "Conflicting migrations detected" CommandError due to replacement 
Migration
being removed
-+
   Reporter:  Daniel Hahler  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Migrations |Version:  1.11
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I am getting the following error:
 {{{
 CommandError: Conflicting migrations detected; multiple leaf nodes in the
 migration graph: (0002_initial_models, 0XXX_merge_20170628_1435 in myapp).
 To fix them run 'python manage.py makemigrations --merge'
 }}}

 Running the command results in `No conflicts detected to merge.` however.

 `0002_initial_models` is not actually a leaf node, but `0003_initial_data`
 depends on it.
 `0003_initial_data` however is removed, since it replaces
 `0XXX_merge_20170628_1435`, which is not applied yet and therefore also
 does not show up in `showmigrations`?!
 (it gets removed in
 
https://github.com/django/django/blob/a6756195c1a11eee10c16c96fe95d52e22e1d9ba/django/db/migrations/graph.py#L252)

 I think `0003_initial_data` should still show up in `showmigrations`, but
 with some indication that it replaces other migrations.
 That would happen in case it wasn't removed as a leaf node in
 
https://github.com/django/django/blob/a6756195c1a11eee10c16c96fe95d52e22e1d9ba/django/core/management/commands/showmigrations.py#L82-L83.

--
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/050.1ab087059cdfd47164587f99205e69af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.