Mark,
Seems that's not going to be so easy hehehe: error: Failed build dependencies: icu is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 bzip2-devel is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 doxygen is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-ldap is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-six is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-pyasn1 is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-pyasn1-modules is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-dateutil is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-argcomplete is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-argparse-manpage is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-policycoreutils is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-libselinux is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 python3-packaging is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64 npm is needed by 389-ds-base-1.4.2.4-20191218.el7.x86_64
Most packages are pretty easy to install but seems that python3-libselinux was not shipped into centos7: https://bugs.centos.org/view.php?id=16389 https://bugzilla.redhat.com/show_bug.cgi?id=1756015 https://bugzilla.redhat.com/show_bug.cgi?id=1719978
Seems to me there's no solution at this point, Am I right?
Thanks
On Wed, Dec 18, 2019 at 6:20 PM Mark Reynolds mreynolds@redhat.com wrote:
On 12/18/19 4:05 PM, Alberto Viana wrote:
Mark,
Yes, I'm.
To compile lib389 I installed a package for python3 called "selinux" (via pip)
# pip3 show selinux Name: selinux Version: 0.2.1 Summary: shim selinux module Home-page: https://github.com/pycontribs/selinux Author: Sorin Sbarnea Author-email: sorin.sbarnea@gmail.com License: MIT license
May be am I missing this lib(python3-libselinux)?
It's a requirement for lib389 in our specfile, should be easy to check for it.
What if you try an rpm using "make -f rpm.mk rpms" from the 389-ds-base/ directory?
On Wed, Dec 18, 2019 at 5:39 PM Mark Reynolds mreynolds@redhat.com wrote:
On 12/18/19 3:21 PM, Alberto Viana wrote:
Hi Guys,
I compiled my 389 with selinux enabled (--with-selinux):
configure:21564: checking for --with-selinux configure:21575: result: yes
with_selinux='yes'
but If I ran dscreate interactive, shows me: selinux is disabled, will not relabel ports or files.
The selinux is enabled on the system ~# getenforce Enforcing
Centos7 # ns-slapd -v 389 Project 389-Directory/1.4.2.4 B2019.352.1557
What am I missing? Could not found any related doc at 389 or rhds pages.
Not sure, this is the code that is generating the error message:
import selinux if selinux.is_selinux_enabled(): # We have selinux, continue. status = True else: # We have the module, but it's disabled. log.error('selinux is disabled, will not relabel ports or
files.' )
So this is all happening in the python library (python3-libselinux). Are you running dscreate as root?
Mark
Thanks.
Alberto Viana
389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject....
--
389 Directory Server Development Team
--
389 Directory Server Development Team