Ticket UUID: | c68b4e0f1f0874c4dff0ed24966e25ac51e7cfe5 | ||
Title: | after committing "Fossil : no such file: in -E2F0FD85......." | ||
Status: | Open | Type: | Incident |
Severity: | Severe | Priority: | |
Subsystem: | Resolution: | Open | |
Last Modified: | 2010-02-23 11:09:24 | ||
Version Found In: | 4f24addea9 | ||
Description & Comments: | |||
What we've tested.
All machines are running fossil version 4f24addea9 2009-12-20 and for all of the following machines we tried a clone from my server machine. Using The Internet: His computer running Windows 7 - Didn't work His laptop running Windows 7 - Didn't work His server running XP - DID work My Computer using my DNS:Port running Windows 7 - DID work Using My Local Network: My Computer using my localhost:port running Windows 7 - DID work My friend can't commit to the database even after cloning. He keeps getting an error message "Fossil : no such file: in -E2F0FD85.......". Nothing in the database starts with a negative and doesn't have E2F0FD85 anywhere in the timeline. This seems as if the database is corrupt but we've successfully clone/committed as specified above. Has anyone seen this kind of error before? The error occurs when I normally get the "unable to sign manifest. continue (y/N)?" message from fossil so the error is displayed after " 'gpg' is not recognized as an internal or external command, operable program or batch file.' Though I realize some of you may not see these prompts I hope someone can be of help. anonymous added on 2010-02-23 11:09:24: fossil setting clearsign 0 |