|
2010-02-25
| ||
| 12:59 | • Fixed ticket [7c3ca0eae8]: "not a ordinary file" errors in update command plus 1 other change artifact: 85eed76eb4 user: drh | |
| 12:59 | • Ticket [7c3ca0eae8]: 2 changes artifact: e21e6045a8 user: drh | |
| 12:58 | If a file has been deleted from the filesystem, but not deleted by fossil, then make the "update" command restore that file. Ticket [7c3ca0eae8287] check-in: 63d5a4fe25 user: drh tags: trunk | |
| 07:46 | • New ticket [7c3ca0eae8] "not a ordinary file" errors in update command. artifact: e02bc5ee84 user: anonymous | |
| Ticket Hash: | 7c3ca0eae8287e75f79fdb05f2ed4942dcd2c0a0 | ||
| Title: | "not a ordinary file" errors in update command | ||
| Status: | Fixed | Type: | Code_Defect |
| Severity: | Important | Priority: | |
| Subsystem: | Resolution: | Fixed | |
| Last Modified: |
2010-02-25 12:59:45 16.10 years ago |
Created: |
2010-02-25 07:46:27 16.10 years ago |
| Version Found In: | 20100213123048 | ||
| Description: | ||||
|
With reference to ticket 15f8f4a425248c35fe0babfcb6ccf45f1d5b9932, the "not a ordinary file" problem is not restricted to the rm command. Attempting to do "fossil update" or "fossil checkout --latest" when any file has been deleted will cause a similar error.
This change in behavior appears to remove all straightforward means of restoring deleted files; multiple commands or extra scripting will be needed if one wishes to restore several files. Not to mention that it breaks existing scripts written to automate fossil processes, for unclear reasons. drh added on 2010-02-25 12:59:37: | ||||