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

Moving children without repo root access

From: Josh Cepek <josh.cepek_at_usa.net>
Date: Tue, 02 Jun 2009 16:30:56 -0500

I've run into a problem performing a 'svn mv' operation on 2 URLs
through Apache when committing as a user with access to a common parent
directory but not the repository root. This results in a response from
the server as follows:

svn: Server sent unexpected return value (403 Forbidden) in response to
PROPFIND request for '/svn/testrepo'

As a workaround, the common parent directory (where the limited user
does have access) can be checked out with a limited --depth option, the
move performed, and then checked-in. However, this adds complexity, and
is counter-intuitive for someone expecting access to perform the move.

I've attached a testcase1.sh that provides an example of this, and
testcase2.sh showing the workaround I mentioned. These test cases
assume the Apache configuration has been set up in a working
environment, that the /somdir path doesn't yet exist, and that the repo
is using an authorization file similar to the following:


Outside of the workaround in testcase2.sh, is there a way to make the
move work for server URLs?

If this isn't currently supported (whether it's a bug or expected
behavior) I'd love to see this supported in a future version. Granting
the limited user access to the repo root, even read-access, is not a
workable solution in this case, not to mention the endless headache of
denying access to new sub-projects that are created.

Thanks for any suggestions or comments,

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].

Received on 2009-06-02 23:49:58 CEST

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