Ticket Hash: | 375e5703329a743339c3b6399d7c41a8c98c7a24 | |||
Title: | fossil: bad object id: 0 on up | |||
Status: | Fixed | Type: | Code_Defect | |
Severity: | Critical | Priority: | ||
Subsystem: | Resolution: | Fixed | ||
Last Modified: | 2010-11-25 01:52:57 | |||
Version Found In: | 71ad9b62a7 | |||
Description: | ||||
Just ran fossil pull and then tried to run fossil up with fossil version [71ad9b62a7] 2009-12-31 14:59:03 UTC on the fossil repository and received this error "fossil: bad object id: 0 on up". I ran fossil rebuild and still get the same error.
jeremy_c added on 2010-01-01 01:31:42: jeremy_c added on 2010-01-01 01:32:21: anonymous added on 2010-01-01 01:37:09: anonymous added on 2010-01-11 06:40:35: anonymous added on 2010-01-11 06:44:45: anonymous added on 2010-10-23 23:07:21: This is fossil version [b48f78964e] 2010-09-18 15:51:43 UTC on the fossil repo. drh added on 2010-10-24 22:55:25: fossil update --latest fossil update trunk fossil update version-number Instead of just: fossil update The problem is here that fossil is having trouble figuring out what version it needs to update to. If you give it a hint, it will normally keep going without trouble. It would help to have a reproducible test case. anonymous added on 2010-10-25 20:09:02: sqlite3 $repo 'select uuid from blob order by uuid' for both repo files. anonymous claiming to be viric added on 2010-11-24 22:18:21: drh added on 2010-11-25 01:52:57: |