Is it the dependency on the selinux-devel or SELinux in general? I do not see a reason why we should not require an selinux-devel package by default and not build with it only if it is explicitly disabled at build time using some kind of --no-selinux-integration flag or similar.

Dmitri, we DO have a --without-selinux configure flag. What he is reporting is that our recent addition of SELinux user contexts with FreeIPA is not properly honoring that flag. We're trying to build it unconditionally. This is incorrect (we need to support building on platforms that do not have SELinux).

This is a regression and needs to be fixed before 1.9.0 is released.

component: SSSD => Build Environment
keywords: => Regression
priority: minor => blocker
rhbz: => 0

Thank you for the bug report. I've just posted a patch to the upstream devel list. I'll let you know once it's pushed to master so that you can cherry-pick it and include for build for your distribution (I assume you are building beta6 for a non-Fedora/non-Red Hat distro)

owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned

Fixed in af824ba

milestone: NEEDS_TRIAGE => SSSD 1.9.0 RC1
resolution: => fixed
status: assigned => closed

Replying to [comment:3 jhrozek]:

Thank you for the bug report. I've just posted a patch to the upstream devel list. I'll let you know once it's pushed to master so that you can cherry-pick it and include for build for your distribution (I assume you are building beta6 for a non-Fedora/non-Red Hat distro)

You obtain the patch from our upstream repository with:

git format-patch -1 af824bac568ebe8a03273f73246ac78b415ea756

Or just download the single patch file here:

http://git.fedorahosted.org/cgit/sssd.git/patch/?id=af824bac568ebe8a03273f73246ac78b415ea756

Thank you again for the bug report.

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2522

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.