On Tue, Aug 16, 2011 at 4:52 PM, Christopher Vance <[email protected]>wrote:
> On Mon, Aug 15, 2011 at 9:47 PM, Richard Hipp <[email protected]> wrote: > > How about "fossil test-integrity"? > > fossil: checksum mismatch on blob rid=7657: > da39a3ee5e6b4b0d3255bfef95601890afd80709 vs > 76ce4c2d48d71c1c50113303fa40dbf1805bfad7 > > But I also notice that a fresh clone from www.fossil-scm.org on two > different OSs shows > > fossil: checksum mismatch on blob rid=2: > da39a3ee5e6b4b0d3255bfef95601890afd80709 vs > f62f7b3cc4dfa0516391806d2c1276dd170be809 > What OS are you using? Did you build Fossil yourself, or are you using a precompiled binary? What does "fossil version" tell you? To repair the problems above, run either sqlite3 or "fossil sql" against the repo and type: DELETE FROM blob WHERE rid=7657; ... or whatever the faulty rid is. Then do "fossil rebuild; fossil sync". > > So this is clearly not unusual. > > Next I'll do a sqlite3 .dump and see what I can discover ferretting around. > > > > >> > >> Any suggestions? Any other information I can provide? > > -- > Christopher Vance > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
