4 ms·
I'm a maintainer of the Unison package in Fedora and I'd love to know which version(s) of Unison you use day to day. In Fedora (and I think this applies in Deb
by rwmj 7y ago
I'm a maintainer of the Unison package in Fedora and I'd love to know which version(s) of Unison you use day to day.
In Fedora (and I think this applies in Debian too) we have to maintain 3 versions because Unison isn't interoperable across minor releases. For this reason we package 2.13, 2.27 and 2.40, and I think there is discussion about packaging the latest release too. Keeping these ancient (esp 2.13) versions going is a pain to say the least.
- carapace 7y ago> Unison isn't interoperable across minor releases. Ouch! FWIW, Thanks for all your work.
- raegis 7y agoI use it in Debian, which used to (until recently) package 2 versions in every release. This was convenient for me, a conservative user, who might run old-stable on some computers for months before upgrading to stable. I have used workarounds in the past (mount home directory in a container, and sync from within) so I'm fine with a single version in Debian. But you package for Fedora, which is "upstream" for RHEL (if I'm not mistaken) with their 10 year life cycles, so I'm sure RHEL customers would love you to keep as many versions available as possible :)
- LeoPanthera 7y agoThis incompatibility is one of the reasons why I reduced my dependency on it, though I still use it for minor things. The last straw came when it turns out that unison was incompatible with the same version, if that version had been built on a different system. I can't remember the details but there was some library version difference that results in a unison that has the same version number but wouldn't talk to one from another system without crashing. Drove me crazy.
- mjn 7y agoThat can happen because unison uses OCaml's built in serialization, which isn't guaranteed to be stable across OCaml versions. It doesn't often change, but the representation of arrays was changed in OCaml 4.02, which meant unison compiled with 4.01 couldn't sync with unison compiled with 4.02. Debian bug discussing the issue: https://bugs.debian.org/802919 https://bugs.debian.org/802919
- rstuart4133 7y ago> which isn't guaranteed to be stable across OCaml versions Oh, so OCaml is a toy language from academics. I've read so many good things about it over the years, but no one mentioned that aspect of it. There should be a law about putting a warning in Big Red Letters on the box so someone doesn't make the mistake of using it in a large, long lived project.
- ernst_klim 7y ago> Oh, so OCaml is a toy language from academics. What? Why did you conclude so? > but no one mentioned that aspect of it. Really? Did you open the documentation? It's stated explicitly. https://caml.inria.fr/pub/docs/manual-ocaml/libref/Marshal.html https://caml.inria.fr/pub/docs/manual-ocaml/libref/Marshal.h... > There should be a law about putting a warning in Big Red Letters on the box so someone doesn't make the mistake of using it in a large, long lived project. It's documented, and it's not intended to be used for serialization, you use it in very particular cases, for example for faster object sharing with IPC for multicore. We use Json or S-expressions or other stuff for that purposes. I really don't know why unison people don't switch to a proper serialization.
- extempore 7y agoThis was very upsetting when it happened. The same version of unison was incompatible with itself if they had been built with different but consecutively released versions of the ocaml compiler. I feel like using compiler versions like 4.01 and 4.02 is irresponsible when it's documented that they produce binary incompatible products, but that is how it was. https://marc.info/?l=unison-users&m=142286809310149 https://marc.info/?l=unison-users&m=142286809310149
- rlonstein 7y agoThis has bit me a couple of times and is currently an issue between my Linux and Mac systems. Annoying but it works so well that I build it locally.
- kurlberg 7y agoAn ugly way around it is to compile your own version of unison. The good news, if I remember correctly, is that the binary can be built in one place and copied around to the other hosts (and say put in $HOME/bin.)
- LeoPanthera 7y agoI was syncing between OS X and FreeBSD, so sharing a binary wasn't possible.
- jojoo 7y agothat was one of my biggest problems ~8 years ago. keeping the macports and the debian versions in sync was too tiresom, someday i just switched to rsync which worked well enough for my usecase.
- trm42 7y agoYep, this is PITA as a user as well. 2.48.4 on Ubuntu 18.04 but finding about the same working version for Mac required additional hunting. But nevertheless Unison is awesome. Been using for the last 15 years or so <3
- avhception 7y agoThanks for your work! At the moment I'm running unison on Gentoo, Fedora and even FreeBSD hosts. There is even a ppc64le host running Fedora. On Fedora I'm using unison251-text from the croadfeldt/Unison COPR. On Gentoo it's net-misc/unison-2.51.2, on FreeBSD it's unison-nox11-2.51.2 from pkg.
- ufo 7y agoThank you for your work! I use Unison on Fedora almost every day. The version is 2.40, which IIRC is the default you get from "dnf install unison". My use-case is that I run Unison on two computers running Fedora, to implement a form of "sneakernet" file sync. Work computer <-> usb thumb drive <-> home computer. I wasn't aware that the exact version of Unison was so important. Will start paying attention to that.
- nelgaard 7y ago2.48.4 mostly. I use it on different versions of Debian and Ubuntu. For a while I had to compile Unison from source to make it work everywhere.