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

RE: Re: back-end fsfs DB corruption? - attempt to merge uncovering it

From: Jonathan <jawolter_at_gmail.com>
Date: Mon, 14 Sep 2009 13:52:33 -0700 (PDT)

Great, thanks!

I'm working with Paul on this. Will we need to upgrade the server to take advantage of these bug fixes?

We're on 1.6.3 for the server currently.

> There are 3 bugs you have run into, all of which are known
> and fixed:
> 1) Tree conflicts can only be resolved to 'working' state right now,
> and svn should not be fooling users into thinking 'theirs-full'
> etc. applies to tree conflicts.
> 2) The "attempt to add tree conflict that already exists" error
> does not print the path of the double-tree conflict victim.
> 3) It is possible to corrupt the working copy during a tree conflict
> which involves a replace. This is what is stopping your merge.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-14 23:06:24 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.