New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ds_selinux_enabled may fail on suse in some cases #3677
Comments
Comment from mreynolds (@mreynolds389) at 2019-09-26 17:43:46 Metadata Update from @mreynolds389:
|
Comment from tbordaz (@tbordaz) at 2019-09-26 17:45:18 @Firstyear is okay to close it now ? (#3678) |
Comment from tbordaz (@tbordaz) at 2019-09-26 17:45:18 Metadata Update from @tbordaz:
|
Comment from firstyear (@Firstyear) at 2019-09-27 01:46:15 Not yet, I need to know if it's okay to backport to 1.4.0 and 1.4.1 from @mreynolds389 |
Comment from mreynolds (@mreynolds389) at 2019-09-30 15:19:05
Yeah of course it s fine. Typically if its not a RFE, or change in behavior, you can backport it to whatever branch you want. |
Comment from firstyear (@Firstyear) at 2019-10-01 02:50:20 @mreynolds389 Thanks mate. Just want to be sure you know what I'm up to! Rather have your input than surprise you with weird changes is all. I'll backport this today. |
Comment from firstyear (@Firstyear) at 2019-10-01 02:57:14
|
Comment from firstyear (@Firstyear) at 2019-10-01 02:57:15 Metadata Update from @Firstyear:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50622
Issue Description
We don't check if we have the selinux python module in this command, so it may fail when we do not have it.
The text was updated successfully, but these errors were encountered: