push to luarocks about lgi HOT 14 CLOSED

@airtonix, we are still in the same boat as last month:

just use
sudo luarocks install --server=https://luarocks.org/dev lgi

There is no development/scm rockspec uploaded to the lgi module on luarocks.org, so this command will make no difference

Basically, you (@airtonix ) are installing the release version of LGI, but using Lua 5.4 (your log says lgi 0.9.2-1 depends on lua >= 5.1 (5.4-1 provided by VM)) which is only supported by git-master.

Deploying a new versioned release aside, I think a good first step would be to create a dev rockspec that knows how to build from the repository's source.

This is now possible thanks to @leafo work with #305. You can currently install the LGI git version with the command:

luarocks install https://raw.githubusercontent.com/lgi-devs/lgi/master/lgi-scm-1.rockspec

from lgi.

just use

sudo luarocks install --server=https://luarocks.org/dev lgi

There is no development/scm rockspec uploaded to the lgi module on luarocks.org, so this command will make no difference

I would also like to see a new version deployed to LuaRocks.

Deploying a new versioned release aside, I think a good first step would be to create a dev rockspec that knows how to build from the repository's source.

Note: I am admin on luarocks.org so I can help get this release sorted out if the original owner is no longer responsive, we can move the lgi name on the root manifest to another account

from lgi.

This is fine with me 👍.

(But a new release including the commits which make lgi fit for lua5.4, which in fact are already present would still be a good idea, I think. But that's not in my hands)

from lgi.

Why me? @Nuc1eoN Why don't you do it? If I were go guess, I would claim that you are still writing Lua code and use LGI. I do not.

from lgi.

just use

sudo luarocks install --server=https://luarocks.org/dev lgi

from lgi.

Yes already tried this, the Problem is that this way V 0.9.2-1 will be installed which is from 2017 and has no lua5.4 support.
(What works is using the provided rocspec removing the tag from the source -> just use the current master, but that's not really convenient)
But I see maybe the bigger Problem is that there is no more recent version than 0.9.2-1 despite the fact it is 5 years old and there actually was some (important, if I think of lua5.4 support) development in that period of time.

from lgi.

Yes already tried this, the Problem is that this way V 0.9.2-1 will be installed which is from 2017 and has no lua5.4 support. (What works is using the provided rocspec removing the tag from the source -> just use the current master, but that's not really convenient) But I see maybe the bigger Problem is that there is no more recent version than 0.9.2-1 despite the fact it is 5 years old and there actually was some (important, if I think of lua5.4 support) development in that period of time.

That is a big issue. Damn, maybe the dep should be updated for Lua5.4?

from lgi.

That is a big issue

Yes, I agree.

I see two things

1. Change (and push the change to luarocks) the deps so that one can only install this for lua versions < lua5.4.
2. Make a new release + rockspec (and push this to luarocks)

from lgi.

> sudo luarocks install --server=https://luarocks.org/dev lgi
[sudo] password for XYZ:
Installing https://luarocks.org/lgi-0.9.2-1.src.rock

lgi 0.9.2-1 depends on lua >= 5.1 (5.4-1 provided by VM)
make -C lgi
make[1]: Entering directory '/tmp/luarocks_lgi-0.9.2-1-AFaZD8/lgi/lgi'
pkg-config --exists 'gobject-introspection-1.0 >= 0.10.8' --print-errors
touch .depcheck
gcc -fPIC  -O2 -fPIC -I/usr/include -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread  -Wall -Wextra -O2 -g -c -o buffer.o buffer.c
gcc -fPIC  -O2 -fPIC -I/usr/include -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread  -Wall -Wextra -O2 -g -c -o callable.o callable.c
callable.c: In function ‘closure_callback’:
callable.c:1237:13: error: too few arguments to function ‘lua_resume’
 1237 |       res = lua_resume (L, NULL, npos);
      |             ^~~~~~~~~~
In file included from lgi.h:11,
                 from callable.c:12:
/usr/include/lua.h:300:15: note: declared here
  300 | LUA_API int  (lua_resume)     (lua_State *L, lua_State *from, int narg,
      |               ^~~~~~~~~~
make[1]: *** [Makefile:63: callable.o] Error 1
make[1]: Leaving directory '/tmp/luarocks_lgi-0.9.2-1-AFaZD8/lgi/lgi'
make: *** [Makefile:16: all] Error 2

Error: Build error: Failed building.

from lgi.

yep having this on luarocks would be great. imagine all the "OMG BBQ IT DOESNT INSTALL!!!1111pony" tickets you're about to get that you won't have to get. :>

from lgi.

@psychon Would you mind pushing a new release to LuaRocks with Lua 5.4 support (or upload the 'dev' manifest)?

from lgi.

Why me? @Nuc1eoN Why don't you do it? If I were go guess, I would claim that you are still writing Lua code and use LGI. I do not.

Excuse me, I was under the impression that you are maintaining the LGI repository.

Note: I am admin on luarocks.org so I can help get this release sorted out if the original owner is no longer responsive, we can move the lgi name on the root manifest to another account

@leafo Are you still an admin of luarocks.org? Could you still reassign the ownership of that package (https://luarocks.org/modules/pavouk/lgi), so that we can release an official 'dev' version (as you've suggested in #305)?
Thank you.

from lgi.

TL;DR: I can try to help with LGI, but don't expect "anything big" from me.

Excuse me, I was under the impression that you are maintaining the LGI repository.

Heh, in a way I am. But I am not really doing anything. LGI was originally created by @pavouk . At one point in time, I created my own cairo and pango bindings for AwesomeWM and (IIRC) the debian maintainer of AwesomeWM asked me why I am reinventing the wheel instead of just using LGI. That's how I ended up with LGI. In the past, I did some work on this project and I think I am known to (try to) react to bug reports here. But my only "special power" is that I can merge PRs here. I never ever uploaded anything to LuaRocks. And I haven't actually done any "real work" in Lua or for LGI in ages.

Also: Sorry if my answer above was a bit harsh.

from lgi.

Why me? @Nuc1eoN Why don't you do it? If I were go guess, I would claim that you are still writing Lua code and use LGI. I do not.

Excuse me, I was under the impression that you are maintaining the LGI repository.

Note: I am admin on luarocks.org so I can help get this release sorted out if the original owner is no longer responsive, we can move the lgi name on the root manifest to another account

@leafo Are you still an admin of luarocks.org? Could you still reassign the ownership of that package (https://luarocks.org/modules/pavouk/lgi), so that we can release an official 'dev' version (as you've suggested in #305)? Thank you.

@hishamhm

from lgi.