From owner-freebsd-python@FreeBSD.ORG Mon Oct 28 22:50:03 2013 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9A7D36C0 for ; Mon, 28 Oct 2013 22:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8331B25B4 for ; Mon, 28 Oct 2013 22:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9SMo2ZZ020859 for ; Mon, 28 Oct 2013 22:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9SMo2oJ020858; Mon, 28 Oct 2013 22:50:02 GMT (envelope-from gnats) Date: Mon, 28 Oct 2013 22:50:02 GMT Message-Id: <201310282250.r9SMo2oJ020858@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Krzysztof Stryjek Subject: Re: Re: ports/165545: [patch]: net-mgmt/collectd5 doesn't compile against lang/python[23]* X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Krzysztof Stryjek List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 22:50:03 -0000 The following reply was made to PR ports/165545; it has been noted by GNATS. From: Krzysztof Stryjek To: koobs@FreeBSD.org Cc: bug-followup@FreeBSD.org, pgollucci@freebsd.org, rflynn@acsalaska.net Subject: Re: Re: ports/165545: [patch]: net-mgmt/collectd5 doesn't compile against lang/python[23]* Date: Mon, 28 Oct 2013 23:42:02 +0100 Hello, On Mon, Oct 28, 2013 at 09:20:16PM +1100, Kubilay Kocak wrote: > Hi Krzysztof, > > I'm on a Python bug busting mission and would like your input on > resolving this PR. At last follow-up, a patch by Mel (CC'd) to > collectd5's configure script exists, but has no feedback. > > The answers to a couple of questions should help get us the most > appropriate and timely outcome: > > 1) Can we close this PR given its present state? > > If not: > > 2) Is this still an issue with: > a) Current collectd5 version, AND > b) Supported Python versions? My experience is that currently collectd5 compiles with current python (2.7) without problems. So I think this PR could be closed. Greetings, -- Krzysztof Stryjek UNIX administrator/Juniper Networks Specialist email: wtp (at) bsdserwis (dot) com http://www.linkedin.com/in/KrzysztofStryjek GPG fingerprint: 8BD7 40CE 8994 0BBE CE6C 91CD 1292 8959 DC61 0E76 In theory, there is no difference between theory and practice. In practice, there is.