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

Re: directory problem on 'svn ci'

From: Ryan Schmidt <subversion-2011a_at_ryandesign.com>
Date: Wed, 26 Jan 2011 09:12:44 -0600

On Jan 26, 2011, at 05:07, Stefan Sperling wrote:
> On Tue, Jan 25, 2011 at 08:28:08PM -0600, Ryan Schmidt wrote:
>>
>>>> I _know_, by sheer evidence of the svn-commit.tmp file being
>>>> "physically" there, that it is created one directory level above where
>>>> it was used to be created!
>>
>> FWIW, on my Mac OS X installation (Mac OS X 10.6.6, SVN 1.6.15), I also notice the svn-commit.tmp is created one directory up, but that appears to be normal for Subversion (now anyway; not sure what used to be normal), and works fine for me.
>
> Can someone take the time to confirm if this has changed from earlier
> versions, and if so, in which version this changed?

I tested 1.6.15, 1.6.4, and 1.6.0, and they all behaved the same, which was:

If I have a working copy /path/to/wc and I am in that directory and I commit, svn-commit.tmp is created in /path/to/wc.

If I am in a subdirectory of that working copy and I commit, svn-commit.tmp is created in the parent directory. For example, if I am in /path/to/wc/foo/bar and I commit, svn-commit.tmp is created in /path/to/wc/foo.

I'm still unclear what problem this behavior is perceived to cause.

Note I did all tests with apr 1.4.2 and apr-util 1.3.10. Perhaps this is an apr or apr-util issue and trying earlier versions of those would produce different results. Andreas, do you know what versions of apr and apr-util you have now, and what versions you had before?
Received on 2011-01-26 16:13:36 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.