From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ciao.gmane.io (static.214.254.202.116.clients.your-server.de [116.202.254.214]) by sourceware.org (Postfix) with ESMTPS id 26CF13857C42 for ; Tue, 1 Sep 2020 00:39:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 26CF13857C42 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1kCuKO-00034K-VM for cygwin@cygwin.com; Tue, 01 Sep 2020 02:39:12 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Andrew Schulman Subject: Re: [ANNOUNCEMENT] unison2.48-2.48.4-2 (Warning: possible breakage) Date: Mon, 31 Aug 2020 20:39:07 -0400 Message-ID: References: <0e456fd0-0beb-6f04-40d7-836ed8b64612@cornell.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2020 00:39:16 -0000 > > 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