Re: Cleanup needed after failed update

Stefan Sperling <stsp_at_elego.de> writes:

> I don't know if Justin's particular case could somehow be detected and
> handled in a more automated fashion. But it would be nice if svn did this.
> Justin, if you care strongly about this, please add an entry to our issue
> tracker[1] that points at this thread in the archives and summarizes the
> problem. Maybe somebody will find time to look into this in detail some day.
> Anyone is welcome to do so, including anyone who has participated in this
> thread so far, and submit concrete suggestions or even patches that address
> this issue. Thanks!

There is a 1.7 bug:

http://subversion.tigris.org/issues/show_bug.cgi?id=4192

that fails to remove locks that should be removed.

I'm not sure whether that applies to Justin's particular case because
that's only a problem if the lock gets released between the original
workqueue run and the second workqueue run. That's a very small
window--in most cases both runs see the lock and the bug does not apply.

There is also a 1.6 bug:

http://subversion.tigris.org/issues/show_bug.cgi?id=4196

that removes locks that should remain.

I think it is likely that Justin is seeing the buggy 1.6 behaviour. In
some circumstances this buggy behaviour will not cause a problem but in
other circumstances it will corrupt the working copy.

-- 
Philip