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

Re: Working directory not locked (on commit) - 0.21.0

From: <rbb_at_rkbloom.net>
Date: 2003-05-01 20:22:17 CEST

On Thu, 1 May 2003, Jens B. Jorgensen wrote:

> Philip Martin wrote:
> >"Jens B. Jorgensen" <jens.jorgensen@tallan.com> writes:
> >
> >>Philip Martin wrote:
> >>
> >>>"Jens B. Jorgensen" <jens.jorgensen@tallan.com> writes:
> >>>
> >>>>jbj1@tallan2 /d/src/c++/pkcs11
> >>>>$ svn commit -m 'foo!'
> >>>>svn: Working copy not locked
> >>>>svn: Are all the targets part of the same working copy?
> >>>>svn: directory not locked (d:/src/c++/pkcs11)
> >>>>
> >>>>
> >>>I suspect that the problem is the difference between the strings
> >>>"/d/src/c++/pkcs11" and "d:/src/c++/pkcs11".
> >>>
> >>>
> >>Well, I checked out the repository just as file:///svn/c++/pkcs11.
> >>
> >It's not the URL that matters, this is a working copy path problem.
> >
> >>The /d/src/c++/pkcs11 just shows up because I have d: "mounted" as
> >>/d for cygwin purposes.
> >
> >I don't know anything about cygwin, but Subversion uses paths to key
> >into a hash table. If the same path shows up in two different forms
> >it could produce your error.
> >
> Here's the command I used to create the repository:
> svnadmin create svn
> Here's the command I used to import the source:
> svn import -m 'initial version' file:///svn pkcs11new c++/pkcs11
> Basically I have d:/svn as my repository and I have my code under
> d:/src. All the commands have been run with a current working directory
> in d:. Is there somewhere I could check for pathname mismatches? I don't
> see anything suspicious in .svn/entries. I put the file up here:
> http://www.ultraemail.net/~jbj1/entries.zip
> With respect to rbb@rkbloom.net's comment about cygwin/windows
> difficulties I am aware of the potential problems using cygwin in
> windows. I don't think that I ever specified either d: or /d in any
> pathnames to any svn command through this whole thing (the repository
> was created and all subsequent commands run all in the span of
> yesterday). Not having specified either d: or /d anywhere I'm not sure
> where any other difficulties could have come in. Is there something I
> could take a look at?

If I had to hazard a guess, this is a conflict between APR and something
that SVN is doing natively. My guess (and it is a guess), is that SVN is
trying to get the current directory, and it is also using APR to convert a
directory to an absolute path. Because APR was compiled for native
Windows, it is returning d:\...., but svn is getting /d/.... from cygwin.

Of course, that is a complete guess, without looking at any of the
offending code. I am not even sure that svn is getting a path without
going through APR. All I can tell you, is that APR should _never_ be
returning a /d/... path on Windows, unless it was compiled in a cygwin


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 1 20:07:43 2003

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.