From owner-freebsd-python@FreeBSD.ORG Sun Nov 3 06:04:58 2013 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 994A64BE; Sun, 3 Nov 2013 06:04:58 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B168C2EA2; Sun, 3 Nov 2013 06:04:57 +0000 (UTC) Received: from [192.168.0.22] (unknown [130.255.26.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id F176A43600; Sun, 3 Nov 2013 01:04:40 -0500 (CDT) Message-ID: <5275E762.2070804@marino.st> Date: Sun, 03 Nov 2013 07:04:18 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: koobs@FreeBSD.org Subject: Re: List of ports with "python 3" errors in poudriere References: <526F74EB.3090609@marino.st> <20131029101843.Horde.4oSfvuetQiW-9bokMpbfHw1@webmail.df.eu> <526F8AD2.50001@FreeBSD.org> In-Reply-To: <526F8AD2.50001@FreeBSD.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Baptiste Daroussin , mva@freebsd.org, python@freebsd.org, Kubilay Kocak X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: marino@freebsd.org List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Nov 2013 06:04:58 -0000 On 10/29/2013 11:15, Kubilay Kocak wrote: > On 29/10/2013 8:18 PM, Marcus von Appen wrote: >> >> For those with too much free time at their hands: feel free to go >> through John's list >> and fix the ports to use a proper python version at build time instead >> of `python` :-). >> > > Thanks for the explanation marcus. > > Can we get that list submitted as a PR, with clear instructions on the > fix procedure? Maybe even an example fix to help motivate > > I think this is a perfect opportunity to share the load, and I'll put my > hand up to help. > > Some clarity/confirmation included in the PR for the following would > also be great: > > - Can these be fixed *now* or is there something that needs to be done > first? > - What is the definition of 'proper' as you use it here? > Hi, Do you guys have an ETA for this? We're trying to stabilize dports for Release 3.6 and all the aforementioned ports are broken. DPorts is not supposed to feature ports that can't be built so I have have to choose whether to remove them or fix them myself. I was under the impression from Marcus that the fixes were rather trivial so I figured that they would get fixed quickly. If that's not going to be the case, it would be nice to nice that as well. Thanks, John