While this PR is simple it took me a whole night to understand how termux build system works. RTFM

What's the benefit of building Luarocks against Lua5.4 anyway?
It's probably worth doing just on its own merit but is there any larger impetus for doing so?

LuaJIT does seem to be supported as a Lua 5.1 implementation, so would that be another option here or is there something I'm missing?
https://github.com/luarocks/luarocks/blob/v3.12.2/configure#L352-L354

Benefits? No, I didn't take that into consideration. Just bump to a newer version, and that's all.
Official installation guide uses latest lua release btw

Yeah that's fine, just wanted to know if there was some other motivation for it.

I've rebased this PR against the latest state of the master branch and reworded the commit messages to follow our standard format.
^{https://github.com/termux/termux-packages/blob/master/CONTRIBUTING.md#commit-guidelines}
Don't worry if you missed this section earlier.

The CI seems to have hit a fluke failure state on the master branch,
https://github.com/termux/termux-packages/actions/runs/18581004881
I'm rerunning a build for luarocks manually.
https://github.com/termux/termux-packages/actions/runs/18581061027

The CI seems to have hit a fluke failure state on the master branch, https://github.com/termux/termux-packages/actions/runs/18581004881 I'm rerunning a build for luarocks manually. https://github.com/termux/termux-packages/actions/runs/18581061027

Unfortunately, the update seems to still not have reached the server:

https://packages.termux.dev/apt/termux-main/pool/main/l/luarocks/

Reminder to self, do not merge stuff immediately before going to bed.

I've rebased this PR against the latest state of the master branch and reworded the commit messages to follow our standard format. https://github.com/termux/termux-packages/blob/master/CONTRIBUTING.md#commit-guidelines Don't worry if you missed this section earlier.

I even didn't take a look at it, sry

Network issue? E: Failed to fetch xxx

https://github.com/termux/termux-packages/actions/runs/18581061027
This one fails because docker image hadn't finish building yet...

Yeah, this fails because it was using docker image
sha256:5758c2453391660af537ad23906d4ccb28782f49969c7d36568f5b09cc71abe8, not this one with lua5.4 sha256:538bf45b77dda89b2c64e9482c80ebbfd15bd80d64c54c040a06a50372c8a299
Try again, please

Okay so we just hit an edge case due to the image rebuild.
Probably something we can look into later.

Yeah, this fails because it was using docker image sha256:5758c2453391660af537ad23906d4ccb28782f49969c7d36568f5b09cc71abe8, not this one with lua5.4 sha256:538bf45b77dda89b2c64e9482c80ebbfd15bd80d64c54c040a06a50372c8a299 Try again, please

In this situation, I think you should be able to solve this by opening another PR to revision-bump luarocks again, with the name revbump(main/luarocks): 3.12.2-3 and this content:

--- a/packages/luarocks/build.sh
+++ b/packages/luarocks/build.sh
@@ -3,7 +3,7 @@ TERMUX_PKG_DESCRIPTION="Deployment and management system for Lua modules"
 TERMUX_PKG_LICENSE="MIT"
 TERMUX_PKG_MAINTAINER="@termux"
 TERMUX_PKG_VERSION="3.12.2"
-TERMUX_PKG_REVISION=2
+TERMUX_PKG_REVISION=3
 TERMUX_PKG_SRCURL=https://luarocks.org/releases/luarocks-${TERMUX_PKG_VERSION}.tar.gz
 TERMUX_PKG_SHA256=b0e0c85205841ddd7be485f53d6125766d18a81d226588d2366931e9a1484492
 TERMUX_PKG_AUTO_UPDATE=true

you can do it if you want or if you prefer, I can open it

But why? Already bumped and no more changes, we just need a rebuild, using the new docker image

But why? Already bumped and no more changes, we just need a rebuild, using the new docker image

sometimes in termux-packages, if a package fails to build in CI like this after the merge to master branch, it unfortunately becomes difficult or impossible to successfully "rebuild" it at all in a way that is capable of deploying the update into the apt repository without actually creating another PR:

however, if you and Tomjo2000 would like to use this case to investigate whether that is possible, then you can.

Isn't triggering workflow_dispatch enough?

I think any one of "Members" can try re-running this job (Github allows you to do so)

Or trigger a new job like this, this should be enough

But why? Already bumped and no more changes, we just need a rebuild, using the new docker image

licy183 ended up doing the thing I said instead, in this:

• luarocks: revbump to rebuild #27084

There has been a report that unfortunately, this PR caused the 3rd party software "rocks-git.nvim" to begin failing with this error:

ERROR | 2025-11-07 15:30:24.171 | ....local/share/nvim/rocks/rocks_rtp/lua/rocks/luarocks.lua:66 | ln: failed to create hard link '/data/data/com.termux/files/home/.local/share/nvim/rocks/lockfile.lfs' => '/data/data/com.termux/files/home/.local/share/nvim/rocks/.lock.tmp.71836202': Permission denied

I don't personally know how to fix that, but it appears that maybe, the change has caused some component or dependency of the 3rd party software to fail to detect the system luarocks, and maybe resulted in it autodownloading and attempting to use an unpatched vanilla luarocks that lacks this important patch:

• luarocks: use symlink #19696
• [Bug]: luarocks cannot install rocks modules #19668

I don't personally know how to completely adapt this other distro's luarocks package logic to Termux, but I noticed that Arch Linux appears to contain a luarocks package that is somehow configured to connect to all four different versions of Lua at the same time, rather than being restricted to a single version of Lua:

https://gitlab.archlinux.org/archlinux/packaging/packages/luarocks/-/blob/e9e8810bdd76a9d75f9e3a21528a78fb35f3c5e0/PKGBUILD#L54-L57

However, according to the issues page of the Arch Linux package, it seems like that approach might also not be completely without problems:

https://gitlab.archlinux.org/archlinux/packaging/packages/luarocks/-/issues/4

@Ra2-IFV do you happen to know how to fix that?