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

Nested working copies in SVN 1.7.x+ question

From: Vladimir Berezniker <vmpn_at_hitechman.com>
Date: Sun, 23 Dec 2012 21:35:12 -0500

Hi All,

I ran into some issues with SVN tests for JavaHL, as test WCs end up
nested within the branch WC. So I am curious to understand what the
official stance is, are nested working copies a supported use case?

If this use case is supported please find below a theoretical
problem(s) I mention it in case it does mater to someone, but I am not
sure how much this affects real users:

If there is a parent folder with .svn folder the nested checkout can
fail if the parent folder is inaccessible, corrupt, etc.

Example to illustrate:

mkdir test
cd test
svn co http://heimdall-one-click.googlecode.com/svn/trunk/HeimdallOneClick
--depth empty . (this could be any valid repo URL)
chmod 0 .svn (simulate problem with parent .svn folder)
mkdir sub1
cd sub1
svn co https://svn.apache.org/repos/asf/subversion/branches/javahl-ra
--depth empty .

Error is raised:

svn: E000013: Can't check path '<censored>/test/.svn/wc.db': Permission denied

Even though there is unrelated checkout in a child folder, it is
affected by state of the parent. IMHO would having the means of
telling SVN the boundary after which it should not keep looking for
.svn admin folder and/or explicit WC admin folder path parameter be
sensible? I could not find any such options in my cursory search.

P.S. I noticed this issue in the process of bringing javahl-ra branch
up to date with trunk. At some point running make check-javahl caused
the working copy to be upgraded and no longer accessible by svn 1.7.7.
 I know that in later commits auto upgrades got disabled so as soon as
I reach them this will be a mute point, but as I mention above, other
variation can still occur.

Regards,

Vladimir
Received on 2012-12-24 03:35:49 CET

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.