Opened 12 years ago

Closed 11 years ago

#35116 closed defect (fixed)

unison fails with "index out of bounds"

Reported by: rolf.lochbuehler@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.1
Keywords: Cc: me@…, dcecchin@…, jdswinbank (John Swinbank), ryandesign (Ryan Carsten Schmidt), ob+macport@…, someuser12, jrblevin@…
Port: unison

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I've been using unison to sync certain directories on an 2008 iMac and a 2010 Macbook. This used to work up until a week ago or so. Today, whenever I start unison, it copies a few files, but eventually aborts with this message:

  <file> has already been transferred

  Invalid argument: index out of bounds

  Fatal error: Lost connection with the server

This error is not triggered by a specific file. If I have unison start in a different directory it runs into the same error.

Applies to unison 2.40.65. Macports installations are up to date on both Macs as of today, see attached list of installed revisions. Both Macs run Mac OS X 10.7.4.

Attachments (1)

installed.txt (10.4 KB) - added by rolf.lochbuehler@… 12 years ago.
Output of "port list installed"

Download all attachments as: .zip

Change History (14)

Changed 12 years ago by rolf.lochbuehler@…

Attachment: installed.txt added

Output of "port list installed"

comment:1 Changed 12 years ago by rolf.lochbuehler@…

Forgot to mention that I ran "port upgrade outdated" on both systems earlier today, although I believe that this did not upgrade the unison package. However, I don't remember anything else that could have triggered this problem.

comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Port: unison added

comment:3 Changed 12 years ago by me@…

I have reproduced this as described. Replacing the binary with the 2.40.69 binary from the Unison home page fixes the problem. MacPorts reports the version of Unison to be 2.40.65 which is not a stable build, so I'm not sure how it ever reached MacPorts?

Unison is currently unusable until this is fixed.

comment:4 Changed 12 years ago by me@…

Cc: me@… added

Cc Me!

comment:5 Changed 12 years ago by me@…

r88712 - the previous revision - works fine, so could the current revision be rolled back, at least?

comment:6 Changed 12 years ago by dcecchin@…

Cc: dcecchin@… added

Cc Me!

comment:7 Changed 12 years ago by jdswinbank (John Swinbank)

Cc: swinbank@… added

Cc Me!

comment:8 in reply to:  3 ; Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

Replying to me@…:

MacPorts reports the version of Unison to be 2.40.65 which is not a stable build, so I'm not sure how it ever reached MacPorts?

It reached MacPorts by someone updating the port to that version, someone who was probably unaware that this was not a stable build. In #35639 I plan to replace the current unison port with a new unison240 port, and based on your statement here, I plan to make it the latest stable version, which as far as I can tell is 2.40.63.

comment:9 Changed 12 years ago by ob+macport@…

Cc: ob+macport@… added

Cc Me!

comment:10 Changed 12 years ago by someuser12

Cc: macosx12345@… added

Cc Me!

comment:11 Changed 11 years ago by jrblevin@…

Cc: jrblevin@… added

Cc Me!

comment:12 in reply to:  8 Changed 11 years ago by someuser12

Replying to ryandesign@…:

In #35639 I plan to replace the current unison port with a new unison240 port, and based on your statement here, I plan to make it the latest stable version, which as far as I can tell is 2.40.63.

FWIW: the latest stable version is now 2.40.102. The patch I submitted in #35407 to allow compilation with the X11 interface (x11 variant) is still needed.

comment:13 Changed 11 years ago by ecronin (Eric Cronin)

Resolution: fixed
Status: newclosed

Updated to 2.40.102 in r100034 which should fix this.

Note: See TracTickets for help on using tickets.