On Sun, 01 May 2016 14:16:59 +0000 Daniel Alder
<debbug16.10.hac...@antichef.net> wrote:
> Package: unison
> Version: 2.48.3-1
> Severity: important
> 
> Dear Maintainer,
> 
>    * What led up to the situation?

unison marshalls data in datastructures dependent on the ocaml version
it was build with.

So even for the same version of unison you have to choose to be
compatible with e.g. Ubuntu, Debian stable, etc.

Right now if you just build unison from source on Sid it works with
Ubuntu Xenian.

But put it on hold when it works.


> I tried to sync using unison between an up-to-date Debian stretch and a 
> Ubuntu xenial host, both have the same unison version:
> 
> Debian:
> ii  unison         2.48.3-1     amd64        file-synchronization tool for 
> Unix and Windows
> Ubuntu:
> ii  unison         2.48.3-1ubuntu1         amd64                   
> file-synchronization tool for Unix and Windows
> 
> 
> I discovered that the Debian side crashes whenever a file with size 701 bytes 
> or
> bigger has to be transferred from debian to ubuntu.
> The error does NOT appear if the file on the other side doesn't exist yet.
> The error also doesn't appear if both systems are Ubuntu or if both are 
> Debian.
> 
> 
> == Here is a test matrix: ==
> 
>                          debian file
>                          =700 bytes          =701 bytes
> ubuntu file =700 bytes   d->u ok, u->d ok    d->u ok, u->d ok
>             =701 bytes   d->u ok, u->d ok    d->u err, u->d ok
> 
> explanation: d->u means transfer from debian to ubuntu, no matter which side
> runs unison, only the final direction of the file transfer is relevant, see 
> logs
> below.
> 
> 
> == Error log when running on Debian side: ==
> 
> synctest@debian:~$ unison myfolder/ ssh://$remoteip/myfolder/
> Contacting server...
> Connected [//debian//home/synctest/myfolder -> 
> //ubuntu//home/synctest/myfolder]
> Looking for changes
>   Waiting for changes from server
> Reconciling changes
> 
> local          ubuntu             
> changed  ====> changed    testfile  [] >
> 
> Proceed with propagating updates? [] y
> Propagating updates
> 
> 
> UNISON 2.48.3 started propagating changes at 13:31:35.72 on 01 May 2016
> [BGN] Updating file testfile from /home/synctest/myfolder to 
> //ubuntu//home/synctest/myfolder
> Uncaught exception Failure("input_value: bad bigarray kind")
> Raised by primitive operation at file "/tmp/buildd/unison-2.48.3/remote.ml", 
> line 453, characters 18-45
> Called from file "/tmp/buildd/unison-2.48.3/remote.ml", line 459, characters 
> 23-61
> Called from file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 75, characters 
> 20-23
> Re-raised at file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 135, 
> characters 12-13
> Called from file "list.ml", line 73, characters 12-15
> Called from file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 31, characters 
> 2-37
> Called from file "/tmp/buildd/unison-2.48.3/lwt/lwt.ml", line 83, characters 
> 17-46

-- 
Niels Elgaard Larsen

Reply via email to