I want to use subversion to provide revision control for my new blog
that I'm creating in turbogears.
I have created a new fresh repository and checked it out on my local
machine. From within the root of the recently checked out directory I
run a "tg-admin quickstart" I follow the prompts and it produces all
the initial files.
Here's where problems start to occur: tg-admin appears to be
automatically adding the files it creates to subversion. That's OK, but
it appears to add files that don't even exist!
Here are files that 'svn status' show a ! exclamation for:
! EnigmaCurryBlog/__init__.py
! EnigmaCurryBlog/enigmacurryblog/sqlobject-history/empty
! EnigmaCurryBlog/enigmacurryblog/static/javascript/empty
! EnigmaCurryBlog/enigmacurryblog/static/css/empty
If I do a commit anyway I get the following error:
Transmitting file data ..svn: Commit failed (details follow):
svn: Can't copy '/airlock/subversion/blog/EnigmaCurryBlog/__init__.py'
to
'/airlock/subversion/blog/EnigmaCurryBlog/.svn/tmp/text-base/__init__.py.svn-base.tmp':
No such file or directory
svn: Your commit message was left in a temporary file:
svn: '/airlock/subversion/blog/svn-commit.tmp'
The error message doesn't concern me too much, as it is obviously
correct. The __init__.py file does not exist. But why does tg-admin
insist on adding the non-existant files??
Using TG 0.9a1 and subversion 1.2.3
-Ryan
It's funny that you should mention this. I just run into it myself
last night. I hadn't had a chance to open a ticket on it. Feel free to
do so (otherwise, I'll do so with the description you've given here...
it's a good description of the problem.)
Thanks!
Kevin