Date: Tue, 4 Apr 2017 13:20:30 -0700 From: Mark Millard <markmi@dsl-only.net> To: bob prohaska <fbsd@www.zefox.net> Cc: Otac??lio <otacilio.neto@bsd.com.br>, freebsd-arm@freebsd.org Subject: Re: svn: E175003: Attempt to fetch capability 'depth' resulted in 'yes' Message-ID: <DD18F4F3-5123-43B2-BBE2-E7D52B340878@dsl-only.net> In-Reply-To: <20170404160947.GA82658@www.zefox.net> References: <20170310184210.GA38002@www.zefox.net> <26fa7189-fd35-cdb4-ccfc-5ba623be9e59@zyxst.net> <e5d21dab-0ebb-e48d-effe-ba3b855c9d3b@bsd.com.br> <20170404160947.GA82658@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Apr-4, at 9:09 AM, bob prohaska <fbsd at www.zefox.net> wrote: > On Tue, Apr 04, 2017 at 09:30:01AM -0300, Otac??lio wrote: >> Em 04/04/2017 09:21, tech-lists escreveu: >>> On 10/03/2017 18:42, bob prohaska wrote: >>>> After a successful build of >>>> FreeBSD 12.0-CURRENT (RPI2) #5 r314923: Fri Mar 10 09:03:07 PST 2017 >>>> >>>> the next attempt at updating sources produced: >>>> >>>> svn: E175003: Attempt to fetch capability 'depth' resulted in 'yes' > [snip] > >> I'm getting the same error with a beaglebone black running HEAD r315864. >> The workaround was install devel/subversion from packages and run svn >> instead svnlite. >> > > I ended up doing the same thing on RPI2, but also changed from https > protocol to svn protocol. It's beginning to look as if the use of svn > protocol is what fixed it, not the use of svn versus svnlite. I'd had problems with https/http for some time and so a while back I tried svn protocol instead and the problems stopped. I only used svnlite, not installing svn from ports at all. === Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DD18F4F3-5123-43B2-BBE2-E7D52B340878>