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

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

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 15 Sep 2009 18:14:00 +0100

On Tue, Sep 15, 2009 at 11:39:46AM -0500, Paul Hammant wrote:
> Stefan,
> We rebuilt Svn based on 1.6.5 and those two patches, but it still the
> same :-(
> Here is the output. It is the same as the OP.
> svn: Attempt to add tree conflict that already exists
> svn: Error reading spooled REPORT request response
> We confirmed that we had the right svn, by hard-coding the path to
> executable, and confirming it was the right thing by way of 'svn --
> version' before invocation.
> Thus, Svn 1.6.6 IMO is going to exhibit some of the same tree-conflict
> issues as 1.6.3.
> Thoughts?


Are you sure you've applied the patches correctly?
If you run diff -ruN on the source tree you have patched and
one that is fresh and unpatched, does the diff you get look
the same as the one you downloaded from the svn.collab.net

You could also try checking out the 1.6.x-r38000 branch and
build that (run the autogen.sh script, then build as usual).
svn co http://svn.collab.net/repos/svn/branches/1.6.x-r38000

If you are really sure that the fix does not work, can you provide
a script which starts out with an empty repository and issues the
necessary svn commands to trigger the problem?
That would help a lot.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-15 19:14:58 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.