Package: unison Version: 2.51+4.11.1 Severity: wishlist >From time to time, unison changes internal protocol and enforce version checking before syncing. That renders the packaged version unusable when the admin use mixed distributions. I see your workflow is based on the principle that all boxes use the same version of unison (ideally the latest one), which is quite pretentious. I often mix stable and testing distros for instance, but the same problems could happen in other networks where, multiple distros and/or versions are in use.
Maybe using the alternatives mechanism and allowing the admin to choose the main version to use is a first improvement. A better approach could be always run a versioned unison (/usr/bin/unison-X.YZ where X.YZ is the right version at run time) on the remote side and eventually an unversioned executable as a last resort choice. This could be provided as a patch or discussed with upstream for pros and cons. That's my 2 cents, as always. -cheers -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-12-amd64 (SMP w/32 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unison depends on: ii libc6 2.28-10 Versions of packages unison recommends: ii openssh-client [ssh-client] 1:7.9p1-10+deb10u2 Versions of packages unison suggests: pn unison-all <none> -- no debconf information
