Source: python-neovim
Version: 0.3.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, neo...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:neovim
Dear maintainers,
With a recent upload of neovim the autopkgtest of python-neovim fails in
testing when that autopkgtest is run with the binary packages of neovim
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
neovim from testing0.4.3-2
python-neovim from testing0.3.0-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of neovim to testing
[1]. Of course, neovim shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in neovim was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from neovim should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
neovim/0.4.3-2. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=neovim
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-neovim/3517661/log.gz
=== FAILURES
===
_ test_options
_
vim =
def test_options(vim):
> assert vim.options['listchars'] == 'tab:> ,trail:-,nbsp:+'
test/test_vim.py:84:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/neovim/api/common.py:88: in __getitem__
return self._get(key)
/usr/lib/python3/dist-packages/neovim/api/nvim.py:180: in request
res = self._session.request(name, *args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self =
method = 'nvim_get_option', args = ('listchars',), kwargs = {}, async_ =
False
v = [[1, b"Invalid option name: 'listchars'"], None]
err = [1, b"Invalid option name: 'listchars'"], rv = None
def request(self, method, *args, **kwargs):
"""Send a msgpack-rpc request and block until as response is
received.
If the event loop is running, this method must have been called by a
request or notification handler running on a greenlet. In that case,
send the quest and yield to the parent greenlet until a response is
available.
When the event loop is not running, it will perform a blocking
request
like this:
- Send the request
- Run the loop until the response is available
- Put requests/notifications received while waiting into a queue
If the `async_` flag is present and True, a asynchronous
notification
is sent instead. This will never block, and the return value or
error
is ignored.
"""
async_ = check_async(kwargs.pop('async_', None), kwargs, False)
if async_:
self._async_session.notify(method, args)
return
if kwargs:
raise ValueError("request got unsupported keyword
argument(s): {}"
.format(', '.join(kwargs.keys(
if self._is_running:
v = self._yielding_request(method, args)
else:
v = self._blocking_request(method, args)
if not v:
# EOF
raise IOError('EOF')
err, rv = v
if err:
info("'Received error: %s", err)
> raise self.error_wrapper(err)
E neovim.api.nvim.NvimError: b"Invalid option name: 'listchars'"
signature.asc
Description: OpenPGP digital signature
