[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 comes to backups!

Problem is, in some situation that I haven't nailed down, some properties don't seem to get set in the svnsync'd version. I think it happens when I make a tag, ie, copy a directory, that has properties set. For example, in the "svnadmin dump":

--------------------------------------------------------
Node-path: tags/nova/2013-11-04-1
Node-kind: dir
Node-action: add
Node-copyfrom-rev: 24017
Node-copyfrom-path: trunk/src/astrometry
Prop-content-length: 92
Content-length: 92

K 10
svn:ignore
V 6
*.pyc

K 13
svn:mergeinfo
V 30
/tags/nova/2012-06-27-2:21009*
PROPS-END
--------------------------------------------------------

in the svnsync'd mirror:

--------------------------------------------------------
Node-path: tags/nova/2013-11-04-1
Node-kind: dir
Node-action: add
Node-copyfrom-rev: 24017
Node-copyfrom-path: trunk/src/astrometry
--------------------------------------------------------

This sounds a bit like closed issue 4184:
  http://subversion.tigris.org/issues/show_bug.cgi?id=4184

I am using subversion-1.8.4.

For what it's worth, the mirror is on another machine and connects via svn+ssh. This svn repo was created in 2005, and is format "3" (versions 1.5+).

Unfortunately, I was unable to create a simple test case demonstrating the problem, so maybe it is some more complicated circumstance than the properties and directory copy, or maybe it has to do with having an old repo?

Any hints on what could trigger this would be much appreciated!

Thanks,
--dustin

Reply via email to