From users-return-849-daniel=haxx.se@subversion.apache.org Fri Feb 5 13:01:17 2010 Return-Path: Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by giant.haxx.se (8.14.3/8.14.3/Debian-9) with SMTP id o15C1GfV011967 for ; Fri, 5 Feb 2010 13:01:17 +0100 Received: (qmail 20362 invoked by uid 500); 5 Feb 2010 12:01:11 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Delivered-To: moderator for users@subversion.apache.org Received: (qmail 5425 invoked by uid 99); 5 Feb 2010 11:52:12 -0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pavel.tarasenko@gmail.com designates 74.125.78.144 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=2Kuaf4jhvExwIvyYAy9HRtcI8I6dKhH8MpOof6eUy4A=; b=XE3btdWMfVYqF1NQ00h4XK1g91oOER1hbEb71GxW03Pdj54So/7ewpd1PZbUEPiinu 1adH6KTpHUT0X0Rs7Z9adM+i7XLwng0CIrp+RNHSMn2BGAFmOvMDCAvU5CeGU/M7PU49 9xD4UkAbqC/xmFsVzvlOKrYt6Iahwh1xCIK38= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=qAuWrCAeuwHlRAqLDtK484P9ZzGfAUZHSOUsarNFO3izMyy+dMCzTrxNdZrjmBe24T 36DU6lEW0l+FLuB92l7N5D/xekjASXvPE3bam49uQTxHPHC7dP4mdzWlFTi3JaxpWHoP 1X+iUev1Z4aupeU6nwn96soLh0NBuhyRgVV70= MIME-Version: 1.0 Date: Fri, 5 Feb 2010 12:51:44 +0100 Message-ID: Subject: svnsync - commit replaying problem From: Pavel Tarasenko To: users@subversion.apache.org Content-Type: multipart/alternative; boundary=001636c5ba995e11c0047ed91335 --001636c5ba995e11c0047ed91335 Content-Type: text/plain; charset=ISO-8859-1 Hi all, We have huge subversion repository (avg. 3.5 gigabytes, 140000+ revisions) with svn 1.4.4 (yes, too old, but we can't change this), and two mirrors with svn 1.6.9, synchronised through svnsync. Few days ago svnsync stopped working. It can't process one particular revision and displays "Transmitting file data .svnsync: Error while replaying commit". Changes in the revision was very simple - just one-line addition to unicode (utf-16) text file, and svn 1.6.9 can update working copy with this revision without any errors. Moreover, when we tried to reproduce this situation by creation of test repository, that contain only this file, svnsync 1.6.9 works fine too! At this time, the only solution we found is downgrade to svn1.4.4 at mirror servers and then recreate and synchronize repositories from scratch. Is seems like bug in svnsync... or does anybody have idea, what the problem is? Sincerely, Pavel --001636c5ba995e11c0047ed91335 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

We have huge subversion repository (avg. 3.5 gigabytes, 1400= 00+ revisions) with svn 1.4.4 (yes, too old, but we can't change this),= and two mirrors with svn 1.6.9, synchronised through svnsync.
Few days = ago svnsync stopped working. It can't process one particular revision a= nd displays "Transmitting file data .svnsync: Error while replaying co= mmit".

Changes in the revision was very simple - just one-line addition to uni= code (utf-16) text file, and svn 1.6.9 can update working copy with this re= vision without any errors. Moreover, when we tried to reproduce this situat= ion by creation of test repository, that contain only this file, svnsync 1.= 6.9 works fine too!

At this time, the only solution we found is downgrade to svn1.4.4 at mi= rror servers and then recreate and synchronize repositories from scratch.
Is seems like bug in svnsync... or does anybody have idea, what the p= roblem is?

Sincerely,
Pavel --001636c5ba995e11c0047ed91335--