I had a similar incident when trying to do updates to the website as well. In fact, build-bot was having lots of troubles too. I full check-out seemed to do the trick in both cases...
-Nick On Tue, Jan 8, 2013 at 11:00 PM, Alex Harui <aha...@adobe.com> wrote: > Hi, > > I’m now many hours into trying to repair a working copy destroyed by using > “svn switch” which we have to use in order to continue to use a working > copy after the migration from incubator to the top-level. Actually, I’ve > given up and am now checking out a new working copy. > > My theory is that I had some changes pending and somewhere in the hidden > svn files it stored a path to the incubator that didn’t get changed by svn > switch. Today I did an “svn update” on that working copy, changed to a > different window while it ran and when I came back, it had deleted most of > the files from my working copy. After doing some investigation, I couldn’t > figure out why it went bad since “svn info” was pointing to the right > place. I ran “svn switch” again and then ran “svn update” again and > watched a lot of files get added again, so I thought it was just a > temporary glitch and I thought it brought back everything, but then when I > tried to build I found that lots of files were still missing. Fortunately, > I don’t think it deleted any of my changed files. > > All my other working copies seemed to switch ok, and some of them had > changes pending as well, so I don’t have a full explanation as to why this > one went bad. Maybe one of you knows the answer and can clue us in so > others don’t get burned this way. Just be careful when you do an svn > update. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
