Richard, Would love to share repositories but would be violating my IP agreements:( So I'll need to try and trigger the problem with non-business data.
Thanks for the reference to "fossil sync --verily" On Sun, Aug 18, 2013 at 11:36 AM, Richard Hipp <d...@sqlite.org> wrote: > I think there is a bug in the sync algorithm that sometimes causes it to > quit before both sides are fully synced up. But I don't yet have a > reproducible test case, so it is a hard problem to fix. > > If you find a pair of repositories that are not fully syncing, please do > this: > > (1) Make backup copies of the repositories on both sides of the exchange > and make them available to me for debugging. > > (2) Run "fossil sync --verily" which is a heavy-duty sync that has a > simpler design that uses more bandwidth but which is also much more likely > to run to completion. A single "fossil sync --verily" is probably > sufficient to get the two repos talking again after which ordinary syncs > (without the --verily option) should be sufficient again. > > -- > D. Richard Hipp > d...@sqlite.org > -- Clive Hayward
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
