On Tue, Jun 18, 2019 at 10:03:58AM +0200, Oswald Buddenhagen wrote: > On Mon, Jun 17, 2019 at 08:06:05PM +0200, Guillaume Brogi wrote: > > > so, your server is broken, and isync doesn't check the error condition. > > > how negligent of me. :} > > > > > I figured it may have been something like that. > > I guess 1.3.0 uses the old command? > > > yes. you can back out commits 0a5a847932 and f82c172d2 to get the > less broken behavior back. > I'm going to just keep 1.3.0 for now.
> > Nothing useful AFAICT (passwords and fumbling around redacted): > > > yep. i'm out of ideas now. :/ > Ok. > > > i reported the bug to them, so doing nothing might also get you > > > somewhere. :D > > They are usually quite reactive, though I think it's a small team. > > > ok, let's hope the report actually went through (i used their weird > contact form, which didn't give much of a delivery confirmation ...) Ack. If there's no news by next week I'll try contacting them _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
