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

Re: [TSVN] Problems committing a file: "Kann Sperre für Pfad 'f/q/p/to/the/file' nicht prüfen; keine entsprechende Sperrmarke verfügbar."

From: <Lion.Gutjahr_at_escatec.ch>
Date: 2005-10-11 12:52:27 CEST

Stefan Küng <tortoisesvn@gmail.com> wrote on 11.10.2005 11:31:31:

> On 10/11/05, Lion.Gutjahr@escatec.ch <Lion.Gutjahr@escatec.ch> wrote:
> > > Can you perhaps provide some recipe on how I could reproduce the
> > I don't know what i did to put the repo in this state. The only
troubles i
> > had were that the pathnames i initially imported while creating the
> > were too long and TSVN wasn't able to do the job. I did that step
> > with the cmd line client which accepts the MS "\\.\"-notation and
> > succeeded.
> Here's your problem. While TSVN failed correctly, the CL client did
> not. But you see, neither TSVN nor the CL client really support the
> \\.\ notation (i.e. paths longer than 250 chars). Well, even though
> the CL client technically could (TSVN can't because the shell/explorer
> can't either, so TSVN is limited by that), it doesn't really support
> it. In fact, you'll get some nasty error messages.
> Why is that you might ask - well, the Subversion library (and apr too)
> uses the windows define MAX_PATH in several places to reserve memory
> for paths, and MAX_PATH is defined to 260. So whenever you're dealing
> with paths longer than 260chars, the Subversion library either cuts
> the paths or triggers a buffer overflow...
> The only solution for this kind of problem:
> then access your working copy from X:\
Right after i created the repos, I had these troubles with the long
pathnames, but these were solved with the import done from cmd line
(without errors).
Subst works fine and i'm using it for quite a long time to solve other
issues like the above. But there are much longer paths in the same working
copy from the same repo and they work without any problems. So i think this
isn't the reason why the error "...Sperrmarke..." occurs (actually, the
path/to/the/file we're talking about is about 100 chars in size).
I never had to use workarounds like "\\.\" or subst again in this repo
after the successful import and accessed it only through tsvn.

Are there some consistency check tools availably which go beyond what "svn
cleanup" does?

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Oct 11 12:52:29 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.