Ashlen <euryd...@riseup.net> wrote: > On 23/01/06 12:53, Omar Polo wrote: > > This needs some further testing. Packages that depends on luasockets > > are > > > > - devel/luacopas no test suite > > - devel/luaevent test run OK > > - net/jitsi/prosody-plugins no test suite > > - net/prosody no test suite > > - security/luasec no test suite > > - www/luakit with simple runtesting seems fine > > > > I can manage to test it with net/prosody on -RELEASE but will take a > > while. > > I'll see if I can test against net/prosody on -RELEASE as well, actually. I'll > do my best to follow your suggestions. Thank you for taking the time to > respond.
Prosody port maintainer here. Built and installed it with op@ patch in my -current and restarted prosody. It didn't blow up and is currently connected to my usual servers. Running with LD_DEBUG shows it's actually used (is there a better way to check which dynamic libraries a running process is using? fstat doesn't provide that info :( ) dlopen: loading: /usr/local/lib/lua/5.3/socket/unix.so flags /usr/local/lib/lua/5.3/socket/unix.so = 0x0 head /usr/local/lib/lua/5.3/socket/unix.so obj /usr/local/lib/lua/5.3/socket/unix.so has /usr/local/lib/lua/5.3/socket/unix.so as head linking /usr/local/lib/lua/5.3/socket/unix.so as dlopen()ed head [/usr/local/lib/lua/5.3/socket/unix.so] examining: '/usr/local/lib/lua/5.3/socket/unix.so' tail /usr/local/lib/lua/5.3/socket/unix.so protect RELRO [0x6810b52eba0,0x6810b530000) in /usr/local/lib/lua/5.3/socket/unix.so doing ctors obj 0x680e98f65f0 @0x6810b52d0b0: [/usr/local/lib/lua/5.3/socket/unix.so] dlopen: /usr/local/lib/lua/5.3/socket/unix.so: done (success). dlsym: luaopen_socket_unix in /usr/local/lib/lua/5.3/socket/unix.so: 0x6810b52cf60 -Lucas
