Konstantin Khomoutov wrote: > The principal author of fossil offered you direct help [1], > wasn't that more than enough to expect in a situation like this? ;-)
Richard seem busy - after sending him the repository and other information, he hasn't got back to me with any suggestions of how to proceed. Part of the idea of a mailing list is that there is possibility of spreading the support load over more than one person, hence my follow up email. I was hoping for a "see this command" type response to fix something that seemed to happen pretty easily. So since little help has been forthcoming so far, I've compiled the source up (not without trouble, both fossil and zlib seem to have some things missing from their Makefile.msc files, not to mention mismatches /MD /MT options), and sprinkled printf's around the code that leads up to the error. This pointed me in the direction of the renames (no surprise since they were the last thing I did). Reverting the renames seem to have cured the problem. [BTW., the "fossil info" output for a rename seems to be lacking - it should really show both the old and new filename, otherwise it's hard to figure out what happened.] I have since been trying to reproduce the problem, but with no success so far. Something to do with moving/renaming files from one directory to another. The problem was detected in manifest.c/manifest_parse() for case 'F', "fossil_strcmp(p->aFile[i-1].zName, zName)>=0". It seemed to be comparing one of the renamed files to another file in the old directory (I think old, but could be new - see above about the info output). Graeme Gill. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
