[Unison-hackers] Speaking of bugs...

[Benjamin Pierce]

Doesn't look like the failure is at the point of trying to write  
anything.  I'd be interested to know whether the same thing happens  
with 2.27 -- a lot has changed since then!

    - Benjamin


On Apr 2, 2007, at 7:44 PM, David Abrahams wrote:

>
> with unison version 2.13.16, I have been trying to sync two folders
> that were copied from the same source, but have never been sync'd
> before.  One of them happens to be on a filesystem that's mounted
> read-only, but that's the only one that's been changed since the copy,
> so presumably that shouldn't make any difference.  Unison dies with an
> uncaught exception.
>
> I re-ran the sync in text mode with "-debug all" and the end of the
> run looked like the enclosed.  If the readonly mount is indeed the
> problem, is there some other way to ensure that unison won't write
> anything in one of the directory trees?
>
> <unison.log>
>
> TIA,
>
> -- 
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com
>
> Don't Miss BoostCon 2007! ==> http://www.boostcon.com
> _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers