update -r 0 weirdness?

I accidentally updated a file in my working copy to revision 0 and it
was deleted which makes sense (it's just a test repository so no real
harm done). However, now my wc is in a weird state b/c it has leftover
stuff in the .svn tree.

[SoundGeek ~/Development/Test/Work/ProjA]$ svn up -r 0 larry.cpp
D larry.cpp
Updated to revision 0.

[SoundGeek ~/Development/Test/Work/ProjA]$ svn up
svn: Can't copy '.svn/text-base/larry.cpp.svn-base' to
'.svn/tmp/text-base/larry.cpp.svn-base.tmp': No such file or directory

[SoundGeek ~/Development/Test/Work/ProjA]$ svn up -r HEAD
svn: Can't copy '.svn/text-base/larry.cpp.svn-base' to
'.svn/tmp/text-base/larry.cpp.svn-base.2.tmp': No such file or
directory

Should the wc care that larry.cpp is no longer in the repository?
Admittedly, this is certainly an unusual scenario but perhaps it could
be handled better? Is there some admin command I can do to make things
right again?

[SoundGeek ~/Development/Test/Work/ProjA]$ find .svn/ -name "*larry*"
.svn//tmp/text-base/larry.cpp.svn-base.tmp

[SoundGeek ~/Development/Test/Work/ProjA]$ svn st -v
? ProjA Data
! 14 14 stephen .
                14 12 stephen AACUtilities.cpp
                14 13 stephen bob.cpp
                14 13 stephen ProjA.mcp
                14 12 stephen HelloWorld.c

I see that the directory has an exclamation point next to it so it
knows something is missing/incomplete in the directory but I don't know
what I can do about it.

svn ls shows that larry.cpp is still in the repository.

thanks,
stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jan 15 20:56:29 2005