#29027: file_move_safe error with SELinux
-------------------------------------+-------------------------------------
     Reporter:  bhargu               |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  File                 |                  Version:  1.11
  uploads/storage                    |
     Severity:  Normal               |               Resolution:
     Keywords:  selinux              |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Paolo Donadeo):

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


Comment:

 I have a question: why the ticket has been closed? I can confirm the issue
 reported by bhargu still present in Django 2.1.3 and I can confirm that
 the proposed patch:
 
https://github.com/agrimgt/django/commit/f9b48086d083b1eee800ea752f2c3fd60a8cc448
 works.

 This is a show stopper for us: Django simply don't work on a RHEL7 or
 CentOS7 with SELinux enabled. To deploy Django 2.x I'm forced to fork.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29027#comment:4>
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 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/064.074667c6f064cfd9ff06d67889597c6f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to