[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: Jens B. Jorgensen <jens.jorgensen_at_tallan.com>
Date: 2003-05-01 21:59:06 CEST

Philip Martin wrote:

>"Jens B. Jorgensen" <jens.jorgensen@tallan.com> writes:
>>Is there something I could take a look at?
>If you mean you want to debug the problem then you need to determine
>which path gets passed to do_open() in libsvn_wc/lock.c when opening
>an access baton for the directory. The access batons are opened when
>svn_client_commit in libsvn_client/commit.c calls svn_wc_adm_open
>(line 767). Several access batons may be opened, but one should be
>for the directory in question and that path becomes the hash key.
>When svn_client_commit attempts to retrieve the access baton using
>svn_wc_adm_probe_retrieve (line 780) it fails. (At least I am
>assuming that's what happens, but it's really just a guess, until
>someone tracks down the problem we won't know for sure.)
>From the error message it appears that the retrieve call uses the "d:"
>path, which was returned by svn_path_get_absolute. I don't know why
>or how do_open would get the "/d/" form (if it does), but the path
>appears to come from svn_path_condense_targets which also uses
Ok, I'll bit. I have a working copy of svn plus I've built apache and
Berkeley_DB. The build instructions claim existence of a
subversion_msvc.dsp/w to build it. I can't find this there. Could
someone give me some guidance as to the best way to get my build to
happen with vc++. I'm getting a sneaking suspicion it involves cygwin.
Is this correct?

Jens B. Jorgensen
"With a focused commitment to our clients and our people, we deliver value through customized technology solutions"  
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 1 21:59:46 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.