On Sat, Aug 22, 2009 at 8:01 PM, Denis
Onischenko<denis.onischenko_at_gmail.com> wrote:
> thanks for reply,
>
>> what svnsvnc version are you using?
>
> I am using svnsync, version 1.6.4 (r38063)
>
>> Are you using ra_serf or ra_neon?
>
> I was trying neon and serf. Both was failed with same error.
>
>> Are you syncing from the root or from a subpath?
>
> from the root
>
>> What command are you using?
>
> svnadmin create apache-svn
> echo "#!/bin/sh" > apache-svn/hooks/pre-revprop-change
> echo "exit 0" >> apache-svn/hooks/pre-revprop-change
> svnsync init file://`pwd`/apache-svn http://svn.apache.org/repos/asf
> svnsync sync file://`pwd`/apache-svn
>
>
>> At what revision does it fail?
>
> at 51901 revision. apache-svn/db/current contains "51900"
>
So, in revision 51091 the path /infrastructure/site is added. It'
can't be committed in your repository, because the /infrastructure
path itself wasn't created.
Looks like read access to the asf repository's /infrastructure path is
restricted, whereas the '/infrastructure/site' path is open to
everyone.
AFAIK svnsync doesn't support this configuration, I suppose that all
people mirroring the asf repository without read access to the
/infrastructure directory will have the same problem.
There's no easy workaround I can think of. An ugly hack is to roll
back your local mirror to an empty revision before r51091(a revision
with a commit in a for you unreadable path), create the
/infrastructure path, and let svnsync continue from there.
While looking for a way to handle this behavior in svnsync, I found
that this issue is already logged:
http://subversion.tigris.org/issues/show_bug.cgi?id=2960
hth,
Lieven
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2386982
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-27 00:06:08 CEST