From owner-freebsd-arm@freebsd.org Fri Sep 4 21:54:09 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 838059CA061 for ; Fri, 4 Sep 2015 21:54:09 +0000 (UTC) (envelope-from george@ceetonetechnology.com) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (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 4E2E21452 for ; Fri, 4 Sep 2015 21:54:08 +0000 (UTC) (envelope-from george@ceetonetechnology.com) Received: from 127.0.0.1 (25.ip-149-202-63.eu [149.202.63.25]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id t84M8iAj065861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 4 Sep 2015 18:08:53 -0400 (EDT) (envelope-from george@ceetonetechnology.com) Subject: Re: very odd behaviour from svnlite on RPi2 To: freebsd-arm@freebsd.org References: <20150904173804.GA82922@potato.growveg.org> <46ddeb2caa6.2d9e5c4c@mail.schwarzes.net> From: George Rosamond Message-ID: <55EA0FC6.2030607@ceetonetechnology.com> Date: Fri, 4 Sep 2015 17:40:22 -0400 MIME-Version: 1.0 In-Reply-To: <46ddeb2caa6.2d9e5c4c@mail.schwarzes.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2015 21:54:09 -0000 Andreas Schwarz: > On 04.09.15, John wrote: > >> On my newly installed RPi2, I'm trying to install the ports tree. I'm >> running -CURRENT. I usually install and update ports tree on my >> freebsd boxen with the following incantation: >> >> svnlite co https://svn0.eu.FreeBSD.org/ports/head /usr/ports >> >> The problem I'm seeing is variously svnlite bails with the following: > > I got this svn errors from time to time, independently from the rpi. For > getting and updating the ports tree, you can also use the "portsnap" tool > (it's part of the base system). I have had these errors many times before. My assumption is that it's tied to the network driver, although it's been a while since I tested. Have you also tried using svn? Portsnap is definitely the capable workaround, but it doesn't explain the original problem. g