#36793: Reverting a model rename in an environment with pre-Django 6.0 
permission
records leaves wrong users & groups associated
-------------------------------------+-------------------------------------
     Reporter:  Jacob Walls          |                    Owner:  Jacob
                                     |  Walls
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.auth         |                  Version:  6.0
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):

 In [changeset:"42bab76258162e1df77d080aa69cac5d803ae90a" 42bab762]:
 {{{#!CommitTicketReference repository=""
 revision="42bab76258162e1df77d080aa69cac5d803ae90a"
 [6.0.x] Fixed #36843, #36793 -- Reverted "Fixed #27489 -- Renamed
 permissions upon model renaming in migrations."

 This reverts commits f02b49d2f3bf84f5225de920ca510149f1f9f1da and
 6e89271a8507fe272d11814975500a1b40303a04.

 Backport of 030c63d329c4814da221528e823a4aaaaa40e4f1 from main.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36793#comment:17>
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 view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019b8febb98e-e3ffa7cc-1f2a-44e8-ab67-fa6bbe632c03-000000%40eu-central-1.amazonses.com.

Reply via email to