=== rsalveti_ is now known as rsalveti === LordOfTime is now known as TheLordOfTime === yofel_ is now known as yofel [17:14] * TheLordOfTime yawns [17:14] bleh more bugs landed on my plate :/ [18:25] TheLordOfTime: Learn to run faster? [19:09] penguin42, i should :P [19:10] penguin42, regarding your question yesterday, if you've reported to Debian and Upstream, and filed a patch for Ubuntu, just wait, i think it needs fixing in Debian first, or upstream. [19:10] penguin42, and given this is Universe, is upstream even alive? [19:10] doesn't look like its been updated since Lucid. [19:12] and packages.qa.debian shows its not been updated since 2k9 either: http://packages.qa.debian.org/t/tcpick.html [19:26] TheLordOfTime: No I think upstream is pretty dead [19:28] penguin42, i doubt this'll be fixed in Debian, then, you may want to talk to -MOTU and see if they would work with an ubuntu-only patch [19:28] (divergence from upstream) [19:28] s/upstream/debian/ [19:29] since its in Universe, they'd have better insight [19:30] TheLordOfTime: Probably the best thing is to kill it in debian, but are people using it - remember it only breaks for Debian [19:30] bah [19:30] for Ubuntu [19:30] do people in Ubuntu still use it? [19:30] we got bug reports for it [19:30] also, how "broken" is it? [19:31] and why don't people actually bother using the STANDARD packet tracers :/ [19:31] penguin42, there may be bugs, but the majority of them are *old* [19:31] TheLordOfTime: We have two bug reports for it, one of which is the one I patched; the other oene is locked and I can see a fix for it, but it is a bit grim [19:32] TheLordOfTime: Well they're not old, the oneI fixed was dated this month - bug 1086534 [19:32] Launchpad bug 1086534 in tcpick (Ubuntu) "*** buffer overflow detected ***: tcpick terminated with -t arg" [Medium,Triaged] https://launchpad.net/bugs/1086534 [19:32] don't reference this one: https://bugs.launchpad.net/ubuntu/+source/tcpick/+bug/289976 (its hardy) [19:32] Launchpad bug 289976 in tcpick (Ubuntu) "Segmentation fault on tcpick with fragmented IP packets" [Undecided,Confirmed] [19:32] (hardy's pretty old) [19:32] and bug 1026902 was July [19:33] we may want to poke motu about it [19:33] see what they say [19:33] i'm usually hesitant to say a package needs purging, but if its dead and debian's bugs arent getting fixed either... [19:34] http://qa.debian.org/popcon.php?package=tcpick [19:34] pfft [19:34] that's in Debian, not Ubuntu [19:34] we need a tracker for Ubuntu :P [19:35] hehe [19:35] oh interesting they have a link to packages that also show the ubuntu bugs [19:36] I think I'll mail the debian package maintainer - although it's a little less than a month ago so shouldn't push too hard [19:38] * penguin42 needs to extract some life from some debian-multimedia guys as well [19:38] not sure the email address routes anywhere [19:39] why? === LordOfTime is now known as TheLordOfTime [23:41] penguin42, according to Debian BTS, the maintainer field routes to a .com.mx [23:41] not sure that's a valid domain? [23:41] something.com.mx [23:41] (something actually says something though) [23:41] why, it's just commerce in Mexico [23:46] really? [23:46] *shrugs* [23:46] seems to not resolve from here. [23:46] * TheLordOfTime shrugs again [23:52] * penguin42 could do an mx resolve on it [23:53] well my dns is a little wonky today [23:53] so maybe that's the issue [23:53] *shrugs* [23:53] might be a good idea to poke the maintainer though [23:54] (and sorry for randomdisappearanceact :P) [23:55] already did [23:56] good :) [23:56] oh and THERE'S the oidentd bug i was looking for [23:56] how come it took 12 hours to be filed :/ [23:56] filed? [23:56] https://bugs.launchpad.net/bugs/1094773 <-- took 12 hours between ubuntu-bug on affected system and it showing up on LP [23:56] Launchpad bug 1094773 in oidentd (Ubuntu) "oidentd spawns a new process for all new connections unless -l [number] defined" [Undecided,New] [23:57] wonder if its net is lagging horridly [23:57] * TheLordOfTime runs networking checks [23:57] odd, doesn't u-b normally do it there and then? [23:58] usually [23:58] which is why i'm confuzled and amazed it took that long