This bug appears to be fixed in upstream version python-selinux 2.0.55-0ubuntu4. Can you please verify?
This bug appears to be fixed in upstream version python-selinux 2.0.55-0ubuntu4. Can you please verify?