From owner-freebsd-python@FreeBSD.ORG Sat Apr 12 12:30:01 2014 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 ESMTPS id 5C5978D8 for ; Sat, 12 Apr 2014 12:30:01 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49E371214 for ; Sat, 12 Apr 2014 12:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3CCU1rj044530 for ; Sat, 12 Apr 2014 12:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3CCU1Fi044529; Sat, 12 Apr 2014 12:30:01 GMT (envelope-from gnats) Date: Sat, 12 Apr 2014 12:30:01 GMT Message-Id: <201404121230.s3CCU1Fi044529@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Kubilay Kocak Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST files X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Kubilay Kocak List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2014 12:30:01 -0000 The following reply was made to PR ports/188431; it has been noted by GNATS. From: Kubilay Kocak To: bug-followup@FreeBSD.org, antiduh@csh.rit.edu Cc: William Grzybowski Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST files Date: Sat, 12 Apr 2014 22:24:17 +1000 Kevin, Please note that you do *not* need to run the reproduction steps listed above, and only need to provide the output of the ls -la command above. We are interested in the contents of your Python 2.7 site-packages because we have a theory as to what the cause is based on isolation tests we have run on another users installation that is exhibiting similar symptoms