From owner-freebsd-ports-bugs@freebsd.org Fri Nov 8 06:47:58 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 0F9191A8EE3 for ; Fri, 8 Nov 2019 06:47:58 +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 478W716gSFz3xjG for ; Fri, 8 Nov 2019 06:47:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id E4D441A8EE2; Fri, 8 Nov 2019 06:47:57 +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 E49051A8EE1 for ; Fri, 8 Nov 2019 06:47:57 +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 478W715DlYz3xjD for ; Fri, 8 Nov 2019 06:47:57 +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 9438F223D7 for ; Fri, 8 Nov 2019 06:47:57 +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 xA86lvSv052436 for ; Fri, 8 Nov 2019 06:47:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xA86lvRn052435 for ports-bugs@FreeBSD.org; Fri, 8 Nov 2019 06:47:57 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: Fri, 08 Nov 2019 06:47:56 +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 Some People X-Bugzilla-Who: prj@rootwyrm.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: Fri, 08 Nov 2019 06:47:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241347 --- Comment #14 from Phillip R. Jaenke --- No worries on that, we all have lives. Since SSSD has *always* been a "special handling required" port, I think the only real question here is whether to ship as-is (which means default build= s of dependencies will leave it non-functioning) or update samba410 to use MIT default (that's a timur@ call and as MIT is experimental probably a bad ide= a.) Considering all those moving pieces, I think we've re-exposed a shortcoming= in ports infrastructure that isn't going to be resolved today - or this quarte= r, and probably not next year. Once building clean is confirmed and function is confirmed when dependencies are built to suit, commit it as is. Then exclud= e it from official pkgbuilds (maybe RESTRICTED?) so that users have to engage th= eir brains and build everything the right way. Once we have the key portions here, I'm happy to take up the torch of writi= ng a pkg message explaining to users what they need to do to produce a working setup. --=20 You are receiving this mail because: You are the assignee for the bug.=