[Luarocks-developers] Trouble upgrading to LuaRocks 2.2.0-2
Brought to you by:
loderunner
|
From: Sean C. <se...@co...> - 2015-03-17 21:10:25
|
I saw the announcement of LuaRocks 2.2.0-2. I tried updating (using "luarocks install luarocks") and the short version of it---I ended up having to nuke *just about everything* (I kept /usr/local/etc/luarocks) related to luarocks and start over [1]. I do have the latest git repo cloned, and, wanting luarocks installed in my local $HOME/.luarocks tree, made sure the configuration is configured as such. Running from ~/apps/luarocks/src: [spc]lucy:~/apps/luarocks/src>./bin/luarocks LuaRocks scm, a module deployment system for Lua NAME ./bin/luarocks - LuaRocks main command-line interface SYNOPSIS ./bin/luarocks [--from=<server> | --only-from=<server>] [--to=<tree>] [VAR=VALUE]... <command> [<argument>] GENERAL OPTIONS These apply to all commands, as appropriate: --server=<server> Fetch rocks/rockspecs from this server (takes priority over config file) --only-server=<server> Fetch rocks/rockspecs from this server only (overrides any entries in the config file) --only-sources=<url> Restrict downloads to paths matching the given URL. --tree=<tree> Which tree to operate on. --local Use the tree in the user's home directory. To enable it, see './bin/luarocks help path'. --verbose Display verbose output of commands executed. --timeout=<seconds> Timeout on network operations, in seconds. 0 means no timeout (wait forever). Default is 30. VARIABLES Variables from the "variables" table of the configuration file can be overriden with VAR=VALUE assignments. COMMANDS build Build/compile a rock. doc Shows documentation for an installed rock. download Download a specific rock file from a rocks server. help Help on commands. Type './bin/luarocks help <command>' for more. install Install a rock. lint Check syntax of a rockspec. list Lists currently installed rocks. make Compile package in current directory using a rockspec. new_version Auto-write a rockspec for a new version of a rock. pack Create a rock, packing sources or binaries. path Return the currently configured package path. purge Remove all installed rocks from a tree. remove Uninstall a rock. search Query the LuaRocks servers. show Shows information about an installed rock. unpack Unpack the contents of a rock. upload Upload a rockspec to the public rocks repository. write_rockspec Write a template for a rockspec file. CONFIGURATION Lua version: 5.1 Configuration files: System: /usr/local/etc/luarocks/config-5.1.lua (ok) User : /home/spc/.luarocks/config-5.1.lua (ok) Rocks trees in use: /home/spc/.luarocks Okay, so then I: [spc]lucy:~/apps/luarocks/src>./bin/luarocks install luarocks Installing http://rocks.moonscript.org/luarocks-2.2.0-2.src.rock... Using http://rocks.moonscript.org/luarocks-2.2.0-2.src.rock... switching to 'build' mode Updating manifest for /home/spc/.luarocks/lib/luarocks/rocks No existing manifest. Attempting to rebuild... luarocks 2.2.0-2 is now built and installed in /home/spc/.luarocks (license: MIT/X11) [spc]lucy:~/apps/luarocks/src> Okay. Now, when I attempt to use $HOME/.luarocks/bin/luarocks: [spc]lucy:~/.luarocks/bin>./luarocks Site-local luarocks/site_config.lua file not found. Incomplete installation? LuaRocks 2.2.0, a module deployment system for Lua NAME /home/spc/.luarocks/lib/luarocks/rocks/luarocks/2.2.0-2/bin/luarocks - LuaRocks main command-line interface SYNOPSIS /home/spc/.luarocks/lib/luarocks/rocks/luarocks/2.2.0-2/bin/luarocks [--from=<server> | --only-from=<server>] [--to=<tree>] [VAR=VALUE]... <command> [<argument>] GENERAL OPTIONS These apply to all commands, as appropriate: --server=<server> Fetch rocks/rockspecs from this server (takes priority over config file) --only-server=<server> Fetch rocks/rockspecs from this server only (overrides any entries in the config file) --only-sources=<url> Restrict downloads to paths matching the given URL. --tree=<tree> Which tree to operate on. --local Use the tree in the user's home directory. To enable it, see '/home/spc/.luarocks/lib/luarocks/rocks/luarocks/2.2.0-2/bin/luarocks help path'. --verbose Display verbose output of commands executed. --timeout=<seconds> Timeout on network operations, in seconds. 0 means no timeout (wait forever). Default is 30. VARIABLES Variables from the "variables" table of the configuration file can be overriden with VAR=VALUE assignments. COMMANDS build Build/compile a rock. doc Shows documentation for an installed rock. download Download a specific rock file from a rocks server. help Help on commands. Type '/home/spc/.luarocks/lib/luarocks/rocks/luarocks/2.2.0-2/bin/luarocks help <command>' for more. install Install a rock. lint Check syntax of a rockspec. list Lists currently installed rocks. make Compile package in current directory using a rockspec. new_version Auto-write a rockspec for a new version of a rock. pack Create a rock, packing sources or binaries. path Return the currently configured package path. purge Remove all installed rocks from a tree. remove Uninstall a rock. search Query the LuaRocks servers. show Shows information about an installed rock. unpack Unpack the contents of a rock. upload Upload a rockspec to the public rocks repository. write_rockspec Write a template for a rockspec file. CONFIGURATION Lua version: 5.1 Configuration files: System: /etc/luarocks/config.lua (not found) User : /home/spc/.luarocks/config-5.1.lua (ok) Rocks trees in use: /home/spc/.luarocks [spc]lucy:~/.luarocks/bin> I'm concerned about two things: 1) that luarocks/site_config.lua wasn't copied. 2) that it's not defaulting to /usr/local/etc/luarocks. I don't know if there's an actual bug here or what, but this upgrade has been a rather nasty one. -spc [1] It may have had something to do with initially installing LuaRocks via source a long time ago, then switching to updating via luarocks itself. I also use a local tree in $HOME/.luarocks, with appropriate $LUA_PATH and $LUA_CPATH pointing there first before hitting /usr/local directories for Lua modules. That's a guess on my part since I mucked up a few instances of LuaRocks on several machines (sadly, I wasn't paying attention to which window what logged into what machine), and I'm willing to admit that the entire thing might have been my fault at some level. |