Bug#946046: not fixed

[Stéphane Glondu <glondu@debian.org>]

Le 08/08/2020 à 02:41, Vincent Lefevre a écrit :
> unison-2.48 should have never been created: buster has a unison
> package with version number 2.48.4-1, thus one has the impression
> that this is compatible with unison-2.48, while this is not the
> case. The package should have been named unison-2.48+4.08.1 right
> now to avoid this confusion.

I agree with you, retrospectively.

Note that there will never be a unison-2.48+X.XX.X for X.XX.X <> 4.08.1
since unison 2.48.x does not compile with recent versions of OCaml (and
the fix looks too invasive).

> Moreover, unison-2.48 provides /usr/bin/unison-2.48; this is not fine
> since buster also has /usr/bin/unison-2.48, which is not compatible.
> As the client will start a server with the same version number on
> the remote machine (by using the recommended "addversionno = true"),
> this means that one will likely get an archive corruption (which
> happened to me). The OCaml version must be part of the version and
> attached to the name of the unison executable.

Yes, I realized that too late. My hope is to release bullseye with
unison-2.51+X.XX.X and without unison-2.48 at all.

I still think it is useful to have a unison 2.48 compiled with OCaml
4.08.1 around.


Cheers,

-- 
Stéphane