Date: Fri, 21 Jun 2019 16:12:11 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 238465] security/sssd: Update port to new version Message-ID: <bug-238465-7788-i3WrHm1Pnv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238465-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-238465-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=3D238465 --- Comment #2 from John Hein <jcfyecrayz@liamekaens.com> --- Created attachment 205266 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D205266&action= =3Dedit [patch] update to 1.12.5 Here' a patch to update to 1.12.5 This takes sssd from the old 1.11.7 up one major to the latest 1.12 release= .=20 Next will be to update to 1.13.4 which is the latest in the long term maintenance (LTM) release series. I think the LTM series (now 1.13.*) shou= ld be the target for the security/sssd port for now. >From the release info page: https://docs.pagure.org/SSSD.sssd/users/releases.html "Releases designated as LTM are long-term maintenance releases and will see bugfixes and security patches for a longer time than other releases." There is also a so-called "stable" release series. Search for "stable" on = the home page: https://pagure.io/SSSD/sssd That might be a good candidate for a security/sssd-stable port. Alternatel= y, security/sssd could be the "stable" flavor and there could be a security/sssd-ltm or security/sssd13. For now, let's good up to the LTM release at least. Then we can decide whe= re to go from there. QA: - poudriere testport (11/amd64): ok - stage-qa & check-plist: ok - portlint (no new errors or warnings) ** To be helpful, please do some run testing. Just quick testing is fine s= ince I will submit an update to 1.13.4 here soon. Change summary: - update 1.11.7 to 1.12.5 - use non-legacy tdb/ldb/talloc/tevent ports - pet portlint: move USES - put all /var/db paths in /var/db/sss/ (new: /var/db/sss/gpo_cache; move db/sss_mc -> db/sss/mc) - use --without-nfsv4-idmapd-plugin (NFSv4 idmapd function is different in freebsd - see nfsuserd). Future change can investigate integration with nfsuserd. For now, avoid build issues if it tries to include support for idmapd. - update startup script with new /var dirs. Add them to @dir cleanup list= in pkg-plist. Remove the ${RMDIR} for them from Makefile (not needed). - update some of the patches to fix build errors (need LTLIBINTL for some build products, remove more cases of non-portable "timezone" global, catch = up existing patches due to upstream code motion, etc.) - pkg-plist refresh to reflect changes (mostly man pages & docs; a couple = new .so modules and two new .pc files) --=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-238465-7788-i3WrHm1Pnv>