[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnsync error : Error while replaying commit

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Thu, 14 Apr 2011 21:20:19 +0300

On Thu, 14 Apr 2011 11:17 -0700, "ankush chadha" <ankushchadha2003_at_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

> Thanks
> Ankush
>
>
>
>
>
>
> ________________________________
> From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
> To: ankush chadha <ankushchadha2003_at_yahoo.com>; Thorsten Schöning
> <tschoening_at_am-soft.de>; users_at_subversion.apache.org
> Sent: Thu, April 14, 2011 10:21:12 AM
> Subject: Re: svnsync error : Error while replaying commit
>
> "It should work."
>
> 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 07:13 -0700, "ankush chadha"
> <ankushchadha2003_at_yahoo.com>
> wrote:
> > Yes, that was the problem. After fixing the permissions, I initiated
> > another mirror operation that was able to sync everything.
> >
> > The issue was that A had restricted access and a branch 'B' was
> > created from A for public use. Since A was missing in the mirrored
> > branch, the mirror operation failed
> >
> > However even though the error happened due to incorrect authentication
> > scripts, the error message should have included some details about the
> > problem. When I googled for this generic error message, there was lot
> > of crap but no solution. I had to spend almost half a day to narrow
> > down this issue.
> >
> > Thanks
> > Ankush
> >
> >
> >
> >
> >
> > ________________________________
> > From: Thorsten Schöning <tschoening_at_am-soft.de>
> > To: users_at_subversion.apache.org
> > Sent: Wed, April 13, 2011 3:27:30 AM
> > Subject: Re: svnsync error : Error while replaying commit
> >
> > Guten Tag ankush chadha,
> > am Dienstag, 12. April 2011 um 18:46 schrieben Sie:
> >
> > > 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: tschoening_at_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
>
Received on 2011-04-14 20:20:49 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.