=== Logan__ is now known as Logan_ [08:34] I want to fix bugs (development). Should I be on this channel or #ubuntu-devel? If I should be on -devel or -motu, what is the different between the channels? [09:04] cc11rocks: Both and you might want to join -packaging as well. The difference is that -motu deals with unseeded packages and -devel with core packages. [09:04] Thanks iulian! [09:04] And please don't cross post. [09:05] I was telling MCR1 so he knew [09:05] And to tell people my question was resolved [09:05] See? He said thanks [09:05] cc11rocks: You've asked the same question in both channel. [09:06] s/channel/channels/ [09:06] Okay, will take that into account next time [09:07] Do you agree with MCR1 that I can fix the bugs in running OS? [09:08] If you would like me to cross-post the question, I can do that, but then I would be cross posting the question... [09:11] cc11rocks: I do. And no, please don't. [09:13] If I break a package I need to use, I can just reinstall it temporarily from the default repos., then continue with backed-up code later, correct? [09:13] Or should I be using that one command that lets you temporarily change root to whatever (chroot or something)? [09:14] I think chroot would be essentially the same as a VM... [10:54] bzr ubuntu:test failed - http://pastebin.com/3AqiTwyn [10:57] It's way past my bedtime, so if I could get a quick response, that would be awesome. If not, you can email the problem/solution at cc11rocks@yahoo.com . Looks to me as if it's outdated. I just did it, so I don't know how that is possible... [10:57] Either that, or I don't have change perms (which I shouldn't have) [10:59] I'll stick around for another 5 minutes [11:02] *bzr ubuntu:hello failed - http://pastebin.com/3AqiTwyn [11:13] Already, thanks for you help guys. If you guys figure out the issue, you can email me at cc11rocks@yahoo.com === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === Kiall is now known as zz_Kiall === zz_Kiall is now known as Kiall === Kiall is now known as zz_Kiall === zz_Kiall is now known as Kiall [21:35] I wonder what the difference between ruby-json-pure and ruby-json is [21:36] besides that the former is an apparently unmaintaned ubuntu only package which conflicts with the debian one .. [21:45] jtaylor: the json-pure gem is a json parser/encoder in pure ruby; the json gem has a c extension [21:46] they're api compatible, but the c extension is obviously much faster [21:46] yeah [21:46] i do'nt know what the packages are though [21:46] why do we need both? [21:46] upstream codebase is almost the same too [21:47] to the least the conflict between the packages should be resolved [21:47] is that a case for alternatives? [21:47] yeah, they should not conflict - they can be co-installed [21:47] at least in ruby-land. i don't know anything about the gem packaging situation [21:47] there's a reverse dependency in Ubuntu for it [21:48] you do need json-pure for things like jruby, where you don't get c extensions [21:48] which is not in Debian [21:48] but i don't even know whether the ruby packaging situation is evolved enough to support that sort of thing [21:49] I don't see an explicit conflicts either [21:49] oh, maybe in the newer package [21:49] quantal still fails [21:49] fails on what [21:49] aren't they different gems built from the same source? [21:49] on installation [21:50] bug 1026049 style failure [21:50] Launchpad bug 1026049 in ruby-json-pure (Ubuntu) "package ruby-json-pure (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/ruby/vendor_ruby/json.rb', which is also in package ruby-json 1.6.3-1" [Undecided,Confirmed] https://launchpad.net/bugs/1026049 [21:50] ah, yeah, that's a problem :) [21:50] nice the -pure package also fails to build [21:50] ruby-json-pure should put it in json_pure.rb IMHO [21:51] err, i'm not sure that makes sense [21:51] bug 1026049 [21:51] Launchpad bug 1026049 in ruby-json-pure (Ubuntu) "package ruby-json-pure (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/ruby/vendor_ruby/json.rb', which is also in package ruby-json 1.6.3-1" [Undecided,Confirmed] https://launchpad.net/bugs/1026049 [21:51] ups bug 935412 [21:51] Launchpad bug 935412 in ruby-json-pure (Ubuntu Precise) "ruby-json-pure version 1.5.1-0ubuntu3 FTBFS on i386 in precise" [High,New] https://launchpad.net/bugs/935412 [21:51] still affects quantal [21:51] the content of that json.rb is basically just [21:51] begin [21:51] require 'json/ext' [21:51] rescue LoadError [21:51] require 'json/pure' [21:51] end [21:53] I'd start by looking to see if ruby-vmc needs the pure ruby version or can use the c extension, if it can use the c extension, let's drop the forked version, we'd still have to fix up precise a bit better though with replaces/conflicts [21:53] it seems the only rdepend does not use jruby [21:53] so it could use the extension version [21:53] and we can kill the -pure [21:54] I mailed the uploader for an oppinion [21:54] jtaylor: at the canonical address? [21:54] yes [21:54] doesn't exist anymore :) [21:54] oh [21:56] debian 657881 [21:56] Debian bug 657881 in wnpp "ITP: ruby-json-pure -- This is a JSON implementation in pure Ruby." [Wishlist,Open] http://bugs.debian.org/657881 [21:57] no answer upstream since jan [21:57] does really not look like something we should have in the archive [21:59] hm but it is still active [21:59] jtaylor: I certainly don't think we should keep it Ubuntu only if the rdep can be switched, but if it gets packaged in Debian, I see no issue having both [22:00] I also have no issue if its maintained [22:00] but it does not look like it in ubuntu [22:00] ftbs since precise, pretty obvious conflicts [22:01] I'll mail the rdep maintainer if it can use the extension version [22:02] hm but who is that [22:02] noone is subscribed to bugs of the package ._. === Kiall is now known as zz_Kiall [22:10] jtaylor: it's in MOTU land, use your best judgment :), or maybe ask xnox as he seems to be involved in some this stuff [22:10] jtaylor: hello =) which stuff? [22:10] I reached logan in -devel [22:10] oh hey [22:11] I'm here as well :P [22:11] meh ruby, I use rbenv for that..... [22:12] * xnox goes back to idling =) [22:12] jtaylor: do you think it would be less buggy if the packaging were updated to 1.7.5 for ruby-json-pure? [22:12] http://rubygems.org/gems/json_pure [22:12] Logan_: possibly, but someone has to do that [22:12] because it's at 1.5.1 right now in the Ubuntu repo [22:12] right now the issue is that the two packages are not coinstallable [22:12] and updating to 1.7.5 could introduce its own bugs [22:12] they even fail with a dpkg error [22:12] which would require an FFe [22:12] so, basically, fun times [22:13] oh I see [22:13] so conflict them? [22:13] the problem is -pure fails to build [22:13] xnox: I pinged you as you seem to be involved with some of the partner/main archive crossover [22:13] so just conflicting them is not as trivial as it looks [22:14] oh [22:14] micahg: was I ? had no clue.... [22:14] Logan_: unless someone volunteers to fix/update the package I would prefer to remove it [22:14] I don't know much about ruby so I can't fix it [22:14] xnox: maybe not :), ISTR you filing some bugs related to that type of stuff [22:15] I would prefer to remove it regardless if we have a viable alternative from Debian [22:15] er...regardless, if [22:16] removing is good =) [22:16] but that requires changing ruby-vmc [22:16] for which it might be too late now [22:16] so we could for quantal just disable the testsuite, conflict the package and deal with it q+1? [22:16] similar for a precise sru? [22:17] jtaylor: nah, it's unseeded, should be easy enough to get an FFe if we can remove cruft [22:17] * ogra_ makes a note to tell slangasek that xnox plans to do the partner stuff ... [22:17] *g* [22:17] * micahg makes a note to hid from xnox at UDS [22:17] *hide [22:17] jtaylor: for a precise SRU that sounds good [22:18] Logan_: can you check if ruby-vmc would work with ruby-json? [22:18] or give guidance on how to check it? [22:18] micahg: I actually think you did pretty well at hiding from me at the last UDS. It seemed like most of the last UDS I spent with ogra_ infinity tumbleweed Laney and highvoltage [22:19] I wanted to go to the next uds for once, but no work interferes again ._. [22:19] =(((( [22:19] xnox: that's funny because I was with Laney and tumbleweed a lot of UDS as well [22:20] * xnox wonders if Laney & tumbleweed have identical twins [22:20] Maybe you guys spent most of the time together but you just cannot remember. [22:20] That's a possibility... [22:20] xnox, we just need to convince micahg to start smoking ;) (or you need to start spending more time inside next UDS ;) ) [22:21] ogra_: i am actually not smoking any more. [22:21] wow ! [22:21] ogra_: but that may change at the uds though [22:21] congrats [22:22] also electronic cigarettes are fun, cause they make a lot of smoke [22:23] jtaylor: I have no idea [22:23] I'd just remove ruby-vmc, tbh [22:23] * ogra_ doesnt trust them :) [22:23] people can just install it via gem if they want, no? [22:24] I mean, same with any gem [22:24] but [22:24] this is an exceptional case ;) [22:25] popcon 63 [22:26] if no one cares for it and we don't know how to test it, removing might be an option [22:26] on the otherhand we could just change the depend and "require" and see what happens [22:26] either people complain and we have someone to ask, it breaks and no one notices or everyting works fine [22:26] win win win [22:29] wait removing ruby-vmc also requires cloudfoundry removal [22:29] whatever that is [22:29] ups no same source [22:29] jtaylor: well, I'd suggest asking someone who's familiar enough with ruby to make sure the dep can be switched sanely [22:29] ogra_: i don't mind doing partner stuff by the way. [22:30] micahg: yes, I think I'll pop by debian-ruby tomorrow [22:30] thansk [22:30] someone there should know [22:30] *thanks [22:30] xnox, heh, dont overload yourself [22:30] json parsing should really be inside ruby itself nowadys [22:30] i was really not serious about partenr