=== jackson is now known as jackson_ === jackson_ is now known as jackson [09:24] Morning [09:47] Mornin o/ [09:51] lazyPower moin [09:51] \o jackson [12:15] Morning peoples, critters and everything else [15:08] lazyPower: I resolved the problem with missing /scripts. Ruby problem is still unresolved but I found a bug logged for it here: https://github.com/weechat/weechat/issues/433 [17:14] lazyPower: I confirmed this is the problem. If I create a .rb file with just 'require "uri"' in it and try to load it in weechat then I get the same error. [17:14] seems strange that the module loaded just fine in irb [17:14] and was even leveraging the URI module [17:15] Yes. I ran the same thing in irb and there is no issue. [17:15] its got to be loading from a broken $GEMHOME or something. [17:15] ruby is really hinky like this [17:16] Also, I fixed the /scripts problem by purging every package that was weechat related and then installing it again. I think I had an old weechat package plus a new one. Now I have ruby 2.0 only because weechat required it. [17:16] and why i resulted to using rbenv on all the things. [17:16] ok [17:16] i'm fairly certain that removing the ruby apt packages does not clear gems [17:16] so there's something leftover from an older install thats causing those headaches [17:16] either a config, a gem, or something else thats polluting your ruby env [17:17] that or we've shipped a crap copy of ruby [17:17] So how do I clean/fix? [17:17] i'm uncertain :| [17:17] it works in 1 condition, but not in another [17:18] Where did the uri module come from? Can I redownload and compile it or is it part of core? [17:18] so there's a good env in there somewhere (when you fire up irb), but not when you're executing weechat. [17:18] its part of core. [17:19] I don't really know what a gem consists of. Do they get autogenerated? Can I delete them and put them back? [17:23] Gems are a lot like python modules [17:23] they are classes (or collections of classes) with metadata wrappers [17:23] and they sometimes contain compiled stubs of c-bins for faster operation [17:24] its typically not a good idea to just gut GEMS from your system, as its extremely easy to brick a ruby install [17:24] if you purge all ruby, and i mean *all* ruby, you may get away with it by reinstalling. but i'm hesitant to recommend that