4 ms·
LuaJIT.org stopped publishing release tarballs [1] which caused leafo's GH actions builds [2] to suddenly stop working. The workaround was to start testing aga
by benwilber0 2y ago
LuaJIT.org stopped publishing release tarballs [1] which caused leafo's GH actions builds [2] to suddenly stop working. The workaround was to start testing against OpenResty's distribution of LuaJIT [3] which is incompatible with LuaJIT.org's version.
There is no faster way to make a fork the de facto standard version than to break everyone's CI builds.
[1] https://luajit.org/download.html https://luajit.org/download.html
[2] https://github.com/leafo/gh-actions-lua/issues/49 https://github.com/leafo/gh-actions-lua/issues/49
[3] https://github.com/openresty/luajit2 https://github.com/openresty/luajit2
- krapp 2y agoThe workaround for LuaJIT moving to Github was to... clone a fork of it? If they could do that, why can't they just pull from the LuaJIT repo?
- tecleandor 2y agoLuaJIT didn't move to GitHub, they just have a mirror there. The thing is they stopped numbering and publishing releases, it's all a rolling release without any name or number, so you cannot snapshot I'm certain version. But OpenResty fork does create tag versions with date, so they can build or test against certain concrete snapshot frozen in time.
- BugsJustFindMe 2y ago> it's all a rolling release without any name or number, so you cannot snapshot I'm certain version A git commit SHA is a number that identifies a version of the code.
- tecleandor 2y agoYep, but it doesn't serve as model of reference of date, order, patch or anything, and it's meaningless without the git database. It's OK as an immutable tag, but doesn't give you any additional information. Even without SemVer, using a simple date versioning system (let's say 2024.10.2-patch4) gives you a lot of context.