Bug#765010: Please include latest version of usbmuxd in JEssie

2014-11-08 Thread Shérab
let the versions for the other platforms gointo Jessie. Thanks a lot, Shérab. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#751218: [ipheth-utils] Segmentation fault on using iPhone hotspot

2014-09-22 Thread Shérab
Hi, I think this bug is fixed by the recently provided package for usbmuxd. Shérab. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#745844: [Pkg-gtkpod-devel] Bug#745844: libimobiledevice: Re: libimobiledevice-utils: Segfault with iphone 3GS on many utilities

2014-09-16 Thread Shérab
Hi, I just uploaded a usbmuxd snapshot, seeing that upstream hasn't done anything to usbmuxd for a couple of months. I understand a release is coming soon. That upload fixes the bug for me, thanks!!! Shérab. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org

Bug#745844: libimobiledevice: Re: libimobiledevice-utils: Segfault with iphone 3GS on many utilities

2014-09-15 Thread Shérab
to package it and that it is this release which is supposed tosolve the problem? Thanks! Shérab. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#671925: [Pkg-haskell-maintainers] Bug#671925: cabal update fails due to stack space overflow. Stack size can't be increased.

2012-05-08 Thread Shérab
Dear Joachim, thanks a lot for your prompt response. thanks for the report, unfortunately, I cannot reproduce it here. Does it happen to you with an empty .cabal as well? Yes. Cabal creates a default configuration file and says it's downloadling the list of packages and then after some time

Bug#671925: [Pkg-haskell-maintainers] Bug#671925: cabal update fails due to stack space overflow. Stack size can't be increased.

2012-05-08 Thread Shérab
Hi gain, hmm, I cannot reproduce it here. Unless you have any idea what might be causing this (strange network configuration, transparent proxies etc), we’ll have to wait for more reports and look for a pattern. The problem indeed seems somhow network related: I tried from another network and