Hisham Muhammad
Hisham Muhammad
Do we still need this? Looks like `exit /b` (with or without `%ERRORLEVEL%`) is a big rabbit hole, which I'm not keen on getting into: https://stackoverflow.com/questions/66248276/difference-between-exit-b-and-exit-b-errorlevel And from Lua's perspective...
Recent LuaRocks already does some dynamic lib checking and includes lib64 support: https://github.com/luarocks/luarocks/blob/master/src/luarocks/core/cfg.lua#L520-L528 so I think this PR is outdated and can be closed as the wanted functionality has already...
This should have been addressed by f4b1deab270a94778e1bd8903ff48387b0ed9fbc
This issue should be fixed with 8ee4ef81cf015adca29ac51a7d649a5ee04b3edd and 36f6fd122162c49fd1737344c1a9de7cc7bf3758
Closing this since it is a LuaSocket bug and it was fixed in the latest release.
I'm pretty certain this is a LuaJIT bug on MIPS (LoongArch specifically). https://github.com/luarocks/luarocks/issues/1553 is the same. I pushed #1572 as a possible mitigation, but I don't know if that will...
I can't reproduce this, from the error it looks like an intermittent network failure. Feel free to reopen in the problem persists.
`depends on lua >= 5.1 (5.1-1 provided by VM)` This is not an error message. I'm changing it to `depends on lua >= 5.1 (5.1-1 provided by VM: success)` to...
Closing since we haven't heard of others going through the same.
I don't know what happened to [0810eb8](https://github.com/luarocks/luarocks/commit/0810eb8ad185d496a51aaf398527bcddec0052f9) which caused it to get dropped, but this is now fixed by https://github.com/luarocks/luarocks/pull/1569