Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4F796419.6030606@dominolaser.com>
Date: Mon, 02 Apr 2012 10:32:25 +0200
From: Ulrich Eckhardt <ulrich.eckhardt@dominolaser.com>
Reply-To: "users@subversion.apache.org >> SVN users"
 <users@subversion.apache.org>
Organization: Domino Laser GmbH
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: users@subversion.apache.org
Subject: Re: svnsync: Error while replaying commit
References: <1333113928.4211.YahooMailNeo@web28507.mail.ukl.yahoo.com>
In-Reply-To: <1333113928.4211.YahooMailNeo@web28507.mail.ukl.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Am 30.03.2012 15:25, schrieb Gary:
> I see a lot of reports of this error, but little in the way of
> clear information as to what it might mean, or how to fix it:
> 
> $ svnsync sync file://`pwd`/dest
> Committed revision 1.
> Copied properties for revision 1.
> Transmitting file data .....................
> [...]
> Committed revision 79.
> Copied properties for revision 79.
> Transmitting file data .......................
> Committed revision 80.
> Copied properties for revision 80.
> svnsync: Error while replaying commit
> 
> Huh?
> 
> If I look at the source server log, revs 81 & 82 are "missing"
> in the trunk.

Just to cut the discussion short here: You used "svn log $REPO_URL"
directly on the root of the repository, not some directory underneath.
Right?

> I imagine they are/were in a branch, which AFAIK is no longer
> available. Is there any way to get around this? Assuming that's
> the problem, of course.

Do you know more about this branch and how it was removed? Just "svn
delete"ing a branch doesn't cause revisions to vanish. I guess the
repository was modified using the dumpfilter to remove that branch,
causing a non-contiguous range of revisions. svnsync then chokes on
this, because it expects the revisions to be contiguous.

This would explain the reasons, but doesn't help you getting the
repository synced. What I would do is this:
1. Try to reproduce this problem in isolation to make sure it is a
problem with dumpfiltered revisions.
2. Try to create empty revisions in the target repository or modify the
last-synced-revision (I believe that svnsync stores such a property
somewhere). The goal is to keep svnsync from trying to sync that
revision from the upstream repository.
3. File an according enhancement request on svnsync.

Uli
**************************************************************************************
Domino Laser GmbH, Fangdieckstra�e 75a, 22547 Hamburg, Deutschland
Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
Diese E-Mail einschlie�lich s�mtlicher Anh�nge ist nur f�r den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empf�nger sein sollten. Die E-Mail ist in diesem Fall zu l�schen und darf weder gelesen, weitergeleitet, ver�ffentlicht oder anderweitig benutzt werden.
E-Mails k�nnen durch Dritte gelesen werden und Viren sowie nichtautorisierte �nderungen enthalten. Domino Laser GmbH ist f�r diese Folgen nicht verantwortlich.
**************************************************************************************