[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnsync on large files

From: Daniel Shahaf <danielsh_at_apache.org>
Date: Wed, 7 Dec 2016 22:08:39 +0000

Pavel Lyalyakin wrote on Wed, Dec 07, 2016 at 20:59:24 +0300:
> On Wed, Dec 7, 2016 at 8:54 PM, Stümpfig, Thomas
> <thomas.stuempfig_at_siemens.com> wrote:
> >
> > The rev to be synced is 2,291,973,385 Bytes large (Size in txn-protorevs directory. Of target mirror)
> >
> > The sync is with svn 1.9.5 (Visual SVN Server) over both https
>
>
> You should use file:/// access to the local repository instead of
> HTTP(S).

Why? There are perfectly good reasons to use http://localhost/, for
example, to have a one-stop-shop killswitch for disabling "everything"
from accessing the repository.

I'm guessing the dump/incremental-load/update-r0-revprops surgery went
wrong. I would (a) double-check that the revision that had been
manually synced did in fact sync correctly, (b) review the r0 revprops.
(Thomas: you can just post the 'proplist -v' here if you aren't sure
whether it's correct now.)

Also, as Pavel says, we need the full error message.

Cheers,

Daniel

> Here is an example:
> [[[
> svnsync sync "https://svn.example.com/svn/MyRepo"
> "file:///C:/Repositories/MyRepo/"
> ]]]
>
> Does the error occur when you use file:/// access to local repository?
>
> > I tried to rdump, svnadmin load incremental (works) and adjust
> > revprop info in rev 0 to the new imported files. But the I got
> > a path already exists for following syncs. Might not be related to
> > my manipulations but could be the case.
Received on 2016-12-07 23:08:54 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.