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

Behavior Question

From: Paul DeMarco <paul_at_pauldemarco.com>
Date: 2004-12-22 18:19:05 CET

Note sure if this should have done what it did, or what.

I had a local wc with changes, checked out from

Then the server was reconfigured to have the url be:
    - apache was changed to use svn parent directory, and the physical
repository folder was changed to xweb
    - DEVSecure used to be a folder in the repo, the contents of that
folder (trunk tags branches) were moved up a level
    - DEVSecure was removed
    - xweb is not a rename of DEVSecure in the repo, it is infact the
repository name in a folder of multiple repositories

ie the old repository had contents of:

the new repo just has:

On my local wc, I failed to connect (of course), so then I performed a
relocate to: "http://machine/svn/xweb/trunk"
Although it still failed to work properly, giving PROPFIND failures. I
ended up creating a diff off my wc, checking out a new wc, applying the
diff and committing it.

My main question is, i dont know what screwed it up the server url
change, or the repository-side folder change. I thought SVN did
versioned moves. So wouldn't performing the relocate, be enough?

Thinking back I now wonder if I should have done the relocate to
"http://machine/svn/xweb/DEVSecure/trunk", so that the move from
DEVSecure/trunk to trunk would have been recognized by the svn
client.... what is the correct method of handling this?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 22 18:21:36 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.