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

Possible svnsync bug

From: Jamma Tino Schwarze <subversion.lists_at_tisc.de>
Date: Tue, 18 May 2010 17:21:27 +0200

Hi there,

I'm currently in the process of migrating a large CVS repository to
Subversion. One of our use cases for Subversion is partially syncing the
repository to our customers for read-only access.

During testing svnsync I came across an issue which may be reproduced
using the attached test script. It creates a repository (requires
svnmucc for the critical step), then svnsync's the /mf path within the

The operation which seems to be critical looks like this in an svn dump
(revision 5 according to attached script):

Node-path: mf
Node-kind: dir
Node-action: add
Node-copyfrom-rev: 3
Node-copyfrom-path: trunk

Node-path: mf/d
Node-kind: dir
Node-action: delete

Node-path: mf/d
Node-kind: dir
Node-action: add
Node-copyfrom-rev: 4
Node-copyfrom-path: branches/o/d

-> a delete immediately followed by a copy to the same location.

svnsync fails with at :
svnsync: File not found: revision 5, path '/mf/d/m.txt'

This file is not supposed to exist there because mf/d has been deleted
first, then replaced by branches/o/d which does not contain the file (it
is in /trunk/d/ though).

The repository itself seems to be consistend - dumping and loading it
works, even incremental dumping/loading.

I googled for this issue and looked at the issue tracker but couldn't
come up with any matching bug report. I tested against SVN 1.6.11 and
will try again using trunk.

Is it a bug?



"What we nourish flourishes." - "Was wir nähren erblüht."

Received on 2010-05-18 17:21:56 CEST

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