[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 23:27:29 +0100

On Wed, Sep 16, 2009 at 01:03:30AM +0300, Daniel Shahaf wrote:
> Wouldn't svn_ver_check_list() complain if a 1.6.x_at_HEAD binary (which
> calls itself 1.6.6-dev) found a 1.6.5 (release) library at runtime?

Possibly. But it would mean that our fix isn't working :(
Well, I'm convinced that the fix should work. I've tested it
many times. But maybe we didn't catch some corner case.

In which case I'd be very grateful for a reproduction script
which starts with an empty repository and issues the appropriate
svn commands to eventually trigger the double-tree conflict error.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-16 00:28:50 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.