[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 19:23:28 +0100

On Tue, Sep 15, 2009 at 06:14:00PM +0100, Stefan Sperling wrote:
> 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?
>
> Strange.

I gave you the wrong diff command :(

This is the one correct:

svn diff http://svn.collab.net/repos/svn/branches/1.6.x@39163 \
  http://svn.collab.net/repos/svn/branches/1.6.x-r38000 > 3.patch

Note the -r38000, this was missing in my previous mail.

Sorry about that,
Stefan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2395197

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