[MacPorts] #46259: unison @2.40.102_2: Unable to sync (was: Unable to sync with new update 2.40.102_2)

[MacPorts]

#46259: unison @2.40.102_2: Unable to sync
-----------------------------+--------------------------------
  Reporter:  silencer1127@…  |      Owner:  macports-tickets@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  unison          |
-----------------------------+--------------------------------
Description changed by ryandesign@…:

Old description:

> I'm a newbie in this community but a long-time user of unison.
>
> There might be a small bug in the most recent update of unison @
> 2.40.102_2
>
> Begin Error Output
> ----------------------------------------------
> Uncaught exception Failure("input_value: bad bigarray kind")
>
> Fatal error: Lost connection with the server
> ------------------------------------------------
> End Error Output
>
> Client Platform: Mac Pro with OSX 10.9.5
>
> Server Platform: Dell Precision with Linux Mint 17 Mate x64
>
> This error happened quite often but not every time. Also most of the time
> when this error occurred, it can be fixed by manually copy the needed
> files over and sync with unison again.
>
> This never happened with 2.40.102_1 and when activate the old version
> back, the error disappeared as well.
>
> Hope this helps identify the problem.
>
> Thanks!

New description:

 I'm a newbie in this community but a long-time user of unison.

 There might be a small bug in the most recent update of unison @
 2.40.102_2

 {{{
 Begin Error Output
 ----------------------------------------------
 Uncaught exception Failure("input_value: bad bigarray kind")

 Fatal error: Lost connection with the server
 ------------------------------------------------
 End Error Output
 }}}

 Client Platform: Mac Pro with OSX 10.9.5

 Server Platform: Dell Precision with Linux Mint 17 Mate x64

 This error happened quite often but not every time. Also most of the time
 when this error occurred, it can be fixed by manually copy the needed
 files over and sync with unison again.

 This never happened with 2.40.102_1 and when activate the old version
 back, the error disappeared as well.

 Hope this helps identify the problem.

 Thanks!

--

-- 
Ticket URL: <https://trac.macports.org/ticket/46259#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X