I have a new theory: sometimes when you do a 'switch' you'll see a bunch of files get updated then it stops with some sort of message that looks like a warning or error. If you get that, the switch stopped and not all of the directories have been converted over. 'svn info' will show you the new URL, but in the tracking files I think there are old URLs. If you do an svn update then the folders with old urls get deleted. If you get such an error or warning, fix the problem (for me, deleting a folder or file) and run svn switch again until it tells you it is up to date at some revision #. Then I think you will be ok.
On 1/9/13 7:24 AM, "Carol Frampton" <cfram...@adobe.com> wrote: > I had the same issue on one of the two copies of the develop branch that I > "switched". > > Carol > > On 1/8/13 11 :00PM, "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 > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
