Problems updating to WordPress 2.8 using SVN

If you’re like me, you run your WordPress installation off of a SVN checkout, making it far easier to stay up to date with new versions. In fact, using version control checkouts is an excellent way to maintain web applications running on production servers, especially if they don’t require compilation.

However, if you recently tried to upgrade to the latest version using the instructions at the WordPress Codex, you likely ran into a problem with an error mesage like this:

$ svn sw . 
svn: ''
is not the same repository as

This is because sometime between the release of 2.7.1 and 2.8, the URL of the WordPress SVN repository changed from to


Protecting SVN metadata folders on a web server

I recently changed my WordPress install over to an SVN checkout in order to get rid of the tedious steps required to upgrade every time a new version is released.

Thankfully, following the well-written guide on the Codex was easy and straightforward – both for changing this existing installation over to SVN and for setting up a new blog for RunTrackr. I now look forward to updates, just so I can relish in the ease of upgrading. 🙂 Continued