> I am _not_ the maintainer
I'm the Cygwin maintainer for Unison.
> but 2.9.1 is the only version I have that
> will talk to a current development machine -- a current debian machine too.
My Debian host has
$ apt-cache policy unison
unison:
Installed: 2.13.16-6
Candidate: 2.13.16-6
Version table:
*** 2.13.16-6 0
990 http://http.us.debian.org testing/main Packages
300 http://http.us.debian.org unstable/main Packages
100 /var/lib/dpkg/status
2.13.16-5 0
200 http://http.us.debian.org stable/main Packages
So I'm guessing that your development server is still using a locally
installed copy from a long while back, and the sysadmins haven't updated.
Or, they may have a newer version such as 2.13 installed too, and you only
need to change which version your client talks to, e.g.
unison -servercmd /usr/bin/unison-2.13.16
or some such.
which -a unison
ls /usr/{,local/}bin/unison*
might provide some useful information here.
> Maybe we should release 2.27 as an ahead package -- or a seperate one
> that RENAMES the old ones to 'unison-versionname' so that when the newer
> version is used to try and talk to the old one, the side the user is on
> will fall back to the old version...
No need to rename any current versions, since they're already named by their
version numbers:
$ cd /usr/bin
$ ls -o unison*
-rwxr-x---+ 1 aschulma 956416 Aug 25 2005 unison-2.10.2.exe*
-rwxr-x---+ 1 aschulma 962560 Aug 25 2005 unison-2.12.0.exe*
-rwxr-x---+ 1 aschulma 974336 Aug 25 2005 unison-2.13.exe*
-rwxr-x---+ 1 aschulma 991232 Aug 25 2005 unison-2.17.exe*
-rwxr-x---+ 1 aschulma 889344 Aug 25 2005 unison-2.9.1.exe*
-rwxr-x---+ 1 aschulma 907264 Aug 25 2005 unison-2.9.20.exe*
lrwxrwxrwx 1 aschulma 28 Mar 1 09:44 unison.exe ->
/etc/alternatives/unison.exe*
Andrew.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
