2013/10/4 Stephan Beal <sgb...@googlemail.com>:
> That's essentially how libfossil reports the errors for this case. At this
> point i don't know if Ron's problem is caused at parse-time (i don't think
> so - IIRC, manifest parsing errors are immediately fatal) or if it's trying
> to load a manifest which is not there (which i find hard to believe), or
> some such. If i can get a copy of the manifest i can run it through the
> libfossil manifest parser as a sanity check :).
Fully agreed! I also don't think that the parser is the problem, maybe
it's a bug somewhere else which does not properly "fossilize" some
field which ends up in the manifest later. My hope is that the
parser can tell exactly what the problem is, so the real bug can
be found easily. I don't think the bug is in the parser.
If Ron manages to produce this error-message, he will not
be the only one....
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
