From owner-freebsd-python@FreeBSD.ORG Mon Mar 3 17:09:05 2014 Return-Path: Delivered-To: python@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 A3553225 for ; Mon, 3 Mar 2014 17:09:05 +0000 (UTC) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 95E4CF62 for ; Mon, 3 Mar 2014 17:09:05 +0000 (UTC) Date: Mon, 3 Mar 2014 09:09:04 -0800 (PST) From: Roger Marquis To: python@FreeBSD.org Subject: python27-2.7.6_4 install failure User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2014 17:09:05 -0000 Is there a patch or mitigation for this 8.3-RELEASE- install bug? Couldn't find a useful reference to 'lib/python2.7/lib-dynload/bz2.so' on the net. Thanks, Roger Marquis > > Building package for python27-2.7.6_4 > Creating package /usr/ports/lang/python27/work/python27-2.7.6_4.tbz > Registering depends:. > Creating bzip'd tar ball in '/usr/ports/lang/python27/work/python27-2.7.6_4.tbz' > tar: lib/python2.7/lib-dynload/bz2.so: Cannot stat: No such file or directory > tar: Error exit delayed from previous errors. > pkg_create: make_dist: tar command failed with code 256 > *** Error code 1