Arch Linux User Repository

Thanks @sudoforge!

Yes the problems resides in the fact that, after upgrading the system, python -m site shows that python searches packages in /usr/lib/python3.13 (As python was upgraded to 3.13), while paru -Ql neovim-remote shows the package is installed in /usr/lib/python3.12/site-packages/.

To anyone else encountering the error posted by @fuelen, as a workaround, rebuild the package (ideally in a clean chroot), and then re-install it.

this is the error I see

$ nvr
Traceback (most recent call last):
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 563, in from_name
    return next(cls.discover(name=name))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/nvr", line 33, in <module>
    sys.exit(load_entry_point('neovim-remote==2.5.1', 'console_scripts', 'nvr')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/bin/nvr", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
                       ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 981, in distribution
    return Distribution.from_name(distribution_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 565, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for neovim-remote

Makes sense. Indeed, I have removed my yay's cached build and everything works again. Thank you for the help!

I hear that Shougo is maintaining a fork, but other than a new fix, it hasn't seen much more activity than the original repo.

@yashlala, as an AUR package, the consumers (i.e. you) are the ones who build it.

To help users, the maintainer could bump the pkgrel here so that the clients they use (i.e. makepkg, or wrappers like aurutils or yay) will rebuild the "new version".

I should also note here that the upstream project hasn't seen a new commit in a little over two years.

Still broken as per @sudoforge's comment. Looks like rebuilding does make everything work again -- any chance of that happening soon?

Please let me know if I'm misunderstanding the issue.

Broken with Python 3.10, which is in community as of today.

WORKAROUND: Rebuild the neovim-remote package.

@m040601: Done, thanks for the comment.

Please add missing files README and bash completion.

The source repository,

.
├── contrib
│   └── completion.bash
├── images
│   ├── demo1.gif
│   └── demo2.gif
├── INSTALLATION.md
├── LICENSE
├── Makefile
├── MANIFEST.in
├── nvr
│   ├── __init__.py
│   └── nvr.py
├── README.md
├── setup.py
└── tests
    └── test_nvr.py

Contains a file "completion.bash" It should end up in something like, "/usr/share/bash-completion/completions/neovim-remote"

Or if you prefer not to enable it by default in, shipt it to "/usr/share/doc/neovim-remote/" ( or even "/usr/share/neovim-remote/")

It also contains a README. It is more than what is provided with "--help".

It describes some use cases, can contain important warnings, and helps to better understand the mechanism how neovim-remote works, which can be tricky some times.

It should end up in "/usr/share/doc/neovim-remote/README"

Thanks in advance.

There is more info about this change, but I still do not know what should be installed in case of AUR: https://github.com/mhinz/neovim-remote/commit/684ad2323bed82a71253f4c1ac9c8300e62e7cff