Re: [ANN] LuaRocks 3.0.0beta1 for Unix

[Hisham <h@...>]

On 5 July 2018 at 10:00, Matthew Wild <mwild1@gmail.com> wrote:
> On 4 July 2018 at 23:36, Hisham <h@hisham.hm> 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
> behaviour.
>
> However now everything seems to fail (regardless of where I run
> luarocks from), all commands fail with:
>
> $ sudo luarocks-5.4 list
> /usr/local/bin/lua5.4:
> /usr/local/share/lua/5.4/luarocks/core/path.lua:17: assertion failed!
> stack traceback:
>     [C]: in function 'assert'
>     /usr/local/share/lua/5.4/luarocks/core/path.lua:17: in function
> 'luarocks.path.rocks_dir'
>     /usr/local/share/lua/5.4/luarocks/path.lua:216: in function
> 'luarocks.path.use_tree'
>     /usr/local/share/lua/5.4/luarocks/cmd.lua:215: in upvalue
> 'process_tree_flags'
>     /usr/local/share/lua/5.4/luarocks/cmd.lua:394: in function
> 'luarocks.cmd.run_command'
>     /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?

Definitely not!

Let's try to diagnose this:

* Did you install using `make; sudo make install` or `sudo make bootstrap`?
* Did it create a config file /usr/local/etc/luarocks/config-5.4.lua?
  If so, what are its contents?
* Also, could you paste the /usr/local/bin/luarocks launcher script?

Also, the installer failed to create the versioned `luarocks-5.4`
symlink, right? Just noticed that.

Thank you!

-- Hisham