Great! Thanks for the tip, and hope the bug is found... Best regards, Ron
On 06/12/2014 05:43 PM, Richard Hipp wrote: > > > > On Thu, Jun 12, 2014 at 10:40 AM, Ron Aaron <r...@ronware.org > <mailto:r...@ronware.org>> wrote: > > Sorry for the vague message, but I don't have a specific test case. > > Twice this week, I encountered a situation where I did a commit > from one > machine, and an update from the second -- and the second did not > get the > latest updates. > > The first time was about a week ago; the second time was a few minutes > ago where I've updated all machines to the latest Fossil. > > Any ideas on what to do if this happens again? So far my only > recourse > has been to clone again, since nothing else fixed the problem. > > > Add the --verily option to the "fossil sync" and that should clear the > problem. > > There is a bug somewhere that causes this. We haven't been able to > locate it yet. Running sync once with --verily clears that problem > such that it normally does not occur again. > > > -- > D. Richard Hipp > d...@sqlite.org <mailto:d...@sqlite.org> > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
