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.

drh added on 2010-03-01 00:48:07:
Please try running with the --httptrace option, like this:

fossil clone http://whatever/ local.fossil --httptrace

The debugging output that results might give us a clue about what is going wrong.

anonymous added on 2010-03-01 18:07:52:
OK waiting for the user with the issue to run that command. I have run it but it has always worked on my machine so that's probably not useful. What part of the the report is what you want to see? Should I email you the entire report?

Also, while I have your attention, if I do have to start a new database is there a way to take all the settings and tickets from my current database to the new one without having to enter them by hand?? Like the tickets setup, users, all filled out tickets? Has this export feature been requested? If not, I guess this is my feature request. If you'd like me to put it into a new ticket I will gladly do so.

anonymous added on 2010-03-03 19:57:59:
Instead of using --httptrace to test over the internet we decided to have him create a new database and try to commit to it and he's still getting the same issue. Anyone have any idea??? I'm dying here!!!

anonymous added on 2010-03-08 00:15:29:
I just wanted to let everyone know that if they get the error I reported that it may have to do with the antivirus system you have installed. The one we had installed was Computer Associates Antiviris version 6 and it actually stopped our commits. Very odd. After an uninstall it worked fine.