On Apr 23, 2009, at 17:39, jon wrote:
> I'm using svnsync version 1.4.2, and am trying to sync to a new svn
> server running 1.6.1. Part way through the syncing, it fails as
> follows:
>
> Copied properties for revision 831.
> Committed revision 832.
> Copied properties for revision 832.
> svnsync: PROPFIND request failed on '/svn/DEMO/trunk/orphaned/
> _ZVCAAAAA/tabwin.cpp'
> svnsync: '/svn/DEMO/trunk/orphaned/_ZVCAAAAA/tabwin.cpp' path not
> found
>
> When looking at the log on the originating svn server, it appears as:
> r832 | Bob | 1996-06-04 07:11:47 -0700 (Tue, 04 Jun 1996) | 1 line
> Changed paths:
> A /trunk/orphaned/_AWCAAAAA
> A /trunk/orphaned/_AWCAAAAA/tabwin.h
> A /trunk/orphaned/_ZVCAAAAA
> A /trunk/orphaned/_ZVCAAAAA/tabwin.cpp
>
> However, when looking at the log on the mirrored svn server it is:
> r832 | Bob | 1996-06-04 07:11:47 -0700 (Tue, 04 Jun 1996) | 1 line
> Changed paths:
> A /trunk/orphaned/_AWCAAAAA
> A /trunk/orphaned/_AWCAAAAA/tabwin.h
> A /trunk/orphaned/_ZVCAAAAA
>
>
> The tabwin.cpp file is not being properly synced, thus causing the
> failure. Running `svnadmin verify` succeeds, and using `svnadmin
> dump/load` also works.
>
> I dumped revision 832, and here are the contents of the files and
> directories added in that revision:
>
> ----------------------------------------------------------------
> Node-path: trunk/orphaned/_AWCAAAAA
> Node-kind: dir
> Node-action: add
> Prop-content-length: 10
> Content-length: 10
>
> PROPS-END
>
> Node-path: trunk/orphaned/_AWCAAAAA/tabwin.h
> Node-kind: file
> Node-action: add
> Prop-content-length: 10
> Text-content-length: 1074
> Text-content-md5: 36a8aa54e453ccc75e1c201ee9ae8ce6
> Content-length: 1084
>
> PROPS-END
>
>
> Node-path: trunk/orphaned/_ZVCAAAAA
> Node-kind: dir
> Node-action: add
> Prop-content-length: 10
> Content-length: 10
>
> PROPS-END
>
>
> Node-path: trunk/orphaned/_ZVCAAAAA/tabwin.cpp
> Node-kind: file
> Node-action: add
> Prop-content-length: 10
> Text-content-length: 0
> Content-length: 10
>
> PROPS-END
> ----------------------------------------------------------------
>
> Is it possible that svnsync is failing due to the missing Text-
> content-md5 on tabwin.cpp? This was a previous Visual SourceSafe
> repo converted to svn about 3 years ago, and maybe there was a
> hidden issue with the conversion that is now exposed by svnsync.
> Any other ideas for a workaround?
I suppose that's a theory. Your dump says tabwin.cpp is a zero-length
file. Does that sound correct? Was the file in fact empty when it was
added in that revision?
I suppose the md5 may be absent because someone thought nobody would
need to verify the md5 of zero bytes...
I just created a new repository with svn 1.6.1, added a single empty
file foo, and dumped it, and I got:
----------------------------------------------------------------
SVN-fs-dump-format-version: 2
UUID: dfafc4ee-c289-4282-83d4-c41e00f6992c
Revision-number: 0
Prop-content-length: 56
Content-length: 56
K 8
svn:date
V 27
2009-04-23T11:54:05.414245Z
PROPS-END
Revision-number: 1
Prop-content-length: 102
Content-length: 102
K 7
svn:log
V 0
K 10
svn:author
V 8
rschmidt
K 8
svn:date
V 27
2009-04-24T00:33:37.705756Z
PROPS-END
Node-path: foo
Node-kind: file
Node-action: add
Prop-content-length: 10
Text-content-length: 0
Text-content-md5: d41d8cd98f00b204e9800998ecf8427e
Text-content-sha1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Content-length: 10
PROPS-END
----------------------------------------------------------------
So my dump does have the md5 of the zero-length file (and a sha1 as
well). You could try modifying a copy of your dump to include this
md5 line and see if that helps you go further.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1883922
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-24 02:59:58 CEST