Description of problem:
Unison of Mga 6 does not want to work with Unison of Mga 5.
Even if it is probably a Unison upstream issue, this means that no synching is possible between Mga 5 and Mga 6 instances. People with that sync or backup several Mga systems with Unison but can't upgrade all systems at once will have a big problem with this. Since synching means the use of several systems, and people rarely can upgrade all systems at once, this means in practice that Unison becomes unusable. This can be easily avoided by adding Unison 2.40 in Mga 6 as alternative version next to 2.48. That way people can continue to use Unison on 2.40 untill all systems have been upgraded.
Assigning to unison maintainer, but CC'ing all packagers collectively, because I don't remember having seen the maintainer around recently.
marja11, pkg-bugsSource RPM:
Hello, unison Mageia 6 not working with unison mageia 7.
The error message is :
Received unexpected header from the server:
expected "Unison 2.48\n" but received "Unison 2.51 with OCaml >= 4.01.2\n\000\000\000\000\017",
which differs at "Unison 2.5".
This can happen because you have different versions of Unison
installed on the client and server machines, or because
your connection is failing and somebody is printing an error
message, or because your remote login shell is printing
something itself before starting Unison.
Is it possible to have an update of unison on Mageia 6, with the same version of Mageia 7, please ?
Please test unison-2.51.2-1.mga6 in Core/updates_testing!
It's Ok for me.
The synchronization beetwen Mga6 & Mga 7 work fine.
Assigning to QA now,
Since mageia7 is out with a more recent unison version as mageia6, the synchronization between both can't work anymore.
So this updates unison to the same version as mageia7.
Packages in 6/core/updates_testing:
Unison Mga 6 not working with Mga 5 Unison =>
Unison Mga 7 not working with Mga 6 Unison