-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LuaJIT.org 404 when downloading tarball #49
Comments
benwilber
referenced
this issue
in benwilber/lua-valid
Aug 17, 2024
… has broken. In the meantime, we'll just test against OpenResty's LuaJIT distribution.
Merged
rbong
added a commit
to rbong/vim-flog
that referenced
this issue
Aug 17, 2024
rbong
added a commit
to rbong/vim-flog
that referenced
this issue
Aug 17, 2024
rbong
added a commit
to rbong/vim-flog
that referenced
this issue
Aug 17, 2024
Hey Ben, what's the fix you went with to solve this? I've got this in my actions file, is there an easy fix or can you recommend an alternative action? - name: Install luajit
uses: leafo/gh-actions-lua@v10
with:
luaVersion: "luajit-2.1.0-beta3" |
I just changed my workflow to use OpenResty's LuaJIT distribution. It's the same as the standard LuaJIT, which is based on Lua 5.1, except they've back-ported a few things from Lua 5.2 as well. Just change your |
1 task
dargueta
added a commit
to dargueta/unicorn-lua
that referenced
this issue
Sep 12, 2024
wincent
added a commit
to wincent/command-t
that referenced
this issue
Sep 27, 2024
As noted here: - leafo/gh-actions-lua#49 > It appears that LuaJIT.org has stopped publishing release tarballs on > their website.[^tarballs] ie. > No Release Tarballs or Binaries > > LuaJIT uses rolling releases. There are no release tarballs available > for download. Suggested fix: - leafo/gh-actions-lua#49 (comment) > I just changed my workflow to use OpenResty's LuaJIT > distribution[^OpenResty]. It's the same as the standard LuaJIT, which > is based on Lua 5.1, except they've back-ported a few things from Lua > 5.2 as well. > > Just change your `luaVersion` to `luajit-openresty`. As the action states: - https://github.com/leafo/gh-actions-lua/tree/master > `luajit-openresty` — will allways pull master from > https://github.com/openresty/luajit2 I'd rather not do this, because I'd rather test the same version that Neovim embeds[^Neovim], but it looks like I don't have any choice right now. [^tarballs]: https://luajit.org/download.html [^OpenResty]: https://github.com/openresty/luajit2 [^Neovim]: Via `:version`: LuaJIT 2.1.1725453128 (in Neovim v0.10.1).
xiaoshihou514
added a commit
to nvimdev/guard-collection
that referenced
this issue
Oct 4, 2024
imring
added a commit
to imring/Luad
that referenced
this issue
Nov 8, 2024
oleg-jukovec
added a commit
to tarantool/luarocks
that referenced
this issue
Nov 10, 2024
This was referenced Nov 20, 2024
rolandlo
added a commit
to rolandlo/lua-vips
that referenced
this issue
Dec 20, 2024
…ssing release tarball See leafo/gh-actions-lua#49 We still test with luajit-openresty.
rolandlo
added a commit
to libvips/lua-vips
that referenced
this issue
Dec 20, 2024
…ssing release tarball See leafo/gh-actions-lua#49 We still test with luajit-openresty.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that LuaJIT.org has stopped publishing release tarballs on their website.
See: https://github.com/leafo/gh-actions-lua/blob/master/main.js#L89
In the meantime, I've just switched to testing against OpenResty's LuaJIT distribution.
The text was updated successfully, but these errors were encountered: