"Kevin Musker" <kmusker@mintel.com> wrote on 07/31/2006 09:42:42 AM:
> I experienced a problem with the svn command line client and am pretty
> sure it's a bug.
>
> If I svn cp a file from the repository, and subsequently delete it, I
> get an error if I try to copy it in again -
>
> > svn cp $SVNROOT/cheese.cc .
> > svn rm --force cheese.cc
> > svn cp $SVNROOT/cheese.cc .
> svn: 'cheese.cc' is not under version control
>
>
> Not sure if this helps, but the client seems to leave the following
> files lying around:
>
> > find . -name "cheese.cc*"
> ./.svn/text-base/cheese.cc.svn-base
> ./.svn/prop-base/cheese.cc.svn-base
> ./.svn/props/cheese.cc.svn-work
> ./.svn/wcprops/cheese.cc.svn-work
> ./.svn/tmp/text-base/cheese.cc.svn-base
> ./.svn/tmp/prop-base/cheese.cc.svn-base
> ./.svn/tmp/props/cheese.cc.svn-work
svn rm only schedules the deletion. You have to commit it for it to take
effect.
It sounds like you would have wanted to run svn revert to undo the copy,
not svn rm. Unless Subversion treats this as a special case, you would
then have to follow up the svn revert with a regular "rm" to remove the
file from the working copy as Subversion is conservative about potentially
destroying data.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 31 18:23:31 2006