WordPress has a great and constantly up-to-date wiki for administrators to manage WordPress installations via SVN. Every time a release is made, I just search google for “wordpress svn sw” and copy the svn sw link over to my terminal.
But recently they changed the repository URL — which means anyone using the old URL will get the following error when they try to update (assuming they are using the svn sw command):
svn: 'http://core.svn.wordpress.org/tags/2.8'
is not the same repository as
'http://svn.automattic.com/wordpress'
The fix for today’s (2.8) release is easy (replace 2.7.1 with whatever you were previously using):
svn switch --relocate http://svn.automattic.com/wordpress/tags/2.7.1 http://core.svn.wordpress.org/tags/2.7.1/ .
Then just do your normal:
svn sw http://core.svn.wordpress.org/tags/2.8/ .
It’s not hard to fix, but I’m not an avid user of SVN. So every time I do an update (assuming the repo URL has changed), I have to look at svn help and remember the syntax for changing repositories. Now, since I wrote this, I won’t need to. Perhaps this helped you too!
Thanks for posting this fix! Relocating svn repositories isn’t something I do every day either, and your post really helped!
Thanks, the error had me worried for a moment!
Hey, thanks! I do the same thing… google svn wordpress. I had remembered it being at automattic and when I saw the new location, I knew it was going to cause an error. Thanks for writing up the post. I don’t know why it isn’t on the official wordpress svn docs.
Ha! I forgot about the –relocate switch, I did it the hard way zapping the .svn directories
Thanks for the quick tip. You’re number one on google
Actually when i ran into this problem i manually forced the old repo URL (still active, just points to the new one) and it worked fine. But I’m not sure they’ll keep it up forever so this is a good guide!