Regression in working copy logic?

Doing an update with svn trunk (r5971) on one of my repositories yielded:

% svn up
svn: No such file or directory
svn: could not save file
svn: svn_io_file_open: can't open `.svn/tmp/text-base/myfile.svn-base'

(the myfile changed in the repository)

It's apparently because the .svn/tmp/text-base, .svn/tmp/prop-base,
.svn/tmp/props, .svn/tmp/wcprops directories were missing from my working
copy. Explicitly mkdir'ing them fixes the problem and all is well. (Deleting
them in your working copy will reproduce this whenever a file is updated.)

But, I never touched this .svn directory, so I'm wondering if it's possible
that at one point, the svn client didn't create them. This working copy was
created a long time ago. However, fresh checkouts seem to create these
directories.

Wouldn't it be nice to be a bit more graceful in this situation if indeed
older clients never created these directories in .svn/tmp? If so, I can come
up with a patch that detects this scenario and creates the directories. (In
fact, I'll come up with it anyway right now.) -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 19 07:30:31 2003