I posted message below to the users list and got no response. Should I
create a bug report for this?
Thanks and Regards,
On Sat, Jun 19, 2010 at 3:33 PM, Onno van der Straaten <
> Hi all,
> I'm trying to cleanup a repository a bit. While renaming and moving
> files/folders I noticed that commit at times fail with the message "path not
> found". I think this is caused by filenames with spaces.
> I could easily reproduce this on a personal repository
> I have a co of a folder with two subfolders
> my-laptop ~/my_wc $ ls
> folder 1 folder 2
> Rename folder 2 to folder 3
> my-laptop ~/my_wc $ svn move "folder 2" "folder 3"
> A folder 3
> D folder 2/file with spaces.txt
> D folder 2
> Move file to folder 1
> my-laptop ~/my_wc $ svn move "folder 3/file with spaces.txt" "folder 1/file
> with spaces.txt"
> A folder 1/file with spaces.txt
> D folder 3/file with spaces.txt
> my-laptop ~/my_wc $ svn commit --message "test"
> Adding folder 1/file with spaces.txt
> svn: Commit failed (details follow):
> svn: '/svn/!svn/bc/1101/test/folder%202/file' path not found
> If I issue the commands on a file without spaces (replace space with
> underscore) the commit is successful.
> If I reverse the commands, I move the file and then rename the folders, the
> commit also fails but with a different error message
> svn: Item '/test/folder 2' is out of date
> After that I was unable to recover my working copy to a working state. It
> reports tree conflict. svn cleaup, svn revert, svn up didn't help.
> Is this a known problem? Shouldn't this just work regardless of spaces in
> filenames and/or order of the commands?
> BTW, I'm using Linux Mint and svn client version 1.6.5 (r38866).
> Repository is *version 1.5.1 (r32289).*
> Thanks in advance,
Received on 2010-06-23 15:39:20 CEST