Hi, A bit of a corner case but I thought I mention it anyway. If I move a new folder with a renamed file this causes an error message
I'm stacking move operations, which is probably not wise but a result of the fact that I'm using a script with some logic to cleanup our repos. It looks like the following should reproduce it svn move A A2 svn mkdir A2/new_folder svn move A2/file A2/new_folder/file svn move A2/new_folder/file A2/new_folder/file_new_name svn move A2/new_folder A2/new_folder_better_name the last move causes the message like svn: The node 'A2/new_folder/file' was not found. So it seems the wrong/old path was used. Somewhere administration was not correctly updated that the file moved to A2/new_folder/file_new_name? Some output with that message subversion/svn/move-cmd.c:102: (apr_err=155010) subversion/svn/util.c:901: (apr_err=155010) subversion/libsvn_client/copy.c:2347: (apr_err=155010) subversion/libsvn_client/copy.c:433: (apr_err=155010) subversion/libsvn_client/copy.c:433: (apr_err=155010) subversion/libsvn_client/copy.c:366: (apr_err=155010) subversion/libsvn_client/copy.c:342: (apr_err=155010) subversion/libsvn_wc/copy.c:734: (apr_err=155010) subversion/libsvn_wc/copy.c:484: (apr_err=155010) subversion/libsvn_wc/copy.c:269: (apr_err=155010) subversion/libsvn_wc/wc_db.c:2939: (apr_err=155010) subversion/libsvn_wc/wc_db.c:2857: (apr_err=155010) subversion/libsvn_wc/wc_db.c:5981: (apr_err=155010) subversion/libsvn_wc/wc_db.c:434: (apr_err=155010) svn status shows stuff has gone missing, I can see several exclamation marks. I'm using 1.7 dev build revision 961397. Reproduction script is attached. Looks like a bug? Onno
node_not_found.sh
Description: Bourne shell script
