Topic: subversion issues when updating
fwiw, a word of warning: if you have a rails project under svn, be sure that you do *not* have the log, script, and tmp folders under repository control. And think twice about your vendor folder, you may want to exclude it, also.
I'm three days post-upgrade to ruby18.104.22.168/gem09.2/rails1.2.2, and am still in a serious pickle because of the above -- no problems working with the project, but svn is taking such good care of its data that i still haven't figured out how to get it working again (tortoise client).
Things are locked/obstructed and clean-up fails -- and now svn claims my apps folder is "not a working copy directory".