On 3/9/07, Scott Hendrickson <email@example.com> wrote:
> I have an svn repository that was recently moved to a different
> server. A user who had previously checked out a folder within the
> repository was unable to relocate their copy to this new server. They
> kept getting the following error:
> PROPFIND request failed on '/svn/repository'
> PROPFIND of '/svn/repository': 403 Forbidden ( https://domain.name )
> They were able to check out a fresh copy from the new repository, but
> were not able to relocate their old copy to it.
> After looking in to this (and doing a little testing) It appeared that
> the user could not relocate the repository unless they had permission
> to read and write (possibly just read -- I only tested with both read
> and write) access to the root of the repository. When I added them as
> having rw permission in [/], they could relocate the repository
> without any problems. I've attached some (shortened) configuration
> files and log messages below. Hopefully they will help. Of note,
> notice that the error.log file shows them trying to access PROPFIND on
> repository:/ when they were relocating a subfolder within it.
What was the exact command they were using to do the relocate in the client?
Were they just doing relocate against the repos root or the directory
where their WC was based? i.e. 'svn switch --relocate http://foo/svn/
http://bar/svn/' versus 'svn switch --relocate
http://foo/svn/some/folder/ http://bar/svn/some/folder/'? I'd expect
the former to likely fail in that authz config, while the second
Note, on a switch --relocate, the client will try to discover the
repos root to ensure the UUIDs are the same as what it used to be.
Another option is to --force the relocate - that should disable the
UUID check - it's a bit unsafe, but it would circumvent them from
needing to do a PROPFIND on the root of the repository. -- justin
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Mar 14 05:12:28 2007