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

Re: svn assertion

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2006-01-30 14:07:24 CET

On Sun, 29 Jan 2006 kfogel@collab.net wrote:

> Carlo Kok <ck@carlo-kok.com> writes:
> > I have an older checkout done by rapidsvn that has entries with urls
> > like:
> >
> > url="svn://buurtnet/projects/trunk/" ;
> >
> > svn 1.3 seems to give runtime assertions when I execute:
> >
> > svn status -Nu
> >
> > in such a directory.
> >
> > Assertion failed: is_canonical (base, blen), file
> > C:\Home\brane\src\svn\releases\subversion-1.3.0\subversion\libsvn_subr\path.c,
> > line 114
> >
> > Having to fix this in each and every directory is quite a hassle, would
> > it be possible for SVN to just accept this and strip of the ending slash?
> I'm a little leery of having SVN silently clean up bad data in the
> working copy administrative area. Not that this data is fatally bad,
> but it's not something SVN would have written, and presumably modern
> versions of RapidSVN wouldn't write it either. The working copy
> metadata is pretty sacred stuff; better to be strict than loose about
> it, that way we can detect it when tools start to stray.
OTOH, assert isn't the best input validator either:-) We need to validate
the entry when we read it from disk. (And RapidSVN needs to learn to not
throw invalid paths at our APIs.)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 30 14:10:21 2006

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.