X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org DC57F3851C1D
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1598920758;
	bh=UcTl266FY5xXpZtZFBcE6bXz/ZpXlE5+3jtg5l/+qxk=;
	h=To:Subject:Date:References:List-Id:List-Unsubscribe:List-Archive:
	List-Post:List-Help:List-Subscribe:From:Reply-To:From;
	b=ZfyinLm8Lg1ydJ7JHxJpowFTzNgA4HpK3HW1oAz5k1Vv8oLI7n/kIxPZuFta/+V3P
	7iR8+pqMrfbOuaLihhZPy/AdIEF8tD+1CN4brljGpmHK+91h9JTl3daZIdDzqk7gdo
	we7Rza16f5R+5Zds6cvvsja1UkmlBdpaGXzuAJpg=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 26CF13857C42
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] unison2.48-2.48.4-2 (Warning: possible breakage)
Date:	Mon, 31 Aug 2020 20:39:07 -0400
Message-ID:	<ed5rkft7ag48b1hfocqi3ts0sbtj2o6s9q@4ax.com>
References:	<announce DOT jaoqkf92i62p28j6mna6efgf5cg2srj8bi AT 4ax DOT com>
	<0e456fd0-0beb-6f04-40d7-836ed8b64612 AT cornell DOT edu>
Mime-Version:	1.0
X-Newsreader:	Forte Agent 4.2/32.1118
X-Archive:	encrypt
X-Spam-Status:	No, score=-2.3 required=5.0 tests=BAYES_00,
	HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Andrew Schulman via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Andrew Schulman <schulman DOT andrew AT epa DOT gov>
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

> > There is unfortunately another layer of incompatibility in Unison: Two
> > Unison executables are only compatible if they were built with the same
> > version of OCaml. 
> 
> What a mess! 

Glad you understand :)

> Would you consider embedding the OCaml version in the package name 
> as suggested by the Debian maintainer 
> (http://lists.seas.upenn.edu/pipermail/unison-hackers/2020-August/001975.html)? 
> Thus unison2.48-2.48.4-1 would be replaced by something like 
> unison2.48+4.04.1... and unison2.48-2.48.4-2 would be replace by something like 
> unison2.48+4.08.1....  That way people who are happy with unison2.48-2.48.4-1 
> can keep using it without being pestered by setup to update.

Yes, I could do that. I was hoping to avoid it, but it may be the only realistic
solution. 

It may be mainly Unison 2.48 that's affected, and maybe also 2.51 and the
forthcoming 2.52. I guess that very few people are still using the older
versions, and if they are they don't want any changes now.
 
> FWIW, here's my situation, which is probably not typical.  When you released 
> unison2.48-2.48.4-1 a few years ago, it was incompatible with the Linux server 
> that I sync with.  So I simply built OCaml and unison myself on that server, 
> using the same versions that you used, and installed unison in my own ~/bin 
> directory.
> 
> I could do that again, now using OCaml 4.08.1.  But I'd much rather just keep my 
> current arrangement, without having setup try to update unison2.48 every time I 
> run it.

Thanks, that's helpful to know. Your situation might not be unusual, I don't
know. For all I know, you and I are the only Cygwin Unison users.

So was unison2.48-2.48.4-1 built with OCaml 4.04.1? I don't remember, and I'm
not sure how to tell.

Andrew

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -