Hi,
Thanks for the quick solution :-) that works well .. I could start the sync
now.
but I am still having the problem to sync the huge revision.
I will try someone suggested that set the "SVNPathAuthz off" in conf file,
will let you know the result ..
thanks again
Hellen
On Thu, Apr 17, 2008 at 2:03 AM, Murli Varadachari <
mvaradachari_at_facebook.com> wrote:
>
> For a quick and dirty fix [ make a copy first of the existing subversion
> repository ]
>
> Remove /your_repo_location/db/revs/590, 591
>
> Remove /your_repo_location/db/revprops/590, 591
>
> Change rev# in /your_repo_location/db/current back to 589
>
> Try svnsync again
>
> Cheers
> murli
>
>
>
>
> On 4/17/08 12:47 AM, "Hellen" <hellenff_at_gmail.com> wrote:
>
> Hi,
>
> I have a problem when I tried to sync a huge revision on mirror site.
> first I dumped the problematic revision from the master site. then
> manually "svnadmin load .." the dump to the mirror
> site. that looks ok from the log, but then I had problem to sync again,
> getting the following error message:
> ----------------------------
> svnsync: Revision being currently copied (590), last merged revision
> (589), and destination HEAD (591) are inconsistent; have you committed to
> the destination without using svnsync?
> ----------------------------
> I know this might be because I did the manual load to the mirror site. but
> how can I fix this?
> I did some google search, and found someone mentioned:" manual adjustment
> of the revision 0 revprops", not sure how it is related to fixing this
> problem?
>
> as the repository is already very big, I am trying to avoid re-creating
> the mirror as someone suggested. But the worse case scenario if I have to
> re-create the mirror again, how can I not let the problematic revision(a
> very large revision) fail the svnsync again?
>
> thanks much for your help
> Hellen
>
>
>
>
>
Received on 2008-04-17 12:17:23 CEST