[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#394739: marked as done (unison: Upgrade breaks connection with sarge client)

Your message dated Sun, 24 May 2009 14:13:11 +0200
with message-id <20090524121311.GA22746@ipxXXXXX>
and subject line Re: Bug#394739: unison: Upgrade breaks connection with sarge client
has caused the Debian Bug report #394739,
regarding unison: Upgrade breaks connection with sarge client
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
394739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394739
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (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                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Version: 2.27.57-1+b1

Hello Sylvain,
On Mon, Oct 23, 2006 at 12:10:27AM +0200, Sylvain Le Gall wrote:
> On Sun, Oct 22, 2006 at 09:24:03PM +0200, Helge Kreutzmann wrote:
> I am ok with you concerning documentation issue :
> - i will add what is required in NEWS.Debian,
> - i will add update-alternatives to the documentation,

> So, what i propose is to keep the actual way it work and only change
> some documentation.

I just had a look at README.Debian.gz in the Lenny version of unison
and (although the text itself is a little outdated) more or less
covers these issues. Hence I think this bug can be closed.

Greetings

         Helge

-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: