From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] New: unison2.48+4.04.2, unison2.48+4.08.1 [test]
Date: Sat, 20 Nov 2021 16:09:09 -0500 [thread overview]
Message-ID: <da9d8a1a-be2c-b7d4-6af0-1e0c8210c1af@cornell.edu> (raw)
In-Reply-To: <announce.4alflfl3rr9dsrep0ppriuapee4klerpbg@4ax.com>
On 9/8/2020 4:57 PM, Andrew Schulman via Cygwin-announce wrote:
[...]
> You can install any number of these packages side-by-side. Separate
> packages are needed because in order to synchronize your files, you have to
> run compatible versions of Unison on the client and server. Two Unison
> executables are compatible if and only if:
>
> (1) They have the same first two numbers of the Unison version. For
> example, all Unison versions 2.48.* are compatible with each other. But if
> you try to use version 2.51.x to sync with a server running version 2.48.y,
> Unison will issue an error message about incompatible versions and quit.
>
> AND
>
> (2) They were built with compatible versions of the OCaml compiler.
This old problem reared its ugly head again for me, but I found a simple
solution that I'm passing on in case it's of use to others.
My situation is that for years I have been syncing my Cygwin system with a Linux
system on which I had built unison 2.48.x with OCaml 4.04.x. This is compatible
with Cygwin's unison2.48+4.04.2. But I just added a second Linux system that I
want to keep in sync with my other systems, and this one comes with a Unison
compatible with Cygwin's unison2.48+4.08.1.
It turns out that Unison's upstream maintainer is making Linux binaries
available, built with various different versions of OCaml. See, for examples,
the Assets listed under v2.51.4 at
https://github.com/bcpierce00/unison/releases
So if I install unison2.51 on Cygwin and install the appropriate binary in ~/bin
on both of the Linux machines that I want to sync with, then everything works.
For example, if I see
$ unison -version
unison version 2.51.4 (ocaml 4.12.0)
on Cygwin, then I know that I need to use
unison-v2.51.4+ocaml-4.12.0+x86_64.linux.tar.gz on the Linux machines.
It's still annoying, but not as bad as it used to be.
Ken
prev parent reply other threads:[~2021-11-20 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 20:57 Andrew Schulman via Cygwin-announce
2020-09-09 15:23 ` [ANNOUNCEMENT] " Ken Brown via Cygwin-announce
2021-11-20 21:09 ` Ken Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=da9d8a1a-be2c-b7d4-6af0-1e0c8210c1af@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).