Source: neovim
Version: 0.1.7-4
Severity: important
Tags: upstream fixed-upstream
User: msgpac...@packages.debian.org
Usertags: msgpack-c-2.x
Forwarded: https://github.com/neovim/neovim/pull/6406
While performing rebuilds of packages which Build-Depend on
libmsgpack-dev with the 2.x version in experimental, I found that neovim
FTBFS:
not ok 1468 - ShaDa support code is able to dump and read back list
variable automatically
# ...r2/neovim-0.1.7/test/functional/shada/variables_spec.lua @ 26
# Failure message:
...r2/neovim-0.1.7/test/functional/shada/variables_spec.lua:40: Expected
objects to be the same.
# Passed in:
# (table) {
# [1] = {
# [a] = 10 }
# *[2] = {
# *[b] = userdata: 0x41e2bff0 }
# [3] = {
# [c] = 'str' } }
# Expected:
# (table) {
# [1] = {
# [a] = 10 }
# *[2] = {
# *[b] = 10.5 }
# [3] = {
# [c] = 'str' } }
# stack traceback:
# ...r2/neovim-0.1.7/test/functional/shada/variables_spec.lua:40: in
function <...r2/neovim-0.1.7/test/functional/shada/variables_spec.lua:27>
#
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
