[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [ANN] LuaRocks 3.0.0beta1 for Unix
- From: Matthew Wild <mwild1@...>
- Date: Thu, 5 Jul 2018 14:00:41 +0100
On 4 July 2018 at 23:36, Hisham <email@example.com> wrote:
> Hello list,
> I am extremely happy to announce LuaRocks 3.0.0beta1, the
> almost-finished package for the new major release of LuaRocks, the Lua
> package manager.
Build and installation was great! The configure script magically found
my 5.4 installation and just worked.
Then I successfully installed luasocket, though it seemed to install
to the current dir (which happened to be the luarocks source dir I
built from). On reading the changelog, I guess this is expected
However now everything seems to fail (regardless of where I run
luarocks from), all commands fail with:
$ sudo luarocks-5.4 list
/usr/local/share/lua/5.4/luarocks/core/path.lua:17: assertion failed!
[C]: in function 'assert'
/usr/local/share/lua/5.4/luarocks/core/path.lua:17: in function
/usr/local/share/lua/5.4/luarocks/path.lua:216: in function
/usr/local/share/lua/5.4/luarocks/cmd.lua:215: in upvalue
/usr/local/share/lua/5.4/luarocks/cmd.lua:394: in function
/usr/local/bin/luarocks-5.4:35: in main chunk
[C]: in ?
It looks like path.rocks_dir() is passed nil, and cfg.root_dir is nil
also. Is this expected behaviour? Did I do something wrong?