From owner-freebsd-python@FreeBSD.ORG Thu Oct 24 01:10:02 2013 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.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 2A5D5E86 for ; Thu, 24 Oct 2013 01:10:02 +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 16FF32E0B for ; Thu, 24 Oct 2013 01:10:02 +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 r9O1A1gQ002495 for ; Thu, 24 Oct 2013 01:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9O1A1tm002494; Thu, 24 Oct 2013 01:10:01 GMT (envelope-from gnats) Date: Thu, 24 Oct 2013 01:10:01 GMT Message-Id: <201310240110.r9O1A1tm002494@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Jan Mikkelsen Subject: Re: ports/163467: lang/python27: Ports using python 2.7 and " waf" intermittently hang on build/installation X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Jan Mikkelsen List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 01:10:02 -0000 The following reply was made to PR ports/163467; it has been noted by GNATS. From: Jan Mikkelsen To: koobs@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: ports/163467: lang/python27: Ports using python 2.7 and "waf" intermittently hang on build/installation Date: Thu, 24 Oct 2013 11:55:48 +1100 Hi, I do not see this problem in our current 9.1 and 9.2 based builds. Regards, Jan. On 24 Oct 2013, at 11:49 am, Kubilay Kocak wrote: > Hi Jan, > > Are you still experiencing this issue? I note that the PR you mentioned, > ports/160717 was followed-up in May 2013 and closed in June.