[svk-devel] svk 2.0.1rc1 is released. (Spaces bug still there)

Mark Grimes mark at stateful.net
Sat Mar 24 03:22:39 EDT 2007


For the record here's yet another repository that craps out:

Syncing http://source.colloquy.info/svn/trunk
Retrieving log information from 2764 to 3633
Bad URL passed to RA layer: Malformed URL for repository

I'll stop itemizing though, as there are *many*, but the initial three 
should demonstrate how plentiful they are as at least two of them are 
high profile osx projects.

-Mark

On Fri, 23 Mar 2007 10:17:20 -0700, Mark Grimes wrote:
> - SVN::Mirror               ...loaded. (0.730 >= 0.71)
> But the problem is still there.
> 
> CLK: Here's a brief history of the problem and is why I refer to it as 
> a spacing problem:
> 
>> From Viktor Štujber on 02/01/2007:
>> Bad URL passed to RA layer: Malformed URL for repository 
> ('https://svn.binaervar
>> ianz.de/kismac/KisMACng/Resources/Help/English.lproj/KisMAC Help')
>> 
>> Looks like it's really a space/escaping problem. We'll see what clkao
>> has to say about this.
>> 
>> From Viktor Štujber on 01/31/2007:
>> This is the full message (after I modified svn/libsvn_ra_dav/session.c):
>> 
>> Bad URL passed to RA layer: Malformed URL for repository
>> ('http://svn.toxicsoftware.com/public/trunk/Freeware/Python Metadata
>> Importer/Packaging/Installer/Scripts')
>> 
>> It might be that svn doesn't like unescaped spaces in the path, or
>> something else.
>> You can breakpoint neon's ne_uri_parse() (neon/src/ne_uri.c).
> 
> -Mark
> 
> 
> On Fri, 23 Mar 2007 10:56:07 +0000, Chia-Liang Kao wrote:
>> Hi,
>> 
>> On 23/03/07, Mark Grimes <mark at stateful.net> wrote:
>>> Spaces in pathnames on sync are still broken.  I was under the
>>> impression this was fixed in trunk but confirmed that it remains broken
>>> in 2.0.1rc1.  This is a *big* problem as basically most Cocoa developer
>>> repositories which represent a majority of work at least on the Mac OS
>>> X operating system are unusable with SVK, but works with Subversion.
>> 
>> I think the fix is in SVN::Mirror in your particular case, as the
>> server doesn't seem to be 1.4 and supports replay.  Could you try
>> upgrade SVN::Mirror to 0.73 and see if it works better?
>> 
>> Cheers,
>> CLK
>> _______________________________________________
>> svk-devel mailing list
>> svk-devel at bestpractical.com
>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel
> _______________________________________________
> svk-devel mailing list
> svk-devel at bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel


More information about the svk-devel mailing list