[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

quick bug description

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-12-10 13:35:03 CET

I'm trying to get a ViewCVS release done, but ran into an SVN bug. I wanted
to drop off a quick note to the mailing list about it. I don't have a
confirmed recipe, but it went something like this:

(a while back)
[notes]$ svn cp ../STACK .

[trunk]$ svn up
(Obstructed update on STACK)

[trunk]$ rm notes/STACK # note filesytem rm, not svn rm
[trunk]$ svn up
... all seems okay
[trunk]$ cd notes
[notes]$ svn stat

Oops! So, I figure to be a smart guy:

[notes]$ svn revert STACK

Now I was totally screwed. .svn/entries didn't list STACK any more. And the
dir entry was "current", so an "svn up" didn't do anything. I had to set
aside my changes, pull a fresh copy, and hand-merge my changes back in.

I'm thinking the right approach is an update shouldn't just look at the
filesystem for obstruction, but also the .svn/entries file for conflicts.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006

This is an archived mail posted to the Subversion Dev mailing list.