[00:28] <ogasawara> tgardner: http://people.canonical.com/~ogasawara/config2options
[00:55]  * vanhoof is glad to see some perl around here :D
[08:15]  * abogani waves
[08:17] <abogani> Sorry for stupid question...
[08:17] <abogani> Anyone know how many and what are the "fakeroot debian/rules COMMAND" issued by a simple dpkg-buildpackage?
[08:17] <abogani> I'm trying to verify every step without restart the entire build process every time :-(
[08:17] <abogani> Thanks in advance!
[08:18] <amitk> abogani: look at 'debuild -nc'
[08:18] <amitk> or dpkg-buildpackage also takes that option, I believe
[08:26] <abogani> amitk: I'll take a look! Thanks!
[15:18] <__bjf> tgardner, you in the office?
[15:21] <__bjf> tgardner, i'm heading in now
[15:24] <tgardner> __bjf, yep
[16:18] <mpoirier> GrueMater:  o/
[16:43] <cnd> tgardner, apw, ogasawara: heads up:
[16:43] <cnd> there's a 3M multitouch patch that's in the works right now
[16:44] <cnd> sabdfl has explicitly said he wants it in the very next kernel update
[16:44] <cnd> even if it's not upstream
[16:44] <ogasawara> cnd: ack, send it to the list then.
[16:44] <cnd> no budging
[16:44] <cnd> will do, as soon as it's ready
[16:45] <ogasawara> cnd: I just uploaded yesterday, so will probably not do another till early next week if he's wanting an ETA
[16:46] <cnd> ok
[16:51] <bdrung> what do i need to do to get the lirc patch (bug #550369) also applied to the lucid kernel?
[16:51] <ubot2> Launchpad bug 550369 in lirc (Ubuntu Lucid) (and 3 other projects) "Hauppauge TV Card is detected as Leadtek IR in lucid (affects: 13) (dups: 3) (heat: 87)" [Undecided,Fix released] https://launchpad.net/bugs/550369
[16:52] <ogasawara> bdrung: I'd say open a new clean bug report, as that one is already marked Fix Released
[16:53] <ogasawara> bdrung: it'll then need to go through the Lucid SRU process (ie patch sent to the kernel-team mailing list and garner the appropriate number of acks etc)
[17:28] <ogasawara> JFo: bug chat today?
[17:35]  * smb cries
[17:35] <smb> Totally failed to do anything really on that 
[17:52] <bdrung> ogasawara: the linux task is wrongly marked as invalid. can i reopen it or should i use a new one?
[17:52] <ogasawara> bdrung: I
[17:53] <ogasawara> 'd say open a new one to avoid confusion
[17:53] <bdrung> ogasawara: but it's the same issue, because the linux kernel uses a copy of lirc source code
[17:54] <ogasawara> bdrung: you are free to do what you want, I'm just giving my recommendation
[17:54] <ogasawara> bdrung: ie you can re-open the linux task
[17:55] <bdrung> ogasawara: where do i get the linux source tree?
[17:55] <ogasawara> bdrung: git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git
[17:59] <vanhoof> tgardner: ping
[17:59] <vanhoof> tgardner: if you have a sec can you check out bryan's last comment on https://bugs.launchpad.net/ureadahead/+bug/491943
[17:59] <ubot2> Ubuntu bug 491943 in ureadahead (Ubuntu) (and 1 other project) "Kernel trace buffer should be set to less unrealistic value (affects: 16) (dups: 2) (heat: 88)" [High,Triaged]
[17:59] <vanhoof> tgardner: im thinking we should spin another bug for this, wanted to see if you agree
[18:02] <tgardner> vanhoof, I'd like to chat with keybuk about profiling the number of CPUs and system RAM before allocating ureadahead buffers.
[18:02] <tgardner> right now its a fixed value
[18:05] <vanhoof> tgardner: cool
[18:05] <vanhoof> tgardner: i just didnt want to spin that bug (which fixed up the AMD issue) into something new
[18:05] <tgardner> though this particular bug looks like it might be related to 32 bit PAE
[18:06] <tgardner> vanhoof, I'll develop a patch for ureadahead that Bryan can test.
[18:07] <vanhoof> tgardner: awesome
[18:07] <vanhoof> tgardner: the immediate urgency died down for the project we're involved with due to time constraints
[18:08] <tgardner> vanhoof, yeah, you just killed ureadahead, right?
[18:08] <tgardner> or removed*
[18:08] <vanhoof> tgardner: yeah, bug was found the day of the deadline, so it was the only option we saw
[18:08] <tgardner> ack
[18:09] <vanhoof> thanks tgardner 
[18:16] <robbiew> ogasawara: fyi...it appears the tech board will approve the removal of sparc and ia64 before next week's meeting.  Here's the thread -> https://lists.ubuntu.com/archives/technical-board/2010-August/000441.html
[18:16] <ogasawara> robbiew: sweet, thanks for the note
[20:11] <JFo> ogasawara, yeah, I'm a jerk
[20:11] <JFo> I took longer than planned to get my glasses
[20:11] <JFo> and I completely forgot the bug chat
[20:11] <JFo> sigh*
[21:13] <tgardner> bjf, ogasawara : http://www.kernel.org/pub/software/scm/git/docs/git-notes.html
[21:34] <soren> When would the kernel choose to send SIGKILL to a process on its own? I'm desperately trying to get a user-mode-linux thing to work, and I have these odd problems getting it to boot.
[22:57] <soren> Answer: When the process exceeds its stack limit which is excruciatingly often when you're using a version of uml compiled against linux-source-2.6.32 at an /extremely/ unfortunate time.