Comment 22 for bug 1568459

I had the same problem as reported in #21. The solution was to delete a cache file (fp...) in the .unison directory.
If you run unison with '-debug all', it should log the offending cache file right before it reports the exception (at least it did for me).