>> The problem was that the svn upgrade command is case sensitive on the WC >> folder name and failed if the >> name doesn't match exactly. Windows itself is case insensitive and none of >> the other svn commands are >> case sensitive to the WC folder name. > >That is correct. The Subversion client, and a Subversion repository, are >always case-sensitive, >regardless of whether your local filesystem is case-sensitive or not. I don't >believe this is considered >a bug. So be careful to specify things with the >correct case.
2 points: 1. I'm aware the repository itself is case sensitive, but all the other svn XXXX commands are case insensitive for the WC name, so "svn upgrade" isn't working consistently with them 2. the reported error is misleading and meant spending several hours investigating why the working copy couldn't be upgraded. (Which is the reason for testing with beta releases) If it's not a bug, then a an more appropriate error message would be an improvement.
