[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#358082: marked as done (unison causes system to hang)



Your message dated Wed, 17 Feb 2010 00:41:26 +0100
with message-id <20100216234125.GL32325@yocto.gallu.homelinux.org>
and subject line Doesn't exist in 2.27.57
has caused the Debian Bug report #358082,
regarding unison causes system to hang
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.)


-- 
358082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358082
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: unison
Version: 2.13.16-5
Severity: critical
Justification: breaks the whole system

I have two systems using unison. Both linux systems have started
hanging since installing unison 2.13.16-5. Unison 
2.9.x wasn't causing problems.

System A.
debian kernel 2.6.12, reiserfs, MD_RAID5

System B.
debian kernel 2.6.12, reiserfs, MD_RAID1

.prf on system A (executed on system A causes system A to crash)
root = /home/brendon/data/cal (system A)
root = ssh://cal@sol.cal.com/webdav (system B)

.prf on laptop (executed on laptop causing system B to crash)
root = ssh://cal@sol.cal.com//home/cal/webdav (system B)
root = /cygdrive/x/cal (laptop)

I can't have systems crashing, so i'm going to have to revert back to
unison 2.9.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (400, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.12-evms
Locale: LANG=C, LC_CTYPE=C

Versions of packages unison depends on:
ii  libc6                         2.3.5-8    GNU C Library: Shared libraries an

-- no debconf information


--- End Message ---
--- Begin Message ---
Hello,

As reported in the bug, this issue disappeared with unison 2.17, we are
now at version 2.27.

Regards
Sylvain




--- End Message ---

Reply to: