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

Re: [TSVN] revision graph failure /cvs2svn failure was: Re: dev Digest 17 Jun 2005 15:51:22 -0000 Issue 802

From: Johnathan Hegge <jhegge_at_permeo.com>
Date: 2005-06-21 21:21:41 CEST

On Tue, 2005-06-21 at 12:17, SteveKing wrote:
> Johnathan Hegge wrote:
> >>Can you please try the command line client and do an
> >>svn log -v
> >>on the same file/folder you show the log in TSVN?
snip
> >
> >>If the same error occurs, you should ask for help on the corresponding
> >>mailing list (cvs2svn or the Subversion mailing list).
> >
> >
> > The error doesn't seem to occur at the command line, if I'm correctly
> > duplicating it.
>
> Sorry, I told you to do the 'svn log -v' on the file, but you should do
> it actually on the repository root (where /trunk, /branches, /tags is
> located)

Okay, your original idea is correct, revision graph is merely stumbling
on an error in the repository related to a cvs2svn issue:

>This commit was manufactured by cvs2svn to create branch 'test_branch'.
>svn: REPORT request failed on '/svn/!svn/bc/3047'
>svn: The REPORT request returned invalid XML in the response: XML parse
>error at line 51373: not well-formed (invalid token)
>(/svn/!svn/bc/3047)

This message at least shows the actual creator was cvs2svn. I thought,
mistakenly, that the 3047 referenced above was a subversion revision
number, it appears to be something else, perhaps dynamic? I've seen
different numbers referred to with the consistent failures.

At any rate, we'll start pursuing this down the cvs2svn list.

Thanks much for the help.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jun 21 21:21:59 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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