Hi Mark,
I do not want to sidetrack this discussion and it sounds like you are
not having the issue I am going to mention, but I thought you could not
rely on this any more due to the random hash ordering of APR in recent
releases (which would yield different md5sum)?
At one point I put in
Dear Bert,
Thanks very much for your reply. I was also frustrated that I was not
able to create a small test case that reproduces the problem, hence my
plea for ideas of what could be triggering the problem.
Your example 'svn:mergeinfo' missing could be caused by older Subversion
clients t
[I am not on the list; please cc me in replies]
Hi,
I keep an svnsync'd mirror of my svn repository, and I run a very
stringent verification check: I do an "svnadmin dump" on the original and
the mirror, and demand that they have the same md5sum. It is paranoid,
but paranoia is good when it
D'oh, I didn't RTFIssues. My apologies.
http://subversion.tigris.org/issues/show_bug.cgi?id=4134
--dstn
On Mon, 28 May 2012, Dustin Lang wrote:
Hi,
For backup purposes I keep a mirror of my svn repo. The mirror is modified
only by "svnsync", which runs hourly
Hi,
For backup purposes I keep a mirror of my svn repo. The mirror is
modified only by "svnsync", which runs hourly in a cron job.
In order to validate the mirror, I run an "svnadmin dump" on the mirror
and on the original, and assert that their md5sums are the same.
I am finding that in
