On Thu, Jan 13, 2022 at 07:17:27PM -0600, William A Rowe Jr wrote: > Thanks Stefan, it's attempting [locally] to replace a file, which was > just created during the > checkout (which might even be open).
Hmm. I assume SVN would close such files based on APR pool lifetime. Handling of the pristine installation step has been changed in SVN trunk: https://svn.apache.org/r1886490 In particular: """ On Windows, it uses the existing mechanism of installing the files by handle, without having to reopen them. """ If you are running 1.14 or an older release, perhaps try a client built from trunk to see if this issue has already been fixed for a future SVN 1.15 release? > So it looks like some hash > collision or other > duplication issue where there are two attempts to emplace the same > hash svn-base image, > and linux is letting this happen without complaint, while windows refuses. Does the same file content (ignoring expanded keywords, if any) exist at multiple paths? If so, such paths would naturally share the same pristine based on the hash of file contents.
