You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NVIM v0.9.4
Build type: Release
LuaJIT 2.1.1696795921
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.9.4/share/nvim"
Run :checkhealth for more info
After that I went into the Neovim again, now I am able to install the luarocks package as normal. Not sure if there a compatibility problem with the Luajit and what not. But this is what I've found and circumvent so far.
The text was updated successfully, but these errors were encountered:
The issue happens here because Starting from 2.1.x LuaJIT is a rolling release. So those numbers we see are not release numbers, but just incremental rolling counters. It just means LuaJIT gets updated as soon as the master branch updates. But the hererocks python file still hasn't been updated to support rolling releases.
We would need to fix this on both ends, in the hererocks.py file that luarocks uses (that is a fork since the original project by mpeterv is no longer maintained), and in packer.nvim (just for passing the argument)
nvim --version
:git --version
:Steps to reproduce
:PackerSync
Actual behaviour
Found error `Failed to install hererocks'
Expected behaviour
Able to install hererocks and the luarocks dependencies
packer files
Since the installation failed, I've dug into the
luarocks.lua
a bit and found the line which composed the `hererocks' installation command like sowhich returns the results like
$ luajit -v
isBut then after some googling certain user is using the
Neovim of 0.5
andLuajit of the 2.3.0-beta3
, so I tried changing the command like soNow the installation pass (manually)
After that I went into the Neovim again, now I am able to install the luarocks package as normal. Not sure if there a compatibility problem with the Luajit and what not. But this is what I've found and circumvent so far.
The text was updated successfully, but these errors were encountered: