Bug#805456: unison: fails to recognize changes after upgrade of unison on both hosts

[Matthis Kruse <kruse.matthis@web.de>]

Package: unison
Version: 2.48.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading unison on both hosts it doesnt seem to recognize any changes.
I've created several different folders with different contents.
(to be specific: detached sign files from gpg)
However, unison tells me that nothing has changed. I've removed the unison
sync files, so that it may re-inspect it, but same answer!
Then, I've removed almost anything as a test if that might get recognized,
but same problem. I've expected that it recognizes the changes at least
after removing it's sync files in ~/.unison.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.2.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages unison depends on:
ii  libc6  2.19-22

Versions of packages unison recommends:
ii  openssh-client [ssh-client]  1:6.9p1-2+b1

Versions of packages unison suggests:
pn  unison-all  <none>

-- no debconf information