Thus said Richard Hipp on Mon, 13 Jul 2015 15:34:28 -0400:

> Let's hope it  was the "make clean" and not  the "fossil rebuild" that
> cleared the problem....

It's very likely the make clean.

However, last week I had been rebuilding while tracking down a different
problem  which  required crossing  a  schema  change boundary  and  it's
possible that the database was in an unexpected state.

I still think it more likely that make clean and make did the trick.

Thanks,

Andy
--
TAI64 timestamp: 4000000055a415ba
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to