On Fri, Jan 14, 2022 at 4:08 AM Stefan Sperling <s...@apache.org> wrote: > > 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. > """
As indicated, this is in the ubuntu 18.04 SFU on windows, the msys2-64 current distribution, as well as Windows "native". Very consistent. > 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? I'm happy to have a look next week. > > 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.
