Date: Sat, 16 May 2020 15:26:40 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 241347] security/sssd: Update to 1.16.4 Message-ID: <bug-241347-7788-pKxsO0wQPT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241347-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-241347-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241347 Karli Sj=C3=B6berg <karli.sjoberg@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karli.sjoberg@gmail.com --- Comment #24 from Karli Sj=C3=B6berg <karli.sjoberg@gmail.com> --- Hi everyone and thank you all so much for working on this! I gotta say though, that right now sssd is just utterly broken. First of all, the original port (1.11) only builds with 'SAMBA4_BUNDLED_LDB=3DYES' and fails to start for unknown reasons. The logs= say very little about it, but it's got something to do with the version of ldb. Trying to switch up ldb from 14 to 15 in sssd's Makefile to match the ldb in samba410 makes it fail to build. Second, the push to upgrade to sssd 1.13 (that allegedly works) fails to cleanly apply the patchset and therefore fails to build. The WIP to change = it to 1.15 was never more than just that- a work in progress- and never really went anywhere. Lastly, the patch to go to 1.16 also fails to apply and, of course, also fa= ils to build because of it. I would be more than happy to help with either one of these alternatives, I just want to be able to log in to my servers again! Best Regards /K --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241347-7788-pKxsO0wQPT>