Hi Bert, I think I tried 'svn status' before. It didn't help me because I couldn't understand what it showed. But I have sloved this problem by renaming one of the files through urls. Thank you for your suggestion.
Di Bert Huijben-5 wrote: > > > > All 'svn' operations normalize the casing of passed filenames to their > on-disk casing on case insensitive systems. (I'm not 100% sure if this > works > this way on Mac/OS, but it does on Windows > > So if there is some 'aLIGN.c' on disk and you pass 'svn rm align.c', 'svn' > translates that to 'svn rm aLIGN.c' before it passes it into the library. > So > the real handler of the delete never sees that you passed different paths. > (This is done in svn_client_args_to_target_array() -> > svn_opt__arg_canonicalize_path()) > > > The workaround is to temporarily remove the on-disk file to something > completely different and then use the command. > > But just calling 'svn status' should tell you if you have this issue. That > should show you two files: one unversioned and one missing/obstructed. > > Bert > > -- View this message in context: http://old.nabble.com/Help%3A-svn%3A-Working-copy-%27XXXX-XXXX-XXX%27-locked-tp29300593p29304098.html Sent from the Subversion Users mailing list archive at Nabble.com.
