hi Oswald,
Installing isync version 1.2.0-1 (from Debian experimental) fixes the
problem, now everything works fine.
And for some reason it is _much_ faster than 1.1.*.
Thanks for your help!
Best,
Tamas
On Wed, Apr 29 2015, Oswald Buddenhagen wrote:
> On Wed, Apr 29, 2015 at 02:39:11PM +020
On Wed, Apr 29, 2015 at 02:39:11PM +0200, Tamas Papp wrote:
> Thanks for the suggestion. I did run
>
> valgrind --tool=memcheck --log-file=/tmp/mbsync /usr/bin/mbsync -a
>
> and got quite a few 'Use of uninitialised value of size 8' and even more
> 'Conditional jump or move depends on uninitialis
hi Oswald,
Thanks for the suggestion. I did run
valgrind --tool=memcheck --log-file=/tmp/mbsync /usr/bin/mbsync -a
and got quite a few 'Use of uninitialised value of size 8' and even more
'Conditional jump or move depends on uninitialised value(s)' messages.
1. is this the right command line, o
On Tue, Apr 28, 2015 at 03:45:15PM +0200, Tamas Papp wrote:
> I using Debian. I recently upgraded isync from 1.1.1-1 to 1.1.2-1. Since
> then I noticed that mbsync exits with a non-zero exit code even when
> there were no errors (checked with -DV).
>
> Is this intentional?
>
no.
first thing would
Hi,
I using Debian. I recently upgraded isync from 1.1.1-1 to 1.1.2-1. Since
then I noticed that mbsync exits with a non-zero exit code even when
there were no errors (checked with -DV).
Is this intentional?
Best,
Tamas
--
