Not sure what I've done to cause it, and can't easily reproduce the
behavior in a toy case, but it does happen systematically each time I
run a script to build a directory tree for one more chapter of the book
I'm working on (Python Cookbook 2nd Edition) and try to add it to SVN
-- I've tried many variations. I get into a state where, e.g.:
$ svn rm cha/sho
svn: Use --force to override this restriction
svn: 'cha/sho/ne' is not under version control
OK, so 'cha/sho/ne' is not under version control -- darn, I _had_ added
it, I'm sure. But svn st confirms it isn't by showing a ? to its left.
Ah well, easy to fix, thinks I:
$ svn add cha/sho/ne
svn: warning: 'cha/sho/ne' is already under version control
So I can't add it because it's already there, and I can't remove it
(without --force) because at the very same time it's not there. Is it
or not?! How do I verify the situation and fix this obvious
contradiction between the error messages / warnings of different svn
commands?
When I svn up from OTHER machines, directory cha/sho/ne _IS_ there, and
I see none of these anomalies. Ditto if in frustration I throw away my
working copy on the machine where I originally did the svn add and do a
fresh checkout -- again cha/sho/ne is there fresh as a rose. But
except for such extreme means, I can't find a way to convince svn on
the machine I did the svn add from that the directory IS so there under
version control (except that if I try adding it, then it warns me it is
-- but svn st STILL shows a queston mark!!!).
svn --version is 1.0.5. I've tried adding the tree of files and
directories that makes up a chapter in all ways I could think of --
with just a svn add of the top directory of the chapter's tree (cha/sho
in this example), with an os.walk (Python) or find (sh) of the tree,
both top-down and not, and svn add -N file by file and directory by
directory -- no joy.
It's not a killer bug, at worst I CAN use the fresh-checkout trick, but
I'd much rather be able to add everything cleanly in the first place,
so, thanks for any suggestion!
((The OS's in play are Linux and Mac OS X -- the repository is under
Linux -- the misbehavior happens identically with clients on both Linux
and Mac OS X -- if I've omitted any important detail please ask,
thanks!!!))
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 22 16:02:05 2004