Overview
Artifact ID: | 7bdca4e9a4b8e3b6ce58981a1910bef00d4d4897 |
---|---|
Ticket: | e816200f9503cc1167b4538c72789e1ed09231a9
Shunning cause Assertion failure! |
User & Date: | chi 2009-06-10 18:11:49 |
Changes
- comment changed to:
Please consider the following <verbatim> mkdir bug; cd bug fossil new repos.fsl fossil open repos.fsl date > file.dat fossil add file.dat fossil ci -m "checkin 1" -nosign date > file.dat fossil ci -m "checkin 2" -nosign date > file.dat fossil ci -m "checkin 3" -nosign fossil ui </verbatim> If I now shun the revision of "checkin 1" and rebuild the repository, then the timeline will show "checkin 2" as the very first checkin! But if I now select "checkin 2" in the browser and chose to view its ancestors, an error occured and following message will be shown in my browser: <verbatim>Assertion failed: (e>0), function bag_insert, file bag_.c, line 102.</verbatim> However, if I <samp>deconstruct</samp> and <samp>reconstruct</samp> the repository, the "checkin 2" will really be the first checkin and clicking its ancestors will refer to itself, what I would consider a better solution. Please let me know, if more information is needed ... Ciao,<br> chi.
- foundin changed to: "5882d97495"
- private_contact changed to: "63f4cb9d6971f7dbdee05412b8546975182b32e4"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to: "Shunning cause Assertion failure!"
- type changed to: "Code_Defect"