[12:54] <lamont__> infinity: you awake yet?
[02:58] <lamont> infinity: ???
[03:43] <infinity> lamont : Am no.
[03:43] <infinity> s/no/now/
[03:45] <lamont> what were you calling a 'lamont bug' yesterday?
[03:45] <lamont> well, your last night, I guess
[03:45] <infinity> Oh, just a cute feature of the auto-dep-waiter.
[03:45] <lamont> which one is that?
[03:46] <infinity> 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] <infinity> Anyhow, fixed on sanae.
[03:46] <lamont> and in baz?
[03:47] <infinity> I need to publish my branch somewhere, I guess.  I'm still an arch/baz virgin. :)
[03:48] <infinity> 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".
[03:48] <infinity> The above caseis now in the latter.
[03:49] <infinity> Hey, you had mo. :)
[03:49] <infinity> The debate between larry, curly or shemp was fierce, I'll tell ya.
[03:49] <lamont> yeah, but that wasn't where I got him from. :0)
[03:51] <lamont> btw, new buildd-conf coming soon, etc.
[03:52] <infinity> Would it make more sense to add me to the log mails, or to change it to a list?
[03:53] <infinity> I guess I'd have to bug someone for a list then, so probably easier just to add me. :)
[03:53] <infinity> (The list sounds like less of a headache if buildd admins come and go down the road, though)
[03:53] <lamont> yeah - go ahead and add yourself and I'll fetch the changes and push again
[03:54] <lamont> yeah - but the whole thing goes *poof* come launchpad production
[03:56] <infinity> lamont+warty... Does that auto-expand to lamont@, or is that a .forward-hack, like debian's user-extension@?
[03:56] <lamont> + is the recipient delimiter - debian uses -
[03:56] <infinity> So how does one forward that to another address? :)
[03:57] <lamont> so lamont+warty gets delivered by postfix to 'lamont', with an arg of warty.  Likewise, .forward+warty will forward just 'lamont+warty'
[03:57] <infinity> (Not that I care)
[03:57] <lamont> in my case, it comes in as $ARG to procmail
[03:57] <infinity> Right.  Where do the .forward files live, perhaps is what I wanted to know. :)
[03:57] <lamont> to forward it, you could create .forward+warty
[03:57] <lamont>  postconf forward_path
[03:57] <lamont> forward_path = $home/.forward${recipient_delimiter}${extension}, $home/.forward
[03:57] <infinity> (ie: With debian, they're on master)
[03:57] <lamont> oh - for canonical.com/ubuntu.com?
[03:57] <infinity> Aye.
[03:58] <lamont> they live where ever user@foo.com gets directed to
[03:58] <infinity> fiordland?
[03:59] <infinity> A host I can't log into. Yay.
[03:59] <lamont> 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] <lamont> no.  not on fiordland
[03:59] <lamont> in my case, the expansion happens on a mmjgroup.com host
[03:59] <lamont> and fiordland says 'lamont@ubuntu.com lamont@mmjgroup.com'
[04:00] <lamont> in virtual, truth be told
[04:00] <infinity> Oh, wherever it gets redirected to, you meant.
[04:00] <lamont> yeah
[04:00] <infinity> I was expecting to do the expansion on a canonical host.
[04:00] <infinity> Silly me.
[04:00] <lamont> although you _can_ add a specific entry to the map, and redirect 'foo+bar' somewhere different than 'foo'
[04:00] <Micksa> yes I did have linux-kernel-headers installed :)
[04:01] <lamont> but canonical/ubuntu do not do that, to the best of my knowledege.
[04:01] <lamont> Micksa: yeah - I saw that when I did a little digging..
[04:01] <infinity> No big deal anyway, this was all purely academic.
[04:01] <lamont> infinity: np
[04:05] <infinity> Hrm, will warty-mail.py -t 'foo@bar.com,baz@quux.com' work?
[04:10] <lamont> hrm  second
[04:10] <lamont> -t foo@bar.com -t baz@baz.org
[04:11] <lamont> and on that note, I'm gonna wander off for a bit... don't break everything, k?
[04:11] <lamont> (sorry - was distracted..)
[04:17] <dilinger> infinity: i'm going to kindly request that you call your first php5 upload the infinity-breaks-everything release
[04:27] <infinity> 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] <infinity> Also, this is hideously off-toping stuff in -kernel.
[04:27] <infinity> fabbione will be so pleased when he shows up.
[04:27] <dilinger> infinity breaks everything is relevant everywhere :p
[04:27] <infinity> off-toping?... Also, off-topic.
[04:28] <infinity> I have this odd feeling I'm going to be stuck doing the PEAR stuff.
[04:28] <infinity> Which makes me want to KILL.
[04:28] <infinity> But it's the only way php5 (or even php4 4.3.11) will ever get uploade.
[04:28] <infinity> d
[04:42] <dilinger> i'd offer to do it, except.. i won't.
[04:42] <dilinger> :)
[04:42] <dilinger> the closest i get to php at work is running an instance of squirrelmail
[04:42] <dilinger> it's great
[05:10] <fabbione> morning
[05:22] <infinity> squirrel is the most PHP I see in a day too. :)
[05:24] <fabbione> PHP should die
[05:25] <fabbione> i might as well write a change in the kernel to not allow any php binary to start
[05:25] <dilinger> hehe
[05:33] <fabbione> lamont: ping?
[02:52] <lamont> fabbione: ack
[10:56] <ashaak> hi
[11:55] <lamont_r> fabbione: you awake?
[11:55] <lamont_r> fabbione: do we have ip6tables conn tracking support yet?