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

Too early svn up/co abort if one item of svn:external resource list is not accessible

From: Achim Spangler <Achim.Spangler_at_mnet-online.de>
Date: Wed, 26 Mar 2008 21:16:30 +0100

in my project http://www.isoaglib.org, we use svn:external properties to
achieve access control for parts of an anonymous accessible repository.

We have several "svn:externals" properties distributed over some directories,
so that a "svn co" or "svn up" sequence is finished with a list
of "svn:externals" retrievals.

Some users have only access right for a subset of
the "svn:externals"-connected resources.

Example Structure:
| |
| -- dir1 - external1
| |
| -- dir1.2
-- dir2 - external2
    -- dir2.2

User FOO has only access right for external2.

Problematic current (Version: 1.4.3) SVN behaviour:
svn co/up aborts as soon as the first resource is not accessible, so that the
later defined svn:externals are not even tried.
In example: User FOO does not get access to external2, as svn up/co aborts at
            external1 due to missing access rights.

Wanted behaviour:
Each svn:externals should be tried, and all unsuccessful entries should be
reported at the end.
In example: User FOO should get checkout and update including external2, and
            a final report should state failed access to external1

This is from my understanding a svn-client problem.

1) Has this been fixed since Version 1.4.3?
2) Is there some reason for the current behaviour?
3) Am I the only user with such a setup?
  ( I found already some comparable results - but not yet any response or
    plan for solving of this issue )


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-26 21:16:41 CET

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