From owner-freebsd-ports-bugs@freebsd.org Mon Oct 21 17:17:48 2019 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5893815C2F1 for ; Mon, 21 Oct 2019 17:17:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46xjy41gknz4TNp for ; Mon, 21 Oct 2019 17:17:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 37BD915C2F0; Mon, 21 Oct 2019 17:17:48 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3786015C2EF for ; Mon, 21 Oct 2019 17:17:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46xjy40g25z4TNn for ; Mon, 21 Oct 2019 17:17:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EDF762726E for ; Mon, 21 Oct 2019 17:17:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x9LHHluW096356 for ; Mon, 21 Oct 2019 17:17:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x9LHHlGO096354 for ports-bugs@FreeBSD.org; Mon, 21 Oct 2019 17:17:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 241347] security/sssd: Update to 1.16.4 Date: Mon, 21 Oct 2019 17:17:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: vrwmiller@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2019 17:17:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241347 --- Comment #7 from Rick --- Thanks for explaining 1.16 vs 2.x. It makes sense to track the same version being deployed in Red Hat. In considering explicit Samba dependencies, my preference remains in favor = of putting control in the users hands unless there is material information I am missing or misunderstanding. Explicit dependency works for users pulling in Samba as a direct consequence of sssd. However, users pulling in Samba as a consequence of sssd and one or more other ports may experience conflicts an= d/or failed builds. Defining explicit dependencies also implies more effort to ensure compatibility. In other words, ports defining explicit dependencies must st= ay vigilant as Samba versions are deprecated. SSSD fell victim to this as Samba 4.[678] have and are reaching EOL as proven by its failure to build w/ SMB = from July 2019 on after Samba 4.[67] were removed and thus defaults to 4.8. Comments to Makefile or UPDATING explaining and recommending defining defau= lt Samba to 4.10 when SMB is enabled are appropriate w/ the addition that chan= ging the default may result in undesirable behavior as a consequence of differing ABIs with winbind_idmap_sss.so. This is irrelevant to me as each repository stands on it=E2=80=99s own. Having said all that, sssd w/ the attached patch for 1.16.4 continues to fa= il during configure citing the error above. It occurs even despite defining PYTHON_VERSION and/or PYTHON_CMD in make.conf for either Python 2.7 or 3.6 like: .if ${.CURDIR:M*/security/sssd} PYTHON_VERSION=3D 3.6 PYTHON_CMD=3D/usr/local/bin/python3.6 OPTIONS_FILE_SET+=3DSMB=20=20 .endif --=20 You are receiving this mail because: You are the assignee for the bug.=