> Is there any way to get around this problem. I updated all the permissions but
> the problem is that A was created like years back and I won't be able to mirror
> those revisions.
Access restrictions are not versioned with the data, they are read
from the configuration at the moment one wants to access the data.
Therefore it should make no difference when your folder A was created
and if the user used to sync now still can't read folder A, then your
access configuration is just wrong and needs to be tuned.
The easiest thing to test would be to create a new user just for
syncing an give him full access to everything.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefon: Potsdam: 0331-743881-0
E-Mail: tscho...@am-soft.de
Web: http://www.am-soft.de
AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
Specifically, if you run svnsync using an authz-bound user, then you
should just see adds-with-history converted into adds-without-history.
I believe we have regression tests for such scenarios too.
If you can reproduce this (have a minimal example), please file an
issue, thanks.
Daniel
(separately: is the error in the subject really everything? It should
be logging the original error somewhere --- possibly on the server side,
but *somewhere*.)
On Thu, 14 Apr 2011 11:17 -0700, "ankush chadha" <ankushch...@yahoo.com> wrote:
> Yeah, even I thought that the behavior should be same as you mentioned
> but I got "svnsync: Error while replaying commit" error during sync
> operation for that revision.
>
>
> When I checked the mirrored repository, A was missing which is correct
> as at that time A had restricted access. Branch operation of A to B
> failed to mirror though.
>
> I am using svn 1.6.6. After fixing the permissions and re-initiating
> another mirror the problem went away and now both of my repositories
> are synced up with A and B. I am sure that this was the error but
> willl try to write reproduction steps with sample scripts.
>
That would help a lot, thanks,
Daniel
I'm syncing between a Ubuntu with 1.6.5 and os x 1.6.16.
I never had this error, I don't have any right issue.
I was syncing as usual, while commiting other stuffs
on the main server and suddently got this error.
I don't think the commit it is choking on has anything in particular.
Please help.
Where can I check the logs?
/nodje
-- Regards, Stefan Hett