Troubling SVN Error

There is a somewhat rare subversion error out there, in which you can import files but not add them. This is rather infuriating, as you often add your whole project to source control, work on it for a month, and then try to add a file and find that subversion has just broke. Really, it didn't just break, it was always broken and you never knew it. Googling for the answer won't help (well, maybe it will now), because no one seems to know the answer. But, lucky you! I have your answer!

Here's the situation: you are running a website package (like drupal). This package puts up fancy 404 error pages, possibly sends you to the root page. When you type in http://www.mywebsite.com/this_page_doesnt_exist.html, instead of an ugly "404 Document Not Found", you get a pretty "302 Found http://www.mywebsite.com/404.html", which causes your browser to redirect. This is good for users - people don't get much out of the traditional error message. This is bad for svn - when you say "svn add" and then commit, it says "Hi! This file already exists!", which causes svn to tell you: "svn propfind request failed", "302 Found"... less than useful.

So, you already see the answer now, cunning user: go to your apache subversion config, and add the simple statement: "ErrorDocument 404 default" (and reload apache). Users get pretty errors, subversion gets less confused, you get to add files. Server defenestration averted.

Thats it! You're done! Go and add new files with abandon!