On Mar 5, 9:23 am, Ben Collins-Sussman <[email protected]> wrote: > I'm really lost as to what you're trying to accomplish,
I need to change the name of this project from PyWhip to PyKata. I read in an earlier discussion that the way to do this was by cloning the project. > From where I sit, here's what I see: > > 1. You created a new pykataprojectwith an empty repository. > 2. You used 'svnsync' to copy all 60 revisions from the old pywhip > repository to the new pykata repository. > 3. Since then, you've committed 5 new revisions to the pykata repository. > > I see nothing suspicious on the server or with the new pykata > repository. I suspect all the frustration is coming from confusion > around client-side manipulation of your working copies and uncommitted > changes. > > My suggestion isn't that you "start fresh" by nuking the repository -- > you should nuke your *working copy* and do a completely fresh "svn > checkout" of the pykataproject. The fact that you're messing around > inside .svn/ folders means you've probably corrupted the whole working > copy -- .svn/ folders should never be touched, ever. Ah, a key point. I just used sed to change all occurrences of 'pywhip' in all folders. $ sed -i 's/pywhip/pykata/g' * That probably left some checksums out of sync with the file contents. I'm hesitant to continue with the existing repository, because I can already see some missing files, and out-of-date files, in spite of what appeared to be successful commits. I think a reset of the new pykata and another svnsync from the old pywhip would be a safer starting point. I'm also thinking that maybe it isn't worth saving the old revision history. We can keep the old project in place for a few months if we need to recover any old files. > Just do a fresh checkout to a new folder. Try making a simple change > and committing that change. Then move forward from there. Yes, that was my strategy, hence the 5 small commits. It might have worked had I not changed the .svn files. I'm still concerned about changing the project name in the non-hidden files, however, especially app.yaml. If I go through all this effort, am I gong to find that I cannot change this file? > If there are modified files in the old "dead" working copy, then > carefully copy them on top of the new working copy, so that it appears > like you've edited them in the new location. Then you should be able > to commit. I'm not sure how to be careful in this copy operation, so this is one more reason to just "add" them to a skeleton WC. -- Dave -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
