[00:00] skellat, Unit193 I can toss Kubuntu on my laptop and bring it to OLF if you need another laptop... [00:00] I will be there on Saturday. [00:00] I'm supposed to know something? :P [00:01] :P [00:01] How are things? [00:01] (Thinking I won't be able to) Not too bad, about to head out. [00:01] Sweet. :) [00:04] Darkwing: See you Saturday then. Too bad you'll miss the fun on Friday. SEE: http://ohiolinux.org/friday [00:04] [ Friday Schedule - Ohio LinuxFest 2013 | Ohio LinuxFest 2013 ] - https://j.mp/RI5vzK [00:08] * skellat counts the days until he needs to ponder the NMU process or talking to an FTP assistant about this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712102 [00:08] [ #712102 - Plugin no longer functions with Twitter or Identica - Debian Bug report logs ] - https://j.mp/17xBg4o [02:11] Darkwing: Yes, it was verey sweet. \o/ === ChanServ changed the topic of #ubuntu-us-oh to: Welcome to the IRC home of Ubuntu Ohio! | Check us out at http://loco.ubuntu.com/teams/ubuntu-us-ohio/ | Current podcast episode (129): http://tx0.org/6ki/ FLAC Version (128): http://tx0.org/6kh/ | Never attribute to malice what can be better explained by incompetence === ChanServ changed the topic of #ubuntu-us-oh to: Welcome to the IRC home of Ubuntu Ohio! | Check us out at http://loco.ubuntu.com/teams/ubuntu-us-ohio/ | Current podcast episode (129): http://tx0.org/6ki/ FLAC Version (129): http://tx0.org/6kh/ | Never attribute to malice what can be better explained by incompetence [16:03] skellat: so, Ubucon is Friday only? I would but, My wife has to work on Friday so, :/ [16:05] Darkwing: Yep. We'll still be glad to see you on Saturday, though. [16:25] skellat: Do you need another laptop with either ubuntu or Kubuntu? [16:25] or xubuntu or lubuntu or, anything. [16:35] Darkwing: Kubuntu is best. I've got Xubuntu covered. [17:36] paultag: don't take that new queue whining personally. its one silly broken perspective. the silent masses love you! [17:36] gilbert: ♥ [17:37] I have thick skin, but plessy is really just trying to grind me every chance he gets, this is the 3ed -devel topic about my actions he's postede [17:37] posted* [17:37] it's getting tiresome to have to correct his errors [17:38] his activity seems mostly about whining rather than constructive thinking [17:38] anyway, i tend to ignore his mails [17:38] I'm starting to get there [17:39] otherwise, how goes it??? [17:39] haven't chatted in a while... [17:39] Not bad, not bad! Bummed i'll not be at OLF [17:39] I miss everyone tons (I've been busy the last month or so) [17:39] oh, that's too bad :( [17:39] gilbert: how's the married life? [17:39] sunlight? [17:39] sunlight is killer, doing some municipal work [17:39] really good, but frustrating at times [17:39] Oh yeah, and real life [17:39] helping Mako move out and stuff [17:40] gilbert: Well good (except when it's not, but I'm sure it's still OK even then :) ) [17:40] haha, yeah. its just different having to take someone else into account whenever i do anything [17:41] i get in trouble way too often for too much computer time :( [17:41] hahahaha [17:41] d'awww [17:42] gilbert: Have you found a job (yet, I don't seem to remember, doing the professor thing, Doc?) [17:43] actually, i'm putting off the real job thing, but i may go into teaching at some point. i'm more about getting my business off the ground right now [17:43] Oh, right! [17:45] so, that's actually a lot of work, and a different learning experience [17:57] yeah, I can imagine [17:57] so much to keep track of [17:59] paultag: have you messed around with polly? [17:59] (the clang plugin) [17:59] I've not, let's see here [18:00] Warning: Even though this example makes it very easy to use Polly, you should be aware that Polly is a young research project. It is expected to crash, produce invalid code or to hang in complex calculations even for simple examples. In case you see such a problem, please check the Bug database and consider reporting a bug. [18:00] (awesome) [18:00] Oh dude, this is badass [18:00] there is that... [18:00] gilbert: does it seem to work alright? [18:00] don't know, just started looking at it today [18:00] the whole concept of automated parallel code just seems awesome [18:00] Yeah, this is pretty thrilling [18:01] I kinda want to try this out [18:02] (i really wish tar could run in parallel) [18:03] Yeah, humm [18:03] I mean, it is just IO bound [18:03] I wonder how hard that'd be. [18:03] just write out segments by working out the file sized / places beforehand, issue a bunch of reads, and write back as you get data [18:04] that'd be insane [18:04] yeah [18:04] so, i meant the whole compression+tar stack, where compress/decompress is the cpu bound task [18:04] Oh, aye [18:05] i get frustrated that chromium source takes almost 5 minutes to decompress :( [18:05] Oh jeez, that's right [18:05] I keep forgetting you work on all the hard shit in Debian (wine, chrome) [18:05] and it doesn't matter how many cpus i throw at it [18:05] yeah, pretty much... [18:06] is it bzip or gzip? [18:06] xz [18:06] hummm [18:06] what's the block size? [18:06] small enough. [18:06] Hummm. [18:07] I bet you could hack the uncompressor to just split at block sizes, which would be pretty clean [18:07] at worst you have nthreads - 1 blocks in memory [18:08] just found pxz, which could be interesting :) [18:08] Oohhhhhh, interesting! [18:09] Humm, they only talk about compression [18:09] I wonder if it's also decompressioon [18:09] Oh! and h0lger maintains it [18:09] neato [18:09] there is also pixz [18:09] sweet [18:09] (and bremnersoft!) [18:09] why do all my friends maintain xz packages? :) [18:10] b/c xz is the latest hottness :) [18:10] :) [18:12] btw, have you noticed apt-listdifferences in the new queue? [18:12] gilbert: I've not yet, need it through> [18:12] ?* [18:13] oh snap, this looks neat [18:13] i would of course like it to go through, but don't feel obligated to put it before anything else :) [18:13] gilbert: It's marked for ACCEPT. It's super small. I just opened it to check it out and ended up doing a full review :) [18:14] awesome! [18:14] I want to use it, too, looks neat [18:14] you're the best paultag :) [18:14] d'aww [18:14] yeah, i've been using it for weeks now to actually review changes going in, and its super useful. especially for security review [18:14] totally [18:15] although autotools cruft makes some stuff entirely unreviewable [18:15] Yeah, although it's pretty easyish to write stuff that'd filter out known noise [18:16] or use "filters" (debian/* only mode, upstream only mode, no-autotools mode) [18:16] via piping it through something [18:18] its on my TODO list :) [18:18] :D [18:19] i wish there was a policy against automatically generated code in source packages [18:19] I mean, yeah. There sorta is [18:19] technially it's not allowed, but sometimes it's let through when it causes too much work to strip it out [18:20] at the very least, 100% of the source needs to be there [18:20] (it's tough to enforce on .pngs, .jpgs, .wavs, etc) [18:20] but we try (even pdfs) [18:20] but yeah, die, autotools, die [18:21] hehe :) [18:24] alright, time to go hang out with my dad for the rest of the day [18:24] ♥ [18:24] later paultag :) [18:24] gilbert: thanks again for the words of support :) [18:24] o/ [18:24] hey no problem [18:24] your email seemed kind of down, so i wanted to help out [18:25] o/ [19:07] The things I miss while I'm dealing with a vacuum cleaner that broke down because of its thermal cut-out activating