From owner-freebsd-python@freebsd.org Tue Mar 27 09:46:57 2018 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D417CF669FB for ; Tue, 27 Mar 2018 09:46:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6B52D7A07E for ; Tue, 27 Mar 2018 09:46:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2D0CBF669DD; Tue, 27 Mar 2018 09:46:56 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AF4FF669D7 for ; Tue, 27 Mar 2018 09:46:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9551A7A079 for ; Tue, 27 Mar 2018 09:46:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id BBD6F27FFE for ; Tue, 27 Mar 2018 09:46:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2R9ks61002686 for ; Tue, 27 Mar 2018 09:46:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2R9kssD002685 for python@FreeBSD.org; Tue, 27 Mar 2018 09:46:54 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: python@FreeBSD.org Subject: [Bug 226883] lang/python27, lang/python35, lang/python36: libressl 2.7 build failures Date: Tue, 27 Mar 2018 09:46:54 +0000 X-Bugzilla-Reason: CC 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: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc bug_status 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-python@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 09:46:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226883 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brnrd@freebsd.org, | |python@FreeBSD.org Status|New |Open --- Comment #2 from Kubilay Kocak --- Thank you for your report Charlie, Could you confirm/clarify some points that might be slightly ambiguous: - Is D14837 the same as the OpenBSD patches, or different, fixing "both ssl=3Dopenssl and ssl=3Dopenssl-devel" build failures referenced in comment= 0? - In D14837, Does "Fails otherwise" mean the same as "breaks both ssl=3Dope= nssl and ssl=3Dopenssl-devel" as referenced in comment 0 here, or some other subset/combination? - I interpreted 'upstream' in 'upstream will not release their patch' to me= an Python (waiting for libressl upstream to 'release' before committing code).= Is this correct? An explicit/accurate/complete list of what succeeds/fails would be super ha= ndy to figure out where/what needs work from here: >From the standpoint of Python (team) and python ports, we'd ideally like to take changesets from upstream after they're committed and backported there. We're happy to carry local patches prior to next point releases in each bra= nch. If we can confidently get to the point where we have a candidate changeset = with thorough QA passing and no regressions, we can consider landing it early (before upstream (Python)). For clarity purposes, if the changeset in D14837 is incomplete (in that it regresses certain ssl combinations), then it should be abandoned in favour = of a 'work in progress' patch here for someone (Bernard, CC'd, is the point on libressl things) to review and improve upon. At the point where a QA passing/complete patch is ready, we can put it back= up on Phabricator for broader review, if necessary beyond here. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=