I tried with a fresh working copy and got the same results. Beverly
-----Original Message----- From: Bob Archer [mailto:bob.arc...@amsi.com] Sent: Wednesday, May 19, 2010 4:21 PM To: Brown, Beverly; users@subversion.apache.org Subject: RE: "Unreadable path encountered" running svn merge --reintegrate > Yes, I can do everything else with no problem and will revert back to > that to get the job done. I'd really like to be able to use the merge > tracking, though. > > One question - could this have anything to do with filenames that have > spaces in them? I'm searching my tree now trying to find an inaccessible > path using > > find . -type f |xargs sum > /dev/null > > It's showing a filename in a .svn/text-base as "No such file or > directory" > > sum: ./path/.svn/text-base/filename: No such file or directory > sum: with: No such file or directory > sum: spaces: No such file or directory > sum: in: No such file or directory > sum: it.pdf.svn-base: No such file or directory > > This is probably unlikely since all other svn commands work just fine, > but just thought I'd ask. I really am not sure. However, having a problem in the .svn folder could be indicitive of a corrupted working copy. Have you tried to run a cleanup on it? Or... try to do a clean checkout of trunk. Personally, I don't use switch. I check out trunk/branches to new folders as I need them. I think it is cleaner and I don't need to remember what path the working copy is currently pointing to. BOb
