On 2022-02-23 00:23:17 +0100, Vincent Lefevre wrote: > Like with unison-2.51+4.11.1 (Debian bug 990694), -addversionno is > broken: > > $ unison-2.51+4.13.1 -addversionno foo ssh://localhost/foo2 > Unison 2.51.5 (ocaml 4.13.1): Contacting server... > Connected to zira (from ::1) > OS: Debian GNU/Linux bookworm/sid [x86_64] > DISPLAY: localhost:10.0 > zsh:1: command not found: unison-2.51 > Fatal error: Lost connection with the server > > Since the symlink unison-2.51 should currently point to the stable > version unison-2.51+4.11.1 (due to the old bug 990694) in order to > be able to synchronize with Debian/stable machines, there is no > real workaround. Fortunately, it seems that unison-2.51+4.11.1 and > unison-2.51+4.13.1 are completely compatible, no that nothing breaks > yet. But with a potentially incompatible future version, this could > make unison unusable when one has both Debian 11 bullseye and unstable > (future Debian 12) remote machines.
Note: this applies to 2.51-based version only, as it seems that 2.52.0 will use "ocaml-independent protocols" according to a message in the unison-users mailing-list. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
