Description of problem: I'm use verlihub DC++ P2P app. This progam let's you have a p2p server for file sharing. It's powerfull, flexible. Plugins are available. Discussion forum - http://www.verlihubforums.com Discussion DC hub - hub.verlihub-project.org:7777 Manual Wiki Pages - http://www.verlihub-project.org verlihub-0.9.8e-1.x86_64 For this app people write plug-ins and scripts on LUA language. I'm trying use ledokol.lua script. http://wiki.hundrambit.info/doku.php?id=ledokol it's the biggest multifunctional security and entertainment script with over fifty different features for Verlihub. This script can't initialize LuaSocket wile loading - verlihub write me: undefined symbol: lua_getmetatable while load I'm find simular error from google and I find resolve for this. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Setup verlihub-0.9.8e-1.x86_64 and run 2. Compile LUA-API: Lua 1.8.1 and put liblua_pi.so* to .verlihub/plugins dir 3. Start verlihub 4. Put downloaded file http://wiki.hundrambit.info/lib/exe/fetch.php?media=ledokol:ledokol.lua to .verlihub/scripts dir 5. Try load ledokol.lua by !luaload full_path_to/.verlihub/scripts/ledokol.lua 6. Get the Warning: Unable to load LuaSocket module: error loading module 'socket.core' from file '/usr/lib64/lua/5.1/socket/core.so': /usr/lib64/lua/5.1/socket/core.so: undefined symbol: lua_getmetatable and don't working LuaSocket lib in script 7. I can see LuaSocket lib stat by the command !ledostats in main chat window Result: Version LuaSocket: not installed Actual results: LuaSocket lib in script don't work Expected results: Get the work lib :) Additional info: I'm resolve this problem, BIG THX Alexey Ozeritsky user from Mandriva mailing lists http://lists.mandriva.com/bugs/2009-09/msg06138.php This my patch for the lua-socket.spec from lua-socket-2.0.2-4.fc12.src.rpm *** lua-socket.orig.spec 2009-07-27 03:03:13.000000000 +0300 --- lua-socket.spec 2010-04-14 00:22:14.135882754 +0300 *************** *** 31,37 **** %build ! make %{?_smp_mflags} CFLAGS="%{optflags} -fPIC" /usr/bin/iconv -f ISO8859-1 -t UTF8 LICENSE >LICENSE.UTF8 mv -f LICENSE.UTF8 LICENSE --- 31,38 ---- %build ! #make %{?_smp_mflags} CFLAGS="%{optflags} -shared -fPIC -llua" ! make %{?_smp_mflags} CFLAGS="%{optflags} -fPIC" LDFLAGS="-O -shared -fpic -llua" /usr/bin/iconv -f ISO8859-1 -t UTF8 LICENSE >LICENSE.UTF8 mv -f LICENSE.UTF8 LICENSE Result: Everything OK ! :)
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.