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

Re: Possible SVN Relocate bug

From: Scott Hendrickson <sahendrickson_at_gmail.com>
Date: 2007-03-14 07:39:57 CET

On 3/13/07, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> On 3/9/07, Scott Hendrickson <sahendrickson@gmail.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
> should succeed.

It fails in both cases. It only works if I have read access for root
folder (I just verified that I don't have to have write permission for
it to work -- only read).

> 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.

I bet that's what's going on, that makes sense.

> 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

I don't see a --force option for switch, and it won't accept the
command. Maybe that would be a good feature, though :-)

Thanks for following up on this,
-- Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 14 07:40:12 2007

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