On 2024-08-16 16:50, Oswald Buddenhagen via isync-devel wrote:
> On Fri, Aug 16, 2024 at 10:46:22AM +0200, Jan Eden via isync-devel wrote:
> > Although I found a practical solution (i.e. a working order), I would
> > be
> > grateful if someone could explain what is going on here.
> >
> a bug, rat
On Fri, Aug 16, 2024 at 10:46:22AM +0200, Jan Eden via isync-devel wrote:
Although I found a practical solution (i.e. a working order), I would
be
grateful if someone could explain what is going on here.
a bug, rather obviously.
is the problem reproducible with `mbsync -ls`?
if not, with `mbsy
Hi,
I just updated to isync 1.5.0, and now `mbsync -a` fails with a short
error message (`read: unexpected EOF`). Calling mbsync for a single
channel works fine. Verbose mode reveals that the execution for all
channels fails with the error message above when synchronizing the
second channel, so I
