Date: Thu, 01 Mar 2018 08:45:24 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 226135] lang/python27: Fails to package after r462630 (_elementtree / pyexpat modules) Message-ID: <bug-226135-21822-YYlyB4FWLj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-226135-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-226135-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226135 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |python@FreeBSD.org Flags|maintainer-feedback?(python |maintainer-feedback?(sunpoe |@FreeBSD.org) |t@FreeBSD.org), | |maintainer-feedback?(brnrd@ | |freebsd.org) --- Comment #23 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Sunpoet Po-Chuan Hsieh from comment #20) I note that other python ports didn't get the original change (ports r462630, as part of bug 222795), but also: - python34 still has BROKEN_SSL=openssl-devel - python35 doesn't - python36 doesn't Were you going to apply r462630 to the other ports as well? What is the status with regard to ssl support in other ports? (>2.7) Barnerd, if you can comment on the change delta required to get all lang/python?? ports to support openssl/openssl-devel/libressl, that would be appreciated. We (python) want as much consistency across the ports as possible, so I'll want to replicate this change into every port unless there are reasons not to. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226135-21822-YYlyB4FWLj>