Bug#814096: neovim: errors reading/writing shada file

[James McCoy]

On Wed, Feb 10, 2016 at 07:27:16PM -0500, James McCoy wrote:
> On Mon, Feb 08, 2016 at 09:37:31AM -0500, D. Stuart Freeman wrote:
> > On first run neovim works as expected, but on subsequent runs starts with
> > error:
> > 
> >      E576: Failed to parse ShaDa file: incomplete msgpack string at position 81
> > 
> > and exits with error:
> > 
> >      E576: Failed to parse ShaDa file: incomplete msgpack string at position 81
> >      E136: Did not rename /home/stuart/.local/share/nvim/shada/main.shada.tmp.a because /home/stuart/.local/share/nvim/shada/main.shada does not looks like a ShaDa file
> >      E136: Do not forget to remove /home/stuart/.local/share/nvim/shada/main.shada.tmp.a or rename it manually to /home/stuart/.local/share/nvim/shada/main.shada.
> 
> Indeed, this is a known problem when building Neovim against a 1.x
> msgpack-c but running it against a pre-1.x version.  I'll be talking to
> msgpack-c's upstream about this.

FWIW, https://github.com/msgpack/msgpack-c/issues/419 is the discussion.
Depending on the outcome of that, I'll either add an explicit minimum
version to the dependency in Neovim or it will happen automatically
based on changes to msgpack's packaging.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan at debian.org>