Package: unison
Version: 2.13.16-1
Severity: serious

The recent upgrade to 2.13.16 broke unison in many ways simultaneously
and only the help of strace, my instinct, and definitely not the error
messages helped me get it running again. Maybe I have an installation
that the developers did not test?

I'm not sure which version of unison I upgraded *from*. I do have
2.13.16 no on both servers. Both are Debian.

I have only the package unison installed. I never cared about
unison-gtk and never installed it. Maybe this is a situation that the
developers had not expected?

When I started unison-latest-stable, it complained

    Usage: unison-2.13.16-gtk [options]
        or unison-2.13.16-gtk root1 root2 [options]
        or unison-2.13.16-gtk profilename [options]

    For a list of options, type "unison-2.13.16-gtk -help".
    For a tutorial on basic usage, type "unison-2.13.16-gtk -doc tutorial".
    For other documentation, type "unison-2.13.16-gtk -doc topics".
    zsh: exit 1     unison-latest-stable

Note, the ubiquitous suffix "-gtk". Of course, as I said above, I do
and did not have the unison-2.13.16-gtk installed, so it is bug #1
that the Usage output tells me to use a program that I have not
installed.

I found out that the unison-latest-stable call had created a
~/.unison-2.13.16-gtk/ directory. Watching strace I came to the
conclusion that I would have to move the contents of my ~/.unison/
directory into that new directory and so I did. Is it intentional that
the ~/.unison/ directory is ignored completely? I'd call this bug #2.

So then I called

    >11:16:47 [EMAIL PROTECTED]:~% unison-latest-stable default     
    Contacting server...
    zsh: command not found: unison-2.13.16-gtk
    Fatal error: Lost connection with the server

Oh my, same thing here. I do not have installed the -gtk stuff on the
remote server either. Why does my local version of unison suppose that
I have? This seems to me bug #3.

I went to the remote server and created a symlink from
/usr/bin/unison-2.13.16 to unison-2.13.16-gtk and this resolved the
issue completely.

I hope, my descriptions help to find the root of the evil. Thanks for
providing unison!

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages unison depends on:
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an

Versions of packages unison recommends:
ii  ssh                           1:4.1p1-7  Secure shell client and server (tr

-- no debconf information

-- 
andreas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to