> The man page for alternatives > (8) does not seem to specify the allowed range for priority values, but using > 2017 for unison 2.17 > and 2027 for unison 2.27 seem to upset it: > > ajm> /usr/sbin/alternatives.exe --display unison > path to alternate expected in /var/lib/alternatives/unison > ajm> > > Editing /var/lib/alternatives/unison as follows seems to fix things: > > ajm> cat /var/lib/alternatives/unison > auto > /usr/bin/unison > > /usr/bin/unison-2.17 > 17 > /usr/bin/unison-2.27 > 27 > ajm> /usr/sbin/alternatives.exe --display unison > unison - status is auto. > link currently points to /usr/bin/unison-2.27 > /usr/bin/unison-2.17 - priority 17 > /usr/bin/unison-2.27 - priority 27 > Current `best' version is /usr/bin/unison-2.27. > ajm ~>
I can't reproduce this problem on my host: $ alternatives --display unison unison - status is auto. link currently points to /usr/bin/unison-2.27 /usr/bin/unison-2.13 - priority 2013 /usr/bin/unison-2.17 - priority 2017 /usr/bin/unison-2.27 - priority 2027 Current `best' version is /usr/bin/unison-2.27. $ cat /var/lib/alternatives/unison auto /usr/bin/unison /usr/bin/unison-2.13 2013 /usr/bin/unison-2.17 2017 /usr/bin/unison-2.27 2027 > I also found a mixture of names - the new versions install "unison" symlinks, > but the older versions > installed "unison.exe" symlinks. Some of this may have been my hand edits to > fix things up though. I'm not sure. At this point I recommend that you remove and reinstall all of the unison alternatives on your host, as follows: rm /var/lib/alternatives/unison for f in /etc/postinstall/unison* ; do $f ; done and see if that clears up the problem. -- 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/
