I have found the following problems when os deletes are done instead of
subversion deletes.
Dunno if they're known bugs, or not: Mailing list & issue searches were -ve.
Part1 of the bug may possibly be a bug against doccumentation.
Parts 2,3 are most likely buggy failure conditions. It looks like the
subversion commands don't recover properly after a failure.
I'm also not too clear why "svn rm" is required.
I can understand why "svn mv" and "svn add" are needed.
I would have thought it would be easy to detect & remove missing files
automatically.
What am I missing?
Desription of the bugs follows:
*** Bug pt1: os "rm" vs. "svn rm" => trouble. ***
If my working copy has a directory "aa" in it,
and I do:
rm -rf aa
Then it beomes extremely difficult to make the wc commitable.
For instance if I try:
svn rm aa
This fails.
The only way I have found to make the wc commitable is to do the following:
svn up aa.
*** Bug pt2: risks with "svn up aa" ***
If my repository is at file:///home/auser/svn
Then doing the following causes an unrecoverable failure:
svn rm file:///home/auser/svn/aa
svn up aa
I have attempted "svn cleanup" and "svnadmin repair". Neither correct
the failure.
*** Bug pt 3: bad flagging of files for delete***
if i do:
rm -rf aa"
svn rm aa
It fails, to mark aa as deleted (as expected).
It then proceeds to mark a few other other files/dirs for delete!
svn up aa
svn commit aa
Will result in the files marked for delete now being marked as new files,
not under source control!
I can provide shell logs from an empty repository to the bugs for all
the above.
Bye
-Rob.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 7 20:13:02 2003