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
signature.asc
Description: PGP signature
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 he
On Thu, Feb 08, 2018 at 12:28:15PM +0100, Peter P. wrote:
> 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)
>
that means that mbsync didn't properly finish syncing some box(es),
possibly alread
On 18-02-06 17:43:39, Peter P. wrote:
* Oswald Buddenhagen [2018-02-06 16:31]:
On Tue, Feb 06, 2018 at 01:18:23PM +0100, Peter P. wrote:
> since many years I wonder how to read mbsync's status line, eg
>C: 7/7 B: 41/41 M: +0/0 *0/0 #0/0 S: +1/1 *1/1 #3048/3048
> Is there an explanation i
* Oswald Buddenhagen [2018-02-08 18:44]:
> On Thu, Feb 08, 2018 at 12:28:15PM +0100, Peter P. wrote:
> > 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)
> >
> that means that mbsync didn
On Thu, Feb 08, 2018 at 07:32:17PM +0100, Peter P. wrote:
> Trying to apply what you recomment I am noticing the following
> dicrepancy between Debian's 1.2.1-2 and 1.3.0-1: [...]
>
that looks related to one NEWS item ... for 1.2.0.
i'd need to see the full config to make a call.
