From owner-freebsd-ports@FreeBSD.ORG Tue Jun 3 13:15:51 2014 Return-Path: Delivered-To: freebsd-ports@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 ESMTPS id 0EE28817 for ; Tue, 3 Jun 2014 13:15:51 +0000 (UTC) Received: from zion.christianserving.org (zion.christianserving.org [66.128.242.154]) by mx1.freebsd.org (Postfix) with ESMTP id D93A628B6 for ; Tue, 3 Jun 2014 13:15:50 +0000 (UTC) Received: from zion.christianserving.org (localhost.christianserving.org [127.0.0.1]) by zion.christianserving.org (Postfix) with ESMTP id 874BA2879A0; Tue, 3 Jun 2014 08:15:49 -0500 (CDT) X-Virus-Scanned: amavisd-new at christianserving.org X-Spam-Flag: NO X-Spam-Score: -1.107 X-Spam-Level: X-Spam-Status: No, score=-1.107 tagged_above=-9999 required=6 tests=[BAYES_00=-1.9, RDNS_NONE=0.793] autolearn=no Received: from mm-riggsj-9.peace.daveramsey.com (unknown [198.52.26.32]) by zion.christianserving.org (Postfix) with ESMTPSA; Tue, 3 Jun 2014 08:15:47 -0500 (CDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Segfault while checking out port tree with devel/subversion From: Jim Riggs In-Reply-To: <20140603.215915.206199362.yasu@utahime.org> Date: Tue, 3 Jun 2014 08:15:50 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <14929937-3701-4A6C-8551-39AC6B377E6A@christianserving.org> References: <20140603.215915.206199362.yasu@utahime.org> To: "freebsd-ports@freebsd.org" , Yasuhiro KIMURA X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 13:15:51 -0000 On 3 Jun 2014, at 07:59, Yasuhiro KIMURA wrote: > Hello, >=20 > I get segmentation fault while checking out port tree with > devel/subversion. >=20 > ... >=20 > Does anyone experienced this? Yes, we are seeing the same thing, but a single cleanup doesn't always = work for us. Sometimes we have to go through several svn = up-cleanup-up-cleanup-... iterations to get an up-to-date ports tree. = See this thread also: http://lists.freebsd.org/pipermail/freebsd-ports/2014-May/092269.html