On Fri, Mar 15, 2002 at 11:58:59AM -0600, Ben Collins-Sussman wrote:
>
> - Warning -
>
> If you've been a good svn developer, updating your svn tree daily,
> your working copy might actually be corrupted.
>
> A bug in libsvn_wc's update-editor was introduced on March 1st
> (r1395), whereby any 'delete' commands received from the server were
> effectively no-ops. This goes for both files and directories. The
> items weren't deleted from disk, *or* from the entries files.
>
> What this means, then, is that your working copy (at this very moment)
> might have directories claiming to be at certain working revisions,
> but are still hanging onto old, dead entries that *should* have been
> deleted. This may cause problems with future updates and commits.
> Not to mention the fact, that when you run 'status', you're likely to
> see entries that no longer exist in HEAD.
>
> One example is the packages/freebsd/ directory, or the ac-helpers/
> directory, if you've not recompiled recently.
>
> It seems futile to try and hunt down all deletions that happened over
> the last 2 weeks, and try to delete/re-update specific areas of our
> working copies. Frankly, at this point, I wonder if we all shouldn't
> just checkout fresh working copies. :-(
you know, it sucks that this happened, but really, it's amazing that
it doesn't happen more often, considering the heavy development that
is going on, and we should all congratulate ourselves that this is
such an uncommon event.
(how's that for a positive spin ;-)
-garretT
--
garrett rooney Unix was not designed to stop you from
rooneg@electricjellyfish.net doing stupid things, because that would
http://electricjellyfish.net/ stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 15 19:13:59 2002