[This is intended as a bug report...]
In my repository, I have one file which is a symbolic link used only in
builds for other machines. It is, of course, checked out with the rest
when I use svn commands on Microsoft Windows, but appears as a normal
file.
The svn export command fails when it gets to this file, with message
"E720032: Can't remove file 'svn-<RANDOM>': The process cannot access
the file because it is being used by another process." If I use "svn
export PATH1 PATH2" to do the export from a working copy, the file is
copied without any error message.
I expect svn export to work (and produce a small plain file on Windows)
for files with the svn:special property.
Here's what my file looks like.
svn cat svn://localhost/repos/trunk/Current
link A
svn proplist svn://localhost/repos/trunk/Current
Properties on 'svn://localhost/repos/trunk/Current':
svn:special
Here is what happens when any "svn export URL PATH" command reaches it.
There is a pause of a few seconds, then the message.
svn export svn://localhost/repos/trunk/Current Current
svn: E720032: Can't remove file 'svn-DBFBE990': The process cannot
access the file because it is being used by another process.
Possible workrounds for this bug: (a) use svn checkout, or (b) use svn
export from a working copy.
svn --version
svn, version 1.7.9-SlikSvn-1.7.9-X64 (SlikSvn/1.7.9) X64
compiled Apr 5 2013, 15:17:10
[snip]
