On Wed, Feb 05, 2014 at 12:44:01PM +0100, Oswald Buddenhagen wrote: > this appears to be an upstream bug in the compatibility wrapper. > > you can migrate to the "proper" mbsync by running "isync -w" and fixing > the broken .mbsyncrc by hand.
Tried: run "isync -w" from 1.1.0-1 package. Resultimg .mbsyncrc does not contain dots in file paths. However, running "mbsync -a" on it gives the same result (errors messages about broken file paths). Change paths in .mbsyncrc to absolute does not help. -- Eugene Berdnikov -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
