void-linux / void-linux/void-packages

shlibs checking fail on neovim update

Open
#14,856 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug enhancement xbps-src
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Something is wrong with shlibs checking on #14511, but i am not exactly sure what.

Story:

libvterm-0.0.20151229 provides libvterm.so.0, a symlink to libvterm.so.0.0.0
libvterm-0.1.1 provides libvterm.so.0, a symlink to libvterm.so.0.1.1
both provide libvterm.so, a symlink to real libvterm.so.0.?.?
libvterm.so.0.1.1 provides symbols not provided by libvterm.so.0.0.0

neovim-0.4.2 is linked against libvterm.so.0 provided by newer libvterm

xbps-src reads from shlibs that libvterm.so.0 is provided by libvterm>=0.0.20151229
xbps-src generates neovim package with run dep libvterm>=0.0.20151229

xbps don't update libvterm on update of neovim

neovim fails to start because of missing symbols in libvterm.so.0

Question: what is wrong:

  • libvterm providing incompatible versions of libvterm.so.0, even if not telling to use them?
  • toolchain linking against libvterm.so.0 symlink, not explicitly instructed to do so?
  • xbps-src specifying symlink in shlibs?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #14511 and the xbps-src shlibs-checking and dependency-generation behavior described here. Compare the libvterm providers and neovim's generated runtime dependency; done means updates install a compatible libvterm and neovim no longer fails with missing symbols.

Written by the indexing model from the issue text.

Assessment

Tech stack
neovim, shell
Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.