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

Re: Required version of APR

From: Phil Cornelius <phil_at_croftvillas.com>
Date: Fri, 7 Feb 2014 11:18:36 +0000 (UTC)

Stefan Sperling <stsp <at> elego.de> writes:

> Using a binary file that had been committed to a revision that was

> corrupt, we could construct a test case with simply committing this

> file in a loop and running 'svnadmin verify' on the HEAD revision

> right after. The corruption occurred in about 1 in 100 revisions.

> Symptoms were like in http://subversion.tigris.org/issues/show_bug.cgi?


> The commit itself succeeded so Subversion believed the data had been

> committed fine. Only a subsequent 'svnadmin verify' found the problem.

This seems such an edge case, are there any normal or regular conditions in

which this corruption can occur? Will it *only* happen if the revision you

are commiting to is corrupt? could it happen for regular source (text files)

Reason I ask is that a quick trawl shows that subversion possibly defends

against these earlier version of APR


Do you understand why the corruption is occurring ?
Received on 2014-02-07 16:45:42 CET

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

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