[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-10 18:51:03 CEST

tnx for your quick reply stefan.
quotes r below.

Stefan Küng <tortoisesvn@gmail.com> wrote on 10.10.2005 18:01:46:
> Lion.Gutjahr@escatec.ch wrote:
>
> > "Kann Sperre für pfad 'full/qualified/path/to/the/file' nicht
prüfen;
> > keine entsprechende Sperrmarke verfügbar. If you want to break the
lock,
> > use the 'Check for Modifications' Dialog".
[...]
> > The file is not in the repository yet - neither visible with
repo-browser
> > nor with a 'svn list' from the cmd-line. 'svn-status' shows the file as
not
> > under source control.
> > A cleanup didn't help.
> > There is a lock on each file in the dir. I tried to unlock all before
> > commiting the file which produces the troubles, but this didn't help
> > either.
>
> - If 'svn status' shows the file as unversioned, did you even select it
> in the commit dialog? If you did, it's status should be 'added'.
Yes, it shows the status added.

> - what's the version of the server?
> - what's the version of TSVN you're using?
> - how do you connect to the repository? (http/svn/file/...)
I was using svn 1.2.0 on a WindowsXP/SP2 pc with svnserve running.
TSVN version is 1.2.4.4479.
An upgrade to svn 1.2.3 (made this evening) didn't solve the problem.

> P.S. We now have a users mailing list. Maybe next time you should post
> there.
Tnx. Will do it with the next question but will continue this one here just
to hold the history together.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 10 18:52:32 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.