Package: unison Version: 2.13.16-5 Severity: normal Up to todays upgrade of unison, connecting with sarge clients (by setting the appropriate communication version) worked. Now I get: Fatal error: Received unexpected header from the server: expected "Unison 2.13\n" but received "Unison 2.9.1\n\000\000\000\000", which differs at "Unison 2.9". 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.
To get it working, I needed to install unison2.9.1 *and* run
update-alternatives --config unison
An upgrade should not break a working setup like this (requiring
installation of additional software *and* reconfiguring). I vaguely
remember having done this when switching to Testing quite a while back
already.
At least a NEWS.Debian should tell users what to do. And it should not
occure every time a new version of unison is released (i.e., a new
version should be installed additional at with lower priority in
update-alternatives), activating it should be left to the user.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.7-grsec-cz01
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages unison depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
Versions of packages unison recommends:
ii openssh-client [ssh-client] 1:4.3p2-5 Secure shell client, an rlogin/rsh
-- no debconf information
--
Dr. Helge Kreutzmann [EMAIL PROTECTED]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
