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

RE: svnsync failure

From: <Terekhov_mikhail_at_emc.com>
Date: 2006-10-23 20:48:51 CEST

> -----Original Message-----
> From: rooneg@gmail.com [mailto:rooneg@gmail.com] On Behalf Of Garrett
> Rooney
> Sent: Monday, October 23, 2006 1:43 PM
> To: Mikhail Terekhov
> Cc: users@subversion.tigris.org
> Subject: Re: svnsync failure
> On 10/20/06, Mikhail Terekhov <terekhov@emc.com> wrote:
> > Hi,
> >
> > I'm using svnsync to mirror our repository and all was fine, but
> > recently svnsync started to fail with the following message
> >
> > svnsync: REPORT request failed on
> > svnsync: REPORT of 'https://svn.myserver.com/myproject': 200 OK
> > (https://svn.myserver.com)
> >
> > There was no any config changes as far as I can see. Server is a Sun
> > machine and the client is a Linux box. Both have 1.4.0 (r21228)
> installed.
> >
> > Any ideas what could be the reason?
> Interesting. Is there anything odd about the revision it's trying to
> mirror when it hits that error? A 'svn log --verbose -r X' where X ==
> that revision would be interesting. Alternatively, it might be useful
> to see a neon debug trace from that operation. As a final resort, in
> the current trunk version of subversion the error message you'll get
> from that sort of situation will be far more useful (i.e. no "200 OK"
> crap), so you could rebuild with trunk and try it again and see if
> that gives you something more meaningful.

The repository is small, so it is relatively easy to experiment. I've
dumped offending revision (359), loaded it into destination repository
and svnsync became happy again.

The revision in question is very simple - it is just a one file rename.
User (on Windows box & svn-1.3.2) renamed file with a space in the name:
"some%20name.ext" --> "some name.ext".

It is strange but 'svn log --verbose -r 359' says nothing, just a single
line of dashes (both 1.4.0 and trunk versions).

Svncync from the trunk gives the following error:

svnsync: REPORT request failed on 'https://svn.myserver.com/myproject'
svnsync: File not found: revision 358, path '/my/path/some name.ext'

Why 358? The file was created in rev. 230 and never changed since.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 24 16:27:36 2006

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.