On Fri, Jun 29, 2012 at 5:33 AM, Jacek Cała <jacek.c...@gmail.com> wrote:
> Hi, > > I've been doing some code maintenance (lots of deletes, renames, adds) > and now cannot do commit. Every commit attempt causes: > > > fossil.exe: manifest file (1816) is malformed. > > What does this mean? Is there any chance to fix the repo? My fossil > version is 1.22. > It means there is a bug in Fossil. Can you please send me the complete output from trying to do your commit but with the --test option added? Note that the changes to the repository happen inside a transaction. This bug was detected by a self-check phase that occurs just prior to transaction commit. The self-check phase is designed to detect problems before they can cause repository corruption, and to rollback faulty commits before they actually occur, which is exactly what is happening here. This is one of the big advantages of using a transactional database engine as the repository, rather than a pile-of-files as in other VCSes - bugs are annoying but do not cause repository corruption. > > Jacek > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
