[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: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-10-11 12:55:41 CEST

On 10/11/05, Lion.Gutjahr@escatec.ch <Lion.Gutjahr@escatec.ch> wrote:
> 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).

Well, not all Subversion commands have this restriction.

> 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.

Well, I think it *is* the reason. You see, locking is relatively new
in the Subversion library. And maybe in that part of code there's
still some use of MAX_PATH, where in other parts it isn't used.

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

Nope. Sorry.

Stefan

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
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:56:03 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.