=== chmj [~d3vic3@196.11.241.45] has joined #ubuntu-kernel [12:54] infinity: you awake yet? [02:58] infinity: ??? [03:43] lamont : Am no. [03:43] s/no/now/ [03:45] what were you calling a 'lamont bug' yesterday? [03:45] well, your last night, I guess [03:45] Oh, just a cute feature of the auto-dep-waiter. [03:45] which one is that? [03:46] Ifa build fails for any reason whatsoever, and it happened to build-dep on a virtual package, it'll get dep-waited on the virtual. [03:46] Anyhow, fixed on sanae. [03:46] and in baz? [03:47] I need to publish my branch somewhere, I guess. I'm still an arch/baz virgin. :) === lamont will update his branch [03:48] I just split "templates" into two arrays, one array that's an unconditional "you can take action on these regexps", and one that's "these only matter if we never got to a dpkg-source/dpkg-buildpackage run". === lamont notes the introduction of the 3 stooges. woot! [03:48] The above caseis now in the latter. [03:49] Hey, you had mo. :) [03:49] The debate between larry, curly or shemp was fierce, I'll tell ya. [03:49] yeah, but that wasn't where I got him from. :0) === lamont mirrors the archive [03:51] btw, new buildd-conf coming soon, etc. [03:52] Would it make more sense to add me to the log mails, or to change it to a list? [03:53] I guess I'd have to bug someone for a list then, so probably easier just to add me. :) [03:53] (The list sounds like less of a headache if buildd admins come and go down the road, though) [03:53] yeah - go ahead and add yourself and I'll fetch the changes and push again [03:54] yeah - but the whole thing goes *poof* come launchpad production [03:56] lamont+warty... Does that auto-expand to lamont@, or is that a .forward-hack, like debian's user-extension@? [03:56] + is the recipient delimiter - debian uses - [03:56] So how does one forward that to another address? :) [03:57] so lamont+warty gets delivered by postfix to 'lamont', with an arg of warty. Likewise, .forward+warty will forward just 'lamont+warty' [03:57] (Not that I care) [03:57] in my case, it comes in as $ARG to procmail [03:57] Right. Where do the .forward files live, perhaps is what I wanted to know. :) [03:57] to forward it, you could create .forward+warty [03:57] postconf forward_path [03:57] forward_path = $home/.forward${recipient_delimiter}${extension}, $home/.forward [03:57] (ie: With debian, they're on master) [03:57] oh - for canonical.com/ubuntu.com? [03:57] Aye. [03:58] they live where ever user@foo.com gets directed to [03:58] fiordland? [03:59] A host I can't log into. Yay. [03:59] that is, if you send mail to 'foo+bar@host' and 'foo+bar' isn't in the alias file, but 'foo' is, and rewrites 'foo' to 'baz@other.dom.ain', then postfix delivers the mail to 'baz+bar@other.dom.ain' [03:59] no. not on fiordland [03:59] in my case, the expansion happens on a mmjgroup.com host [03:59] and fiordland says 'lamont@ubuntu.com lamont@mmjgroup.com' [04:00] in virtual, truth be told [04:00] Oh, wherever it gets redirected to, you meant. [04:00] yeah [04:00] I was expecting to do the expansion on a canonical host. [04:00] Silly me. [04:00] although you _can_ add a specific entry to the map, and redirect 'foo+bar' somewhere different than 'foo' [04:00] yes I did have linux-kernel-headers installed :) [04:01] but canonical/ubuntu do not do that, to the best of my knowledege. [04:01] Micksa: yeah - I saw that when I did a little digging.. [04:01] No big deal anyway, this was all purely academic. [04:01] infinity: np [04:05] Hrm, will warty-mail.py -t 'foo@bar.com,baz@quux.com' work? === infinity takes that as a "maybe". [04:10] hrm second [04:10] -t foo@bar.com -t baz@baz.org [04:11] and on that note, I'm gonna wander off for a bit... don't break everything, k? [04:11] (sorry - was distracted..) === infinity breaks everything. === lamont looked - it had appeared that you chickened out. :-) [04:17] infinity: i'm going to kindly request that you call your first php5 upload the infinity-breaks-everything release [04:27] Meh. My first php5 upload should be in the next week. But I need to sucker someone into packaging all that PEAR crap. [04:27] Also, this is hideously off-toping stuff in -kernel. [04:27] fabbione will be so pleased when he shows up. [04:27] infinity breaks everything is relevant everywhere :p [04:27] off-toping?... Also, off-topic. [04:28] I have this odd feeling I'm going to be stuck doing the PEAR stuff. [04:28] Which makes me want to KILL. [04:28] But it's the only way php5 (or even php4 4.3.11) will ever get uploade. [04:28] d [04:42] i'd offer to do it, except.. i won't. [04:42] :) [04:42] the closest i get to php at work is running an instance of squirrelmail [04:42] it's great [05:10] morning [05:22] squirrel is the most PHP I see in a day too. :) [05:24] PHP should die [05:25] i might as well write a change in the kernel to not allow any php binary to start [05:25] hehe [05:33] lamont: ping? === dilinger [dilinger@mouth.voxel.net] has joined #ubuntu-kernel === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-kernel === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-kernel === chmj [~d3vic3@196.11.241.45] has joined #ubuntu-kernel === dilinger [dilinger@mouth.voxel.net] has joined #ubuntu-kernel === doko [~doko___@dsl-082-082-194-124.arcor-ip.net] has joined #ubuntu-kernel [02:52] fabbione: ack === JaneW [~JaneW@212.33.141.9] has joined #ubuntu-kernel === JaneW [~JaneW@212.33.141.9] has left #ubuntu-kernel ["Leaving"] === lamont [~lamont@15.238.6.115] has joined #ubuntu-kernel === ashaak [~rick@adsl-ull-96-182.42-151.net24.it] has joined #ubuntu-kernel [10:56] hi === Sepheebear [~SepheeBea@cpe-68-175-56-52.nyc.res.rr.com] has joined #ubuntu-kernel === Sepheebear [~SepheeBea@cpe-68-175-56-52.nyc.res.rr.com] has left #ubuntu-kernel ["Leaving"] [11:55] fabbione: you awake? [11:55] fabbione: do we have ip6tables conn tracking support yet?