Bug#805456: marked as done (unison: fails to recognize changes after upgrade of unison on both hosts)
Your message dated Sun, 3 Jan 2016 16:17:27 +0100
with message-id <56893B87.6020400@dogguy.org>
and subject line Re: Bug#805456: unison: works well on my testing
has caused the Debian Bug report #805456,
regarding unison: fails to recognize changes after upgrade of unison on both hosts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
805456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805456
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unison: fails to recognize changes after upgrade of unison on both hosts
- From: Matthis Kruse <kruse.matthis@web.de>
- Date: Wed, 18 Nov 2015 12:25:40 +0100
- Message-id: <144784594018.11745.8949027563236151161.reportbug@Heideltraud.dasnacl.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
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Control: notfound 805456 unison/2.48.3-1
On 03/01/2016 14:11, Matthis Kruse wrote:
> It never happened to me again, too. I don't know what were wrong, it
> surely is unreproducible and thus probably an error by me and not by
> unison. Sorry for the inconvenience.
>
Ok, thanks for the confirmation. I'm closing the bug.
Regards,
- --
Mehdi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWiTuGAAoJEDO+GgqMLtj/1OwQAJlRrlTdFMCMkqKYLuBe71fC
PYMiFH49XWGZ8SV+5DTTXnL7WJgiUX/I8PMvSjhpDPv/rAWbdVcHmKVfEIt65PJL
IWyfNgxilL9uw3rKFqZKoRXrtlFEWBEKJaN+ypuCmxI1TZXUgQYpvBvIRYQHDv2S
2Mvbf5eH1V8YHaqJkhhP13gA3Z3UwDRBIoKPx2xVyX72v4JGADFx0qNLRW8ou94c
c5yAj0Ts7GY4hyqzSmUiYgVGx/md3oO/oIu0ypAspCfRNRonJ00h+VJ7ToNwwS7z
pcPmWM/tr6EXtDzomGr/t/tHZbKIsO/EfgxqJ7DF7NwnujwqDKBfIjaARizAv7tD
7RWk1eHH/2EYzGyUEiqaOSzuFhcpJjJeC+FSNBLSCi/jOEBjr/J04yMwagZj17Ic
bc4zVXXDa3NM1Qv5ZCgh1ykwA1ourwNmmA3knpICiwv2q3j4H//XA9s/NJ59bmlV
UTPUraXOCGxLJPEuhj1vgqknIDVXeDoUaUKizc/JGrWb2KFLlpO3qsBxCKyo9Uk2
b7DfsrqXFEN/XOJOCv1t4eGP9kIDbg3ADtMld7Szoj/6Mw9U0LyFl1GetaWasUFa
A5FcDIWOqdrS7NlagVo51jW+zTTjcuq870fP5JLLLltrkSYxJJ1/TDXat7uXHK6h
CAwaUbfLy/T7QqtjuYzV
=S0ZO
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: