Trevor - 2014-06-30

We ran in to this at my company as well. We just migrated from svn 1.6 to 1.8. I came up with basically the same fix, but i called svn info on the $f instead of $dirname (which is probably slightly better, since it will give you the proper error message if the directory is under svn control but the file is not):

-    } elseif {! [catch {eval "exec svn info"}]} {
+    } elseif {! [catch {eval "exec svn info $f"}]} {