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

Re: Subversion 1.5 beta1, "malformed URL for repository"

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Thu, 28 Aug 2008 11:27:39 +0100

On Wed, 2008-08-27 at 23:51 -0500, David Huang wrote:
> Hyrum K. Wright wrote:
> > This isn't a solution to the problem, but the 1.5.2 error message for this
> > problem will have additional information which will help the developers fix this
> > issue. Thanks for your patience!
> >
> I applied just that patch (the change to session.c in r32751) to my copy
> of the 1.5.1 source and got:
> C:\ACCTivate\64>svn merge -c 21582 https://dev.alterity.com/svn/ACCTivate
> svn: URL
> 'https://dev.alterity.com/svn/ACCTivate/Installers/Projects/ACCTivate
> CIMS Cumulative Update' is malformed or the scheme or host or path is
> missing
> The problem seems to be the spaces in the path; I'm guessing they should
> be escaped?

Excellent. Now we're getting there.

I'm sorry but I can't dig into this much more right now. David, if you
managed to re-build Subversion from source, it sounds like you are a
person who might be able to help debug this. Would you be willing to
have a go?

If you can't spend much time on it, putting a breakpoint there and
showing us the call stack might be useful. Otherwise, a reproduction
script to create a small repository that exhibits the problem would
definitely be useful, as we could turn that into a regression test.

- Julian

> I recently did an "svn copy" from that URL to the branch
> (https://dev.alterity.com/svn/branches/6.4/Installers/Projects/ACCTivate
> CIMS Cumulative Update), and now that I think about it, this is the
> first time I've tried to merge to branches/6.4 since doing that copy.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-28 12:28:04 CEST

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

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