Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #189751 > unrolled thread

unison compatibility in stretch

Back to article view | Back to linux.debian.user

Contents

  unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-10 13:30 +0100
    Re: unison compatibility in stretch Joe <joe@jretrading.com> - 2017-12-10 15:10 +0100
    Re: unison compatibility in stretch "Juan R. de Silva" <juan.r.d.silva@gmail.com> - 2017-12-10 16:40 +0100
    Re: unison compatibility in stretch Eric S Fraga <e.fraga@ucl.ac.uk> - 2017-12-10 20:50 +0100
      Re: unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-11 11:40 +0100
        Re: unison compatibility in stretch Curt <curty@free.fr> - 2017-12-12 10:00 +0100
          Re: unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-12 11:20 +0100
            Re: unison compatibility in stretch Curt <curty@free.fr> - 2017-12-12 13:40 +0100
            Re: unison compatibility in stretch David Margerison <deltam@electrosonics.com.au> - 2017-12-12 15:10 +0100
        Re: unison compatibility in stretch Eric S Fraga <e.fraga@ucl.ac.uk> - 2017-12-12 13:00 +0100
          Re: unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-13 14:00 +0100
            Re: unison compatibility in stretch Eric S Fraga <e.fraga@ucl.ac.uk> - 2017-12-13 14:40 +0100
              Re: unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-13 15:10 +0100
                Re: unison compatibility in stretch Curt <curty@free.fr> - 2017-12-13 16:50 +0100
                  Re: unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-13 17:50 +0100
                    Re: unison compatibility in stretch Anders Andersson <pipatron@gmail.com> - 2017-12-13 18:40 +0100
                      Re: unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-13 18:50 +0100
                        Re: unison compatibility in stretch Tony van der Hoff <lists@vanderhoff.org> - 2017-12-29 12:30 +0100
                          Re: unison compatibility in stretch Eric S Fraga <e.fraga@ucl.ac.uk> - 2017-12-29 17:10 +0100

#189751 — unison compatibility in stretch

Hi,

For years I've been using unison to keep common files amongst my various
systems.

I now find that stretch provides version 2.48, whereas Jessie provided
2.40, and they are not compatible. My server, which still runs Jessie,
will therefore not accept connections from my desktop box.

In the passt, I've always worked round this by installing the lower
version on my desktop and adjusted the links. This appears no lnger to
be possible.

Does anyone know how to get round this? (I've no immediate intention to
upgrade the server).

[toc] | [next] | [standalone]

#189754

On Sun, 10 Dec 2017 12:25:42 +0000
Tony van der Hoff <lists@vanderhoff.org> wrote:

> Hi,
> 
> For years I've been using unison to keep common files amongst my
> various systems.
> 
> I now find that stretch provides version 2.48, whereas Jessie provided
> 2.40, and they are not compatible. My server, which still runs Jessie,
> will therefore not accept connections from my desktop box.
> 
> In the passt, I've always worked round this by installing the lower
> version on my desktop and adjusted the links. This appears no lnger to
> be possible.
> 
> Does anyone know how to get round this? (I've no immediate intention
> to upgrade the server).
> 

a) Do it the hard way with rsync and ssh?

b) Do it the cumbersome way by exporting samba/nfs mounts and running
Unison 'locally'?

I do the latter, as everything I want to synchronise is kept on my
server on samba shares, where it is also accessible from my Windows
laptop with FreeFileSync (yes, I do know there's a Unison for Windows).

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#189758

On Sun, 10 Dec 2017 12:25:42 +0000, Tony van der Hoff wrote:

> Hi,
> 
> For years I've been using unison to keep common files amongst my various
> systems.
> 
> I now find that stretch provides version 2.48, whereas Jessie provided
> 2.40, and they are not compatible. My server, which still runs Jessie,
> will therefore not accept connections from my desktop box.
> 
> In the passt, I've always worked round this by installing the lower
> version on my desktop and adjusted the links. This appears no lnger to
> be possible.

Why do you say:"It is no longer possible"? I'm currently running Jessie 
on my desktop and Stretch on laptop. I installed on both Unison 2.40 and 
synchronize them without any problem.

[toc] | [prev] | [next] | [standalone]

#189764

[Multipart message — attachments visible in raw view] — view raw

On Sunday, 10 Dec 2017 at 12:25, Tony van der Hoff wrote:

[...]

> In the passt, I've always worked round this by installing the lower
> version on my desktop and adjusted the links. This appears no lnger to
> be possible.
>
> Does anyone know how to get round this? (I've no immediate intention to
> upgrade the server).

There is the -addversionno option which allows use to use different
versions of unison on the server end.  Try this out (without adjusting
any links).

-- 
Eric S Fraga via Emacs 27.0.50, org 9.1.4

[toc] | [prev] | [next] | [standalone]

#189779

On 10/12/17 19:40, Eric S Fraga wrote:
> On Sunday, 10 Dec 2017 at 12:25, Tony van der Hoff wrote:
>
> [...]
>
>> In the passt, I've always worked round this by installing the lower
>> version on my desktop and adjusted the links. This appears no lnger to
>> be possible.
>>
>> Does anyone know how to get round this? (I've no immediate intention to
>> upgrade the server).
> There is the -addversionno option which allows use to use different
> versions of unison on the server end.  Try this out (without adjusting
> any links).
>
No:

tony@tony-lx:~$ unison -addversionno tony
Contacting server...
bash: unison-2.48: command not found
Fatal error: Lost connection with the server

[toc] | [prev] | [next] | [standalone]

#189812

On 2017-12-11, Tony van der Hoff <lists@vanderhoff.org> wrote:
> On 10/12/17 19:40, Eric S Fraga wrote:
>> On Sunday, 10 Dec 2017 at 12:25, Tony van der Hoff wrote:
>>
>> [...]
>>
>>> In the passt, I've always worked round this by installing the lower
>>> version on my desktop and adjusted the links. This appears no lnger to
>>> be possible.
>>>
>>> Does anyone know how to get round this? (I've no immediate intention to
>>> upgrade the server).
>> There is the -addversionno option which allows use to use different
>> versions of unison on the server end.  Try this out (without adjusting
>> any links).
>>
> No:

What, no? Yes (WVSVNTB).

> tony@tony-lx:~$ unison -addversionno tony
> Contacting server...
> bash: unison-2.48: command not found
> Fatal error: Lost connection with the server
>
>

* workaroundable via symlink version number truncation bug

-- 
"The world is full of shipping clerks who have read the Harvard Classics."
— Charles Bukowski

[toc] | [prev] | [next] | [standalone]

#189815

On 12/12/17 08:50, Curt wrote:
> On 2017-12-11, Tony van der Hoff <lists@vanderhoff.org> wrote:
>> On 10/12/17 19:40, Eric S Fraga wrote:
>>> On Sunday, 10 Dec 2017 at 12:25, Tony van der Hoff wrote:
>>>
>>> [...]
>>>
>>>> In the passt, I've always worked round this by installing the lower
>>>> version on my desktop and adjusted the links. This appears no lnger to
>>>> be possible.
>>>>
>>>> Does anyone know how to get round this? (I've no immediate intention to
>>>> upgrade the server).
>>> There is the -addversionno option which allows use to use different
>>> versions of unison on the server end.  Try this out (without adjusting
>>> any links).
>>>
>> No:
> What, no? Yes (WVSVNTB).
>
>> tony@tony-lx:~$ unison -addversionno tony
>> Contacting server...
>> bash: unison-2.48: command not found
>> Fatal error: Lost connection with the server
>>
>>
> * workaroundable via symlink version number truncation bug
>
Thanks for your reply, Curt, but we appear to speak different languages ;)

WVSVNTB?

could you please reduce the brevity of your solution?

Cheers, Tony

[toc] | [prev] | [next] | [standalone]

#189819

On 2017-12-12, Tony van der Hoff <lists@vanderhoff.org> wrote:

>>> tony@tony-lx:~$ unison -addversionno tony
>>> Contacting server...
>>> bash: unison-2.48: command not found
>>> Fatal error: Lost connection with the server
>>>
>>>
>> * workaroundable via symlink version number truncation bug
>>
> Thanks for your reply, Curt, but we appear to speak different languages ;)
>
> WVSVNTB?
>
> could you please reduce the brevity of your solution?
>
> Cheers, Tony
>
>

A reduced brevity version would be to create a symbolic link unison-2.48
pointing to your installed version (unison-2.48.3?) to obviate
the dreaded WVSWVNTB.

 ln -s unison-2.48.3 unison-2.48

-- 
"The world is full of shipping clerks who have read the Harvard Classics."
— Charles Bukowski

[toc] | [prev] | [next] | [standalone]

#189822

On 12 December 2017 at 21:16, Tony van der Hoff <lists@vanderhoff.org> wrote:
> On 12/12/17 08:50, Curt wrote:
>>
>> * workaroundable via symlink version number truncation bug
>>
> Thanks for your reply, Curt, but we appear to speak different languages ;)
>
> WVSVNTB?

The mysterious "WVSVNTB" might be a reference to the first line I have
quoted above.

[toc] | [prev] | [next] | [standalone]

#189818

[Multipart message — attachments visible in raw view] — view raw

On Monday, 11 Dec 2017 at 10:36, Tony van der Hoff wrote:

[...]

> No:
>
> tony@tony-lx:~$ unison -addversionno tony
> Contacting server...
> bash: unison-2.48: command not found

But you do need to install the various versions you may to use on the
server.  Then the client can request to use the version that it has by
using that option.

So install unison-2.48?

-- 
Eric S Fraga via Emacs 27.0.50, org 9.1.3

[toc] | [prev] | [next] | [standalone]

#189847

On 12/12/17 11:58, Eric S Fraga wrote:
> On Monday, 11 Dec 2017 at 10:36, Tony van der Hoff wrote:
>
> [...]
>
>> No:
>>
>> tony@tony-lx:~$ unison -addversionno tony
>> Contacting server...
>> bash: unison-2.48: command not found
> But you do need to install the various versions you may to use on the
> server.  Then the client can request to use the version that it has by
> using that option.
>
> So install unison-2.48?
>
The server is running Jessie, the repository does not contain 2.48.
There appears to be no backport.
The client is running Stretch. Its repository does not contain anything
other than 2.48.

>From what I can see froom googling, there is an incompatibility in one
of the underlying libraries (ocaml?), which prevents Unison 2.48 being
built for Jessie, or Unison 2.40 being built for Stretch.

There doesn't appear to be an alternative for both jessie and stretch.
What a mess!

[toc] | [prev] | [next] | [standalone]

#189850

[Multipart message — attachments visible in raw view] — view raw

On Wednesday, 13 Dec 2017 at 12:49, Tony van der Hoff wrote:

[...]

> The server is running Jessie, the repository does not contain 2.48.
> There appears to be no backport.
> The client is running Stretch. Its repository does not contain anything
> other than 2.48.
>
>>From what I can see froom googling, there is an incompatibility in one
> of the underlying libraries (ocaml?), which prevents Unison 2.48 being
> built for Jessie, or Unison 2.40 being built for Stretch.
>
> There doesn't appear to be an alternative for both jessie and stretch.
> What a mess!

Can you install from testing (buster) on these systems?  I.e. download
the .deb file from the net and install using dpkg directly.  There is
only a dependency on libc6 (>= 2.17); maybe that's satisfied on those
systems?  Maybe not, of course...

The ocaml aspect hit me recently in that unison v2.48.3 and v2.48.4 are
incompatible with each other.  A real mess.  Finally managed to get all
my systems running v2.48.4...

unison is a fantastic tool but these incompatibilities make it
incredibly frustrating to use every now and again.

You could consider the following options:

1. build unison yourself on each system from source.
2. try other tools such as syncthing.

Hope you get this sorted!

-- 
Eric S Fraga via Emacs 27.0.50, org 9.1.4

[toc] | [prev] | [next] | [standalone]

#189851

On 13/12/17 13:35, Eric S Fraga wrote:
> On Wednesday, 13 Dec 2017 at 12:49, Tony van der Hoff wrote:
>
> [...]
>
> unison is a fantastic tool but these incompatibilities make it
> incredibly frustrating to use every now and again.
>
> You could consider the following options:
>
> 1. build unison yourself on each system from source.
> 2. try other tools such as syncthing.
>
> Hope you get this sorted!
>
It seems the unison developers are a little careless with compatibility
issues. This situation has arisen previously, then overcome by unison-all.

Thanks for your suggestion of syncthing; I'll give that a go...

Cheers, Tony

[toc] | [prev] | [next] | [standalone]

#189853

On 2017-12-13, Tony van der Hoff <lists@vanderhoff.org> wrote:
>>
> It seems the unison developers are a little careless with compatibility
> issues. This situation has arisen previously, then overcome by unison-all.
>
> Thanks for your suggestion of syncthing; I'll give that a go...

Sorry for butting in once again, but you do have unison-all installed,
the metapackage which allows specifically for the -addversionno "kludge" by
bringing in versions 2.32 and 2.40 as per the following post curiously
similar to your case (two machines, one with Debian Jessie and one with
Debian Stretch)

https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system

and then working around the eventual minor version number truncation
bug, if indeed it still exists, as per my previous cryptic message.

> Cheers, Tony
>
>


-- 
"The world is full of shipping clerks who have read the Harvard Classics."
— Charles Bukowski

[toc] | [prev] | [next] | [standalone]

#189856

On 13/12/17 15:40, Curt wrote:
> On 2017-12-13, Tony van der Hoff <lists@vanderhoff.org> wrote:
>> It seems the unison developers are a little careless with compatibility
>> issues. This situation has arisen previously, then overcome by unison-all.
>>
>> Thanks for your suggestion of syncthing; I'll give that a go...
> Sorry for butting in once again, but you do have unison-all installed,
> the metapackage which allows specifically for the -addversionno "kludge" by
> bringing in versions 2.32 and 2.40 as per the following post curiously
> similar to your case (two machines, one with Debian Jessie and one with
> Debian Stretch)
>
> https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system
>
> and then working around the eventual minor version number truncation
> bug, if indeed it still exists, as per my previous cryptic message.
>
Yes, thanks Curt. I have unison-all installed, and I've seen that post,
and followed the suggestions, without success. Unison-all is simply a
meta-package, which depennds on all available unison versions. Since
stretch only has 6.40 in its repo, it can only pull that one in.

 I'm fed up with trying bodgy work-arounds, which really should not be
required. I have now spent so much time on this issue that I've become
thoroughly disenchanted with Unison (which is great when it works) that
I'm taking my custom elsewhere.

[toc] | [prev] | [next] | [standalone]

#189860

On Wed, Dec 13, 2017 at 5:44 PM, Tony van der Hoff <lists@vanderhoff.org> wrote:
> On 13/12/17 15:40, Curt wrote:
>> Sorry for butting in once again, but you do have unison-all installed,
>> the metapackage which allows specifically for the -addversionno "kludge" by
>> bringing in versions 2.32 and 2.40 as per the following post curiously
>> similar to your case (two machines, one with Debian Jessie and one with
>> Debian Stretch)
>>
>> https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system
>>
>> and then working around the eventual minor version number truncation
>> bug, if indeed it still exists, as per my previous cryptic message.
>>
>  I'm fed up with trying bodgy work-arounds, which really should not be
> required. I have now spent so much time on this issue that I've become
> thoroughly disenchanted with Unison (which is great when it works) that
> I'm taking my custom elsewhere.

Do you have a good alternative? I'm fed up with Unison since a long
time, because of such an important tool not handling different
versions, and the impracticality of writing it in yet another
experimental language requiring its own complete little world to build
and run.

[toc] | [prev] | [next] | [standalone]

#189862

On 13/12/17 17:29, Anders Andersson wrote:
> On Wed, Dec 13, 2017 at 5:44 PM, Tony van der Hoff <lists@vanderhoff.org> wrote:
>> On 13/12/17 15:40, Curt wrote:
>>> Sorry for butting in once again, but you do have unison-all installed,
>>> the metapackage which allows specifically for the -addversionno "kludge" by
>>> bringing in versions 2.32 and 2.40 as per the following post curiously
>>> similar to your case (two machines, one with Debian Jessie and one with
>>> Debian Stretch)
>>>
>>> https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system
>>>
>>> and then working around the eventual minor version number truncation
>>> bug, if indeed it still exists, as per my previous cryptic message.
>>>
>>  I'm fed up with trying bodgy work-arounds, which really should not be
>> required. I have now spent so much time on this issue that I've become
>> thoroughly disenchanted with Unison (which is great when it works) that
>> I'm taking my custom elsewhere.
> Do you have a good alternative? I'm fed up with Unison since a long
> time, because of such an important tool not handling different
> versions, and the impracticality of writing it in yet another
> experimental language requiring its own complete little world to build
> and run.
>
As mentioned upthread, "Syncthing" [https://docs.syncthing.net] seems to
do much the same as Unison, hopefully more sensibly. I'm going to give
it a try over the next few days, and I'll report back here.

[toc] | [prev] | [next] | [standalone]

#190443

On 13/12/17 17:49, Tony van der Hoff wrote:
> On 13/12/17 17:29, Anders Andersson wrote:
>> On Wed, Dec 13, 2017 at 5:44 PM, Tony van der Hoff <lists@vanderhoff.org> wrote:
>>> On 13/12/17 15:40, Curt wrote:
>>>> Sorry for butting in once again, but you do have unison-all installed,
>>>> the metapackage which allows specifically for the -addversionno "kludge" by
>>>> bringing in versions 2.32 and 2.40 as per the following post curiously
>>>> similar to your case (two machines, one with Debian Jessie and one with
>>>> Debian Stretch)
>>>>
>>>> https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system
>>>>
>>>> and then working around the eventual minor version number truncation
>>>> bug, if indeed it still exists, as per my previous cryptic message.
>>>>
>>>  I'm fed up with trying bodgy work-arounds, which really should not be
>>> required. I have now spent so much time on this issue that I've become
>>> thoroughly disenchanted with Unison (which is great when it works) that
>>> I'm taking my custom elsewhere.
>> Do you have a good alternative? I'm fed up with Unison since a long
>> time, because of such an important tool not handling different
>> versions, and the impracticality of writing it in yet another
>> experimental language requiring its own complete little world to build
>> and run.
>>
> As mentioned upthread, "Syncthing" [https://docs.syncthing.net] seems to
> do much the same as Unison, hopefully more sensibly. I'm going to give
> it a try over the next few days, and I'll report back here.
>
Well, "the next few days" turned out to be a drawn-out frustrating
struggle, with no benefit.

Syncthing appears to be an extremely powerful file synchronization tool,
with an emphasis on security, which in theory would make it an excellent
replacement for unison. However, after many days struggling wit its
configuration through two firewalls and a NAT router, trying to
synchronize 3 systems, with more to add, I've given up. The machines
appear to connect, and some meta-data is transferred, but no data
transfers take place.

I've decided to give up on Syncthing, and revert to Unison, which means
upgrading my server, but hey, what are holidays for?

Cheers, Tony

[toc] | [prev] | [next] | [standalone]

#190450

[Multipart message — attachments visible in raw view] — view raw

On Friday, 29 Dec 2017 at 11:27, Tony van der Hoff wrote:

[...]

> Syncthing appears to be an extremely powerful file synchronization tool,

[...]

> I've decided to give up on Syncthing, and revert to Unison, which means
> upgrading my server, but hey, what are holidays for?

Thanks for the update.  Your experience may be what I ran into when I
tried syncthing a long time ago; I cannot remember why I gave up on it
but it may have had to do with a complex network setup at home...

Let's hope that unison doesn't get out of sync (no pun intended) for you
too soon again!

-- 
Eric S Fraga via Emacs 27.0.50, org 9.1.5

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web