[unison-users] Fatal error: Internal error: On-disk archives are not identical.

[Ian Kelling [e-mail] [unison-users]]

Using unison 2.48.3-1 from debian. I pushed the same binary
to the remote machine. Local host is running debian testing,
remote is debian stable.

md5sum on both machines:
83781feb622cd2c8b71bf9c9e739017f /usr/bin/unison-2.48.3,

I see that is the command being run on the remote
machine when I run unison-gtk, and it waits around for me
to lookup the pid on the remote machine, then I ran
/usr/bin/unison-2.48.3 locally, so I know for sure the exact
same binary is being run on both machines.

Hostnames of the machines are definitely different.

I accidentally deleted the bad archive on the local machine,
backed up the one on the remote machine. The remote archive
was used previously on a different os and migrated to this os,
but the hostname remained the same.

[Adrian Klaver [e-mail] [unison-users]]

Post by Ian Kelling ***@iankelling.org [unison-users]
Using unison 2.48.3-1 from debian. I pushed the same binary
to the remote machine. Local host is running debian testing,
remote is debian stable.
83781feb622cd2c8b71bf9c9e739017f /usr/bin/unison-2.48.3,
I see that is the command being run on the remote
machine when I run unison-gtk, and it waits around for me
to lookup the pid on the remote machine, then I ran
/usr/bin/unison-2.48.3 locally, so I know for sure the exact
same binary is being run on both machines.
Hostnames of the machines are definitely different.
I accidentally deleted the bad archive on the local machine,
backed up the one on the remote machine. The remote archive
was used previously on a different os and migrated to this os,
but the hostname remained the same.

That OS was?

Did the machine architecture differ between where you migrated from and
where you migrated to?
--
Adrian Klaver
***@aklaver.com


------------------------------------

------------------------------------


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/unison-users/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/unison-users/join
(Yahoo! ID required)

<*> To change settings via email:
unison-users-***@yahoogroups.com
unison-users-***@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
unison-users-***@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

[Ian Kelling [e-mail] [unison-users]]

On Wed, Jul 13, 2016, at 05:13 PM, Adrian Klaver

Post by Adrian Klaver ***@aklaver.com [unison-users]

Post by Ian Kelling ***@iankelling.org [unison-users]
Using unison 2.48.3-1 from debian. I pushed the same binary
to the remote machine. Local host is running debian testing,
remote is debian stable.
83781feb622cd2c8b71bf9c9e739017f /usr/bin/unison-2.48.3,
I see that is the command being run on the remote
machine when I run unison-gtk, and it waits around for me
to lookup the pid on the remote machine, then I ran
/usr/bin/unison-2.48.3 locally, so I know for sure the exact
same binary is being run on both machines.
Hostnames of the machines are definitely different.
I accidentally deleted the bad archive on the local machine,
backed up the one on the remote machine. The remote archive
was used previously on a different os and migrated to this os,
but the hostname remained the same.

That OS was?
Did the machine architecture differ between where you migrated from and
where you migrated to?

The architecture did not change, it was the same physical machine. I
don't
know the exact os, probably debian stable or testing. It was definitely
using
some earlier version of unison, I don't know which, but within the last
year
of distro packages.

Anyways, I can't reproduce it, but I just wanted to let you know that
the further
error text claims this happens with unison compiler mismatch or 1 other
condition, but neither were the case for me. Doing the sync with no
archive,
I then ran into the other bug I reported recently about replacing
symlinks,
just thought I'd mention that in case it's related.