Your message dated Tue, 06 Sep 2005 01:02:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326589: fixed in unison 2.13.16-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Sep 2005 09:30:24 +0000
>From [EMAIL PROTECTED] Sun Sep 04 02:30:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from franz.ak.mind.de (k76) [212.42.235.66] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EBqpT-0000us-00; Sun, 04 Sep 2005 02:30:23 -0700
Received: by k76
        via sendmail from stdin
        id <[EMAIL PROTECTED]> (Debian Smail3.2.0.115)
        Sun, 4 Sep 2005 11:30:21 +0200 (CEST) 
From: Andreas Koenig <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: unison: is confused about its own name
X-Debbugs-CC: Andreas Koenig <[EMAIL PROTECTED]>
Date: Sun, 04 Sep 2005 11:30:21 +0200
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
        X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02

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

---------------------------------------
Received: (at 326589-close) by bugs.debian.org; 6 Sep 2005 08:08:29 +0000
>From [EMAIL PROTECTED] Tue Sep 06 01:08:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1ECYPC-0001kd-00; Tue, 06 Sep 2005 01:02:10 -0700
From: Sylvain Le Gall <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#326589: fixed in unison 2.13.16-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 06 Sep 2005 01:02:10 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 7

Source: unison
Source-Version: 2.13.16-2

We believe that the bug you reported is fixed in the latest version of
unison, which is due to be installed in the Debian FTP archive:

unison-gtk_2.13.16-2_i386.deb
  to pool/main/u/unison/unison-gtk_2.13.16-2_i386.deb
unison_2.13.16-2.diff.gz
  to pool/main/u/unison/unison_2.13.16-2.diff.gz
unison_2.13.16-2.dsc
  to pool/main/u/unison/unison_2.13.16-2.dsc
unison_2.13.16-2_i386.deb
  to pool/main/u/unison/unison_2.13.16-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvain Le Gall <[EMAIL PROTECTED]> (supplier of updated unison package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon,  5 Sep 2005 23:50:34 +0200
Source: unison
Binary: unison-gtk unison
Architecture: source i386
Version: 2.13.16-2
Distribution: unstable
Urgency: low
Maintainer: Sylvain Le Gall <[EMAIL PROTECTED]>
Changed-By: Sylvain Le Gall <[EMAIL PROTECTED]>
Description: 
 unison     - A file-synchronization tool for Unix and Windows
 unison-gtk - A file-synchronization tool for Unix and Windows - GTK interface
Closes: 308683 323859 325812 325932 326154 326395 326589
Changes: 
 unison (2.13.16-2) unstable; urgency=low
 .
   * Recommend ssh-client | openssh-client rather than ssh
   * Remove dependency between unison and unison-gtk:
     * Copy manual to unison-gtk.1
     * Install documentation in all package
     * (Closes: #308683)
   * Use "mv unison $(UNISON)" and "$(UNISON_GTK)" rather than supplying
     NAME=$(UNISON) when building (Closes: #325932, #326589, #326395, #325812)
   * Remove reference to PostScript/HTML in the manpages (Closes: #323859)
   * Reformat NEWS.Debian to limit line length to 72 (Closes: #326154)
Files: 
 e4a4b4ad399d03702b2003665938cd5f 654 net optional unison_2.13.16-2.dsc
 271ca212282eae6080b3109b8d1c78d4 10572 net optional unison_2.13.16-2.diff.gz
 6000be130298c0d84e747c4e231449fe 472258 net optional unison_2.13.16-2_i386.deb
 4874e0f6953a2bf313091ae6f69d7fbf 831858 net optional 
unison-gtk_2.13.16-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDHUrS1cqbBPLEI7wRAnbcAJ98uxaLfxWLdL27teRpYPNoD5fSQQCffHtA
8tvAzC98ZVVMkkUTV7KBqWg=
=bPi4
-----END PGP SIGNATURE-----


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

Reply via email to