On 2018-02-08 11:06, Aaron W. Swenson wrote: > On 2018-02-08 12:28, Peter P. wrote: > > Hi list, > > > > upgrading from to on a Debian testing box I do get the following for one > > of my channels: > > > > Error: incompatible journal version (got 2, expected 3) > > > > The mailing list archive doesn't seem to know about it so far. > > > > thanks! > > P > > Same here on Gentoo. I was going to write about it, but kept forgetting > to do so. > > Upgraded from 1.2.1 to 1.3.0. Is there some upgrade step we need to do?
I know this isn’t going to be much help, but I fixed this problem by
finally figuring out which account it was complaining about, and
removing all .mbsyncstate files under the Inbox subdirectory.
It was a bit difficult figuring out which account and subdirectory were
the issue, but I finally noticed my work email hadn’t been updating on
my home machine.
Here’s the important bits from ‘mbsync -a -V -Dsm’:
Channel work
Opening master store work-remote...
Resolving imap.secureserver.net... ok
Connecting to imap.example.net (ip.ad.dr.ess:993)...
Opening slave store work-local...
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
reading sync state /home/titan/.maildir/work/Inbox/.mbsyncstate ...
entry (18073,8946,8,)
…snip a few thousand lines…
recovering journal ...
Error: incompatible journal version (got 2, expected 3)
mbsync then merrily continued taking care of the rest of folders before
going on to the next account.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
