You can’t switch from one repository to another. You will have to check out WordPress 3.0 and overwrite your MU svn.
Haven’t tried this yet as we’re waiting until 3.0.x but you need to add in the –relocate flag:
http://www.svnforum.org/2017/viewtopic.php?p=28686&sid=9bf569ce02af1ffd6a0ddcf286be0f5e
edit: Unless Andrea’s Hubby is right of course. Like I said, I haven’t tried it yet.
tdjcbe: no, as I say I tried
svn sw --relocate http://svn.automattic.com/wordpress-mu/tags/2.9.2/ http://core.svn.wordpress.org/tags/3.0/
and it comes back with the same UUID error.
Ron R: thanks, so I need to move all the user specific directories e.g. blogs.dir, themes, plugins etc to a safe place (wp-config.php is already one level up) and then:
svn co http://core.svn.wordpress.org/tags/3.0 .
Then move those directories back, right?
You should be able to just checkout on top of the install without moving anything. If SVN still gives some error, I would just delete all the SVN data in the directory where you have WPMU installed and then checkout. You can use something like this to delete the svn data (basically just hidden .svn folders):
find /home/yoursite/public_html -name ".svn" -type d -exec rm -rf {} \;
Thanks Mr Brian. But surely if I just checkout on top of the existing install, it will overwrite the wp-content directory with all my plugins and blogs.dir etc?
Interesting idea though to just delete the hidden .svn directory. I can get to that no probs. Presumably than I just do a svn switch to update to version 3?
OK, well I thought I’d report back as to my mind, this is a serious pain in the… Everyone around the web is saying, “Oh just use the relocate command” or glossing over the actual nuts and bolts of doing an SVN upgrade from 2.9.2 to 3.0, but this is all BS. I’m sure there’s some very good technical reason why subversion fails when upgrading from 2.9 to 3.0, but it aint very considerate.
Anyway, MrBrian you can’t simply delete the hidden .svn directory and checkout the new code, as during the new checkout, Subversion complains that there are already files of the same name in the location you’re trying to use. So you end up having to delete all the existing files, in any case.
So, the only way I’ve found to do is as per Ron R’s suggestion, that you have to backup the custom directories (themes, plugins etc) and then do a new install. So deleting all the existing files/directories and doing a new CO with the WP 3.0 code.
Which is quite frankly nerve-wracking enough on a development site, let alone on a clients live site.
I’ve only just switched to using Subversion in the past couple of WP releases coz I wanted to get away from having to do exactly this type of procdedure (and having a nice fall-back to a previous release if a something goes screwy in the process). Turns out that at least for this release you gotta go back to manually moving/deleting files, and there’s no going back once you’ve gone to 3.0… 😐
@mrarrow – Sorry, didn’t see your reply. The process you described is correct.
The –relocate flag is used to relocate a SVN to a new URL, but it must be the same SVN repo. A SVN has a GUID and the GUID has to be the same at the new location as the GUID at the old location.
