Overview
Artifact ID: | 90d968cd0b9dcd2f8a691713d325efcdc165802a |
---|---|
Ticket: | 375e5703329a743339c3b6399d7c41a8c98c7a24
fossil: bad object id: 0 on up |
User & Date: | anonymous 2010-10-25 20:09:02 |
Changes
- Appended to comment:
<hr /><i>anonymous added on 2010-10-25 20:09:02:</i><br /> Could this be a result of fossil deciding that an artifact already exists locally because it is in a cluster? If you hit this case, please do a second clone and see if it still shows the problem. If it doesn't, compare the output of sqlite3 $repo 'select uuid from blob order by uuid' for both repo files.