Just found out we can't use PyWhip for our project name.
Created a new project named PyKata.
Changed all references in my working copy from PyWhip to PyKata.
Clicked the Reset This Repository link at the bottom of the Source tab
page in the new project.
TortoiseSVN commit
https://pykata.googlec
You're trying to commit from an old working copy to a newly-created
repository? You'll have to rewrite all your URLs for the new
repository, using 'svn switch --relocate https://pywhip
https://pykata'.
This is a general "help with svn client" question; you may get faster
replies over at us...@su
On Mar 1, 3:21 pm, Ben Collins-Sussman wrote:
> You're trying to commit from an old working copy to a newly-created
> repository?
Correct. I created the new project, changed PyWhip to PyKata in the
working copy,and now I'm trying to upload (commit) the edited working
copy to the new repository.
Sounds to me like it might be simpler to svnsync from Google Code to your
local harddisk and then svnsync back up to Google Code in the new project.
:-)
On Tue, Mar 2, 2010 at 1:57 PM, Dr Dave wrote:
> On Mar 1, 3:21 pm, Ben Collins-Sussman wrote:
> > You're trying to commit from an old working
:
> Sounds to me like it might be simpler to svnsync from Google Code to your
> local harddisk and then svnsync back up to Google Code in the new project.
I'm using TortoiseSVN on Windows XP. There is nothing in Tortoise
that I can find to do an "svnsync" or "replicate repository". I
already hav
svnsync has nothing to do with this; that's a way of sucking out the
*entire repository* to local disk. Totally irrelevant to the problem
at hand.
Working copies are "glued" to their original repositories in multiple
secret ways: the original checkout URL is embedded deep within every
secret .s
Oh, sorry. Seems I had this completely wrong. I should have read the
original post more thoroughly. Please ignore my svnsync suggestion.
My apologies. :-)
:Darren.
On Tue, Mar 2, 2010 at 9:35 PM, Ben Collins-Sussman wrote:
> svnsync has nothing to do with this; that's a way of sucking out the
Thanks, Ben. Your help is much appreciated.
On Mar 2, 2:35 pm, Ben Collins-Sussman wrote:
>
> Working copies are "glued" to their original repositories in multiple
> secret ways: the original checkout URL is embedded deep within every
> secret .svn/ metadata directory in every folder. So is th
On Tue, Mar 2, 2010 at 6:33 PM, Dr Dave wrote:
> Thanks, Ben. Your help is much appreciated.
>
> On Mar 2, 2:35 pm, Ben Collins-Sussman wrote:
>>
>> Working copies are "glued" to their original repositories in multiple
>> secret ways: the original checkout URL is embedded deep within every
>> s
On Mar 2, 6:55 pm, Nathan Ingersoll wrote:
> On Tue, Mar 2, 2010 at 6:33 PM, Dr Dave wrote:
> > Thanks, Ben. Your help is much appreciated.
> > On Mar 2, 2:35 pm, Ben Collins-Sussman wrote:
>
> >> Working copies are "glued" to their original repositories in multiple
> >> secret ways: the original
On Wed, Mar 3, 2010 at 10:39 AM, Dr Dave wrote:
> On Mar 2, 6:55 pm, Nathan Ingersoll wrote:
>> On Tue, Mar 2, 2010 at 6:33 PM, Dr Dave wrote:
>> > Thanks, Ben. Your help is much appreciated.
>> > On Mar 2, 2:35 pm, Ben Collins-Sussman wrote:
>>
>> >> Working copies are "glued" to their original
On Mar 3, 10:09 am, Ben Collins-Sussman wrote:
> On Wed, Mar 3, 2010 at 10:39 AM, Dr Dave wrote:
> > On Mar 2, 6:55 pm, Nathan Ingersoll wrote:
> >> On Tue, Mar 2, 2010 at 6:33 PM, Dr Dave wrote:
> >> > Thanks, Ben. Your help is much appreciated.
> >> > On Mar 2, 2:35 pm, Ben Collins-Sussman wro
Hold on, let us examine your new pykata repository and see what's up.
On Wed, Mar 3, 2010 at 1:55 PM, Dr Dave wrote:
> On Mar 3, 10:09 am, Ben Collins-Sussman wrote:
>> On Wed, Mar 3, 2010 at 10:39 AM, Dr Dave wrote:
>> > On Mar 2, 6:55 pm, Nathan Ingersoll wrote:
>> >> On Tue, Mar 2, 2010 at 6
The problem cleared. I now have a new repository with the name
pykata. I've also updated my WC to that repository. The only
problems are some worrisome error messages, and the fact that my
directory structure in the WC is a little different than before.
Here are the errors at the end of the syn
On Mar 3, 1:40 pm, Ben Collins-Sussman wrote:
> Hold on, let us examine your new pykata repository and see what's up.
Yes, I would very much appreciate your taking a look. I was not able
to make the edits from 'pywhip' to 'pykata', apparently because there
are some checksums buried in the reposi
I'm really lost as to what you're trying to accomplish, probably
because you're being sloppy with terminology and/or don't understand
how subversion works. That said, the confusion isn't your fault --
you shouldn't have to be an expert at this stuff. :-)
>From where I sit, here's what I see:
1.
On Mar 5, 9:23 am, Ben Collins-Sussman 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:
>
>
OK, here is a procedure that works:
) Create a new repository (or reset an old one).
2) Export all the files and folders from the old working copy
(This leaves out the troublesome .svn folders.)
3) Edit all references to the old name.
$ sed -i 's/pywhip/pykata/g' * # repeat for every folder
One potentially serious problem with the above procedure:
==> Authorship of the files is not preserved. <==
The import to the new repository treats all files as if I had written
them myself.
--
You received this message because you are subscribed to the Google Groups
"Project Hosting on Google C
Well sure, you just threw away all the history. What did you expect? :-)
On Mon, Mar 8, 2010 at 4:35 AM, Dr Dave wrote:
> One potentially serious problem with the above procedure:
> ==> Authorship of the files is not preserved. <==
> The import to the new repository treats all files as if I had
On Mar 8, 10:01 am, Ben Collins-Sussman wrote:
> Well sure, you just threw away all the history. What did you expect? :-)
I wasn't expecting anything, quite frankly. Didn't think about it
until I noticed the problem. It's obvious now that I see it. I posted
the comment because I think others
On Mon, Mar 8, 2010 at 1:11 PM, Dr Dave wrote:
> On Mar 8, 10:01 am, Ben Collins-Sussman wrote:
>> Well sure, you just threw away all the history. What did you expect? :-)
>
> I wasn't expecting anything, quite frankly. Didn't think about it
> until I noticed the problem. It's obvious now that
On Mar 8, 1:12 pm, Ben Collins-Sussman wrote:
> On Mon, Mar 8, 2010 at 1:11 PM, Dr Dave wrote:
> > I'm stuck now with moving the user data (exercises contributed to
> > PyWhip). Looks like that is another thing that Google just doesn't
> > want us to do real easily. Any suggestions?
>
> "user
On Tue, Mar 9, 2010 at 12:52 PM, Dr Dave wrote:
> On Mar 8, 1:12 pm, Ben Collins-Sussman wrote:
>> On Mon, Mar 8, 2010 at 1:11 PM, Dr Dave wrote:
>
>> > I'm stuck now with moving the user data (exercises contributed to
>> > PyWhip). Looks like that is another thing that Google just doesn't
>> >
On Mar 8, 10:36 pm, Jacob Lee wrote:
> This data is not stored in your project; it is stored in the pywhip
> App Engine application. It is possible to get data in and out of App
> Engine programmatically:
> seehttp://code.google.com/appengine/docs/python/tools/uploadingdata.html
> for a tutorial
below)
This problem has already been posted in the appengine forums with no
answer. It is something that needs to be done in cloning a project,
so I hope it will get an answer here. I think it would be good to
have everything relevant to cloning a project in one place. Maybe we
can distill this t
pcfg.py. It just runs and fails. (see session below)
>
> This problem has already been posted in the appengine forums with no
> answer. It is something that needs to be done in cloning a project,
> so I hope it will get an answer here. I think it would be good to
> have everything rel
27 matches
Mail list logo
