Some lua packages are broken in f22

[Kalev Lember]

On 03/20/2015 02:31 PM, Bastien Nocera wrote:
> Seen this as well.

Coincidentally, I looked at lua earlier today to fix another package,
and there's what I found:

> quvi is broken:
> ** (info:11777): CRITICAL **: [_chk_script_ident] /usr/share/libquvi-scripts/0.9/common/quvi/youtube.lua:109: module 'socket.url' not found:
> 	no field package.preload['socket.url']
> 	no file '/usr/share/lua/5.2/socket/url.lua'
> 	no file '/usr/share/lua/5.2/socket/url/init.lua'
> 	no file '/usr/lib64/lua/5.2/socket/url.lua'
> 	no file '/usr/lib64/lua/5.2/socket/url/init.lua'
> 	no file './socket/url.lua'
> 	no file '/usr/share/libquvi-scripts/0.9/common/socket/url.lua'
> 	no file '/usr/lib64/lua/5.2/socket/url.so'
> 	no file '/usr/lib64/lua/5.2/loadall.so'
> 	no file './socket/url.so'
> 	no file '/usr/lib64/lua/5.2/socket.so'
> 	no file '/usr/lib64/lua/5.2/loadall.so'
> 	no file './socket.so'
> error: while initializing libquvi: Could not find any subtitle scripts in the path
> 
> Filed as https://bugzilla.redhat.com/show_bug.cgi?id=1204146

Lua was updated to 5.3, which included a soname bump. To avoid
rebuilding the world, apparently lua is currently carrying a parallel
installable 5.2 library in the same package. I guess the
/usr/lib64/lua/5.2/ modules got left out or something.

Anyway, I'd wager that a simple quvi rebuild would help here, since it
then gets linked with the 5.3 library which presumably has all the
/usr/lib64/lua/5.3/ modules included.

> And my "git web-show" script[1] is broken as well:
> /bin/lua: error loading module 'socket.core' from file '/usr/lib64/lua/5.3/socket/core.so':
> 	/usr/lib64/lua/5.3/socket/core.so: undefined symbol: luaL_checkint
> stack traceback:
> 	[C]: in ?
> 	[C]: in function 'require'
> 	/usr/share/lua/5.3/socket.lua:12: in main chunk
> 	[C]: in function 'require'
> 	/usr/share/lua/5.3/socket/url.lua:13: in main chunk
> 	[C]: in function 'require'
> 	/home/hadess/bin/git-web-show:12: in main chunk
> 	[C]: in ?
> 
> Filed as https://bugzilla.redhat.com/show_bug.cgi?id=1204147

https://bugzilla.redhat.com/show_bug.cgi?id=1204129 might be related,
which I fixed earlier today.

-- 
Kalev