On Thu, Nov 01, 2018 at 03:46:57PM +0100, Oswald Buddenhagen wrote: > On Thu, Nov 01, 2018 at 01:35:00PM +0100, Evgenii Sovetkin wrote: > > recently I started getting warning messages like this: > > > > Notice: conflicting changes in (91083,71378) > > after i got the requested info:
that's the result of a partial syncing config: Sync PullNew PullRenew PullFlags PushFlags the message on the server got deleted, while on the client the flags changed (it became "seen"), which are obviously incompatible modifications (it's impossible to propagate a flag change to a deleted message). usually, the deletion would be pulled and thus resolve the conflict by overriding the flag change, but that's suppressed by the configuration. arguably, because the situation is unresolvable anyway, mbsync should simply update the known message flags, so it would not complain each time anew. until i fix that minor bug/missing feature, you can work around it by hacking the state file - just add the "S" flag to the entry in question. another workaround is simply deleting message *,U=71378:2,S on the client. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
