HI, I think we spotted a bug. The following sequence has been followed:
* User 1 renames a svn folder and commits this * User 2 has unversioned files and uncommited files in the renamed folder * User 2 performs an update * Subversion encounter a tree conflict * All files are still on the disk during this step * Subversion solves three conflict. * unversioned files are removed from users 2 disk. The unversioned files are retained in the old folder with the old name when the same sequence is executed with no uncommited files on users 2 computer. This all has been performed using : Svn, version 1.14.2 (r1899510) compiled Sep 24 2022, 10:21:16 on x86-microsoft-windows using Microsoft Windows [Version 10.0.19045.2130]. Kind regards, [cid:image001.png@01D8F908.E9F7DEE0] Marcel Delorme Head of Software [cid:image002.png@01D8F908.E9F7DEE0]<https://venturasystems.com/> Phone: +31 (0) 515 729433<tel:+31%20(0)%20515%20729433> Email: m.delo...@venturasystems.com<mailto:m.delo...@venturasystems.com> Address: De Marne 216, 8701 MH Bolsward, Netherlands [cid:image003.png@01D8F908.E9F7DEE0]<https://www.linkedin.com/company/ventura-systems-bv> [cid:image004.png@01D8F908.E9F7DEE0]<https://www.facebook.com/Ventura-Systems-130403847033358/>