Ticket UUID: | a9722a15d235b8220fe56794c2e89f6abbfa3f8c | ||
Title: | Fossil leaves files in inconsistent state after error | ||
Status: | Fixed | Type: | Code_Defect |
Severity: | Severe | Priority: | |
Subsystem: | Resolution: | Fixed | |
Last Modified: | 2010-01-14 15:35:44 | ||
Version Found In: | [d5695157d0] 2009-11-11 16:21:19 UTC | ||
Description & Comments: | |||
OP: Windows
performing a fossil update One file cannot be written (in our case, one DLL that was being used by an open program). Fossil gives an error and stops. The situation is the following: The name of the checkout version (given by fossil info) is the one previous to the update. All the files that had been updated prior to the error, become labelled as "EDITED". The situation is not easy to fix: "fossil update" does nothing "fossil checkout --latest --force" will miss all the legitimate changes made to the files Possible solutions:
drh added on 2010-01-13 16:02:04: fossil undo Did that not revert the files to their state before the update? anonymous claiming to be ramsan added on 2010-01-13 22:36:30: But shouldn't fossil do an automatic undo in case of error? anonymous claiming to be ramsan added on 2010-01-14 11:14:02: I have made a similar test in unix. Before the update, I've made: chmod -w file.c fossil update The update gives an error, "fossil info" points to the old version, and some of the files become marked as "EDITED" fossil undo does not work and responds: fossil: no update or merge operation is available to undo drh added on 2010-01-14 15:35:44: |