[00:17] * jjohansen heads out for a bit, back on in 20 [00:31] pgraner, http://kernel.ubuntu.com/~bradf/table.html [00:32] pgraner, that is with a better dataset, just lucid bugs [00:32] pgraner, still very simple algo. none of the code you sent to me === bjf is now known as bjf[afk] === maco is now known as maco2 [02:43] kees: have you boot tested that last yama patch you added? "UBUNTU: SAUCE: Yama: verify inode is symlink to avoid bind mounts" [02:44] kees: I'm getting an oops/panic on two test systems I've tried (one's i386 the other amd64) [02:45] kees: if I back out just that last patch, the systems boot fine [02:45] kees: I posted some test kernels on tangerine in my home directory under yama/ [02:46] kees: the "good" debs are of the latest ubuntu-maverick tip http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=summary which contains just the first 2 yama patches you originally submitted [02:47] kees: the "bad" debs are the latest ubuntu-maverick tip plus that last yama patch you added [02:50] kees: for now I'm only going to apply the first 2 patches and do an upload upload since I rebased to 2.6.35-rc5 and want to get it uploaded for testing asap [03:05] how do i add directories to the module search path ? [03:11] Dawgmatix: i don't think you can [03:11] ok [03:12] oh, you can add -d to the modprobe command line [03:12] but I don't think you can specify it for other invocations of modprobe [03:13] hmm looks like you can change modules.conf to add paths too [03:13] I don't see a configuration parameter to do that [03:14] I was going by http://pwet.fr/man/linux/formats/modules_conf [03:14] that has a path parameter that you can set === jjohansen is now known as jjohansen-afk [03:14] back on later [03:16] Dawgmatix: my modprobe isn't trying to read any /etc/modules.conf file though [03:16] (sudo strace -e trace=open,stat modprobe pretend-module-name) [03:16] yeah i just realised ubuntu doesnt come with a modules.conf [06:22] moin [07:10] ogasawara: I did; I functionally tested it, in fact. You can see my tree on tangerine. :( [07:11] ogasawara: ah, no, I totally lied. [07:11] ogasawara: one sec, I will fix. [07:12] ogasawara: I had a slightly different version. :( [07:13] kees: no worries, just push the fixed version to your tree and I'll pull it [07:13] kees: it'll make the next upload [07:13] it's really loopy having my pristine yama source, the security-next tree and the maverick tree. :P [07:14] kees: just for good measure, go ahead and send the pull request to the mailing list [07:15] ogasawara: okay. is the tree with the other two pushed already? I can rebase my maverick tree if so. [07:15] kees: I've already applied and uploaded the other two [07:15] okay, I'll rebase === hrw|gone is now known as hrw === bryce-alt is now known as bryyce [09:23] apw, smb: http://www.amazon.co.uk/dp/B003HIWHN0 [09:48] lag: class2? [09:51] * lag shrugs [09:52] I thought SDHC was class 4? [09:58] There are class 6 of those as well, though that kind of triples the price [10:10] lag: class2/4/6/10 maybe class8 too [10:11] @ 32GB? [10:16] The HTC Desire's specification says: "microSD™ memory card (SD 2.0 compatible)" [10:16] Does that mean classes >2 won't work? [10:16] lag: I did not know that 32GB microsd exists [10:16] lag, don't think so, think thats specification 2.0 [10:16] That's what I was bringing to apw and smb's attention [10:16] lag: that mean that it support microsd [10:17] How does that differ to class 2? [10:17] class 2/4/6/8/10 is just speed [10:17] classes are simply speed specifications [10:17] presumably minimum speeds in some sense [10:17] sd 2.0 is specification of SD standard version 2.0 [10:17] k [10:18] so things like "suport for 1/4/8 bits, sdio support things" [10:29] 1 === amitk is now known as amitk-afk [10:35] What would be the best way to get a patch into the kernel? I basically just need to drag'n'drop the wacom module source files into the kernel. [10:36] The kernel wacom source is out of date and doesn't support the wacom bamboo pen & touch series. [10:39] I've figured out the the source files in drivers/input/tablet/wacom* are the same as those in the linuxwacom package, so a simple drag and drop of the files should work. Can someone give me some advice on this. [10:40] ripps, Upgrading a whole driver is usually rather frowned upon for released kernels, at least if that brings a log of changes. And the other question would be whether it needs some userspace update as well? [10:41] One thing might be to have the updated driver included in linux-backports-modules [10:41] smb: I've already confirmed that the only the kernel module needs update. I've currently been pointing people to use a wacom-dkms package in one of my ppas [10:41] s/a log/a lot/ [10:42] yeah, linux-backports-modules sounds like a good idea [10:42] The problem is in lucid too, would it be possible to backport the driver there, as well? [10:45] If you say Lucid, too. Is the other release Maverick? Ultimately for Maverick it would be a goal to update the driver upstream as well. Though it might be a bit late for that. And yes, for Lucid I think it would be reasonable to have that backport there as well. Maybe needs thinking of having a seperately grouped binary package, like linux-backports-input [10:45] sounds good to me. [10:47] although, the kernel input api is different between the lucid kernel and the maverick kernel, so the maverick version of the wacom source needs to be tweaked [10:47] Is there a guide out there on how to make a linux-backports package? [10:47] ripps, So I would say the best approach is to bring the issue and proposal up in a mail to kernel-team@lists.ubuntu.com and let it be discussed/documented there [10:48] ripps, We do the l-b-m package and sadly I guess to make that extension is rather well undocumented and probably complex. === amitk-afk is now known as amitk [11:38] apw, smb: I've found a regression in the kernel from 2.6.32 to 2.6.35 which affects the radeon driver. How do you suggest that I start bisecting? I cloned the maverick branch but obviously it doesn't contain an Ubuntu-2.6.32 tag [11:38] tseliot, thats triciker [11:39] apw: how tricky is that? [11:39] tseliot, i would try the mainline kernels and see if the issue is in there [11:39] ah [11:39] as thats much easier to bisect [11:40] and you can use the mainline builds in between to narrow your search [11:41] apw: and shall I rely on the date the kernel was built and look it up in the linus tree? === hrw is now known as hrw|gone [11:53] tseliot, how to map an ubuntu kernel into a mainline version is a question in the kernel FAQ :) [11:54] https://wiki.ubuntu.com/Kernel/FAQ#Given an Ubuntu kernel package version how do we find the exact mainline release it is based on? [11:54] which points you here: http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html [11:54] apw: thanks, I'll RTFM ;) [11:57] :) === hrw|gone is now known as hrw [12:44] did the kernel-team mailinglist get my linux-backports-input proposal? [12:45] ripps, Did not yet see anything but it might be stuck in moderation until the right half of the planet is awake [13:32] smb: thanks for your kernel source, it was built yesterday evening and we test it today :) [13:33] TeTeT, Good to hear [13:45] pgraner, how is your machine which was grinding till we freed the buffers ... how many more cycles has it managed [13:47] apw, its done 35 and was doing fine until I started copying data to the usb disk, now even mumble is dead, I had to switch to my netbook [13:47] apw, same box is showing the I/O issues [13:48] pgraner, ok [13:48] 35 would be counted as success me thinks on the original issue [13:48] apw, yep I would agree, so tgardner's patch should do the trick [13:48] pgraner, fingers crossed [14:08] hi all. I was wondering how can I know which cn_idx number I should use for DRBD. Where can I find that #? [14:09] andreserl, you might have better luck asking that on #ubuntu-server as they do more with DRBD than we do [14:10] apw, yeah but afaik the cn_idx is the number related to the kernel. But will try asking there :) THanks [14:10] (I mean the number that the module uses in the kernel) [14:10] andreserl, its just not a kernel feature most of us would routinely use, they might and might answer sooner (or indeed at all :) [14:11] apw, ok :) [14:11] thanks [14:15] * apw cirtanly has no idea what the cn_idx even is :) [14:20] apw, Guess we can guess what the idx part is but cn... :) [14:20] smb, cn == channel number ? [14:21] connection index [14:22] Could be a lot without knowing. So andreserl might know more than us here [14:23] smb, I just know I need to now the cn_idx for the DRBD kernel module and make the change in the drbd8 package before uploading :/ [14:23] what does cn_idx stand for even [14:24] idx presumably is the index ... [14:24] apw, I think we were at connection index [14:24] apw, connection index [14:24] But server is likely the guys. Given they provide the kernel module as dkms [14:25] smb, The drbd kernel module is included in the kernel starting from 2.6.33, [14:25] so there's no longer the need to use dkms [14:26] and even so, when using dkms, we also specify the cn_idx [14:27] andreserl, ok, I might be backwards there. Last thing I remember was making it dkms because we had it in seperate modues and too often behind what was needed [14:29] * apw is looking for it [14:29] smb, ummm what I know is that in drbd module was in hardy kernel, after that, it wasn't. And for what I understand, from now on, the DRBD module will be in the kernel starting from 2.6.33 [14:31] http://www.drbd.org/download/mainline/ [14:33] in the drbd8 source package, in debian/dkms.conf we specify the cn_idx: "MODULES_CONF[0]="options drbd cn_idx=7" [14:33] in hardy, Intrepid, I believe it used to be 6 [14:33] in debian is 4 [14:33] so now in maverick, I don't really know which one is it [14:34] include/linux/connector.h:#define CN_IDX_DRBD 0x8 [14:34] apw, awesome! thanks :) === sconklin-gone is now known as sconklin [15:19] tgardner: looks like you're the person with the IGEPv2 OMAP board [15:23] amitk, oddly enough, I am just in the process of turning it on this morning. I've never encountered a web site that is quite so bad (http://www.igep-platform.com) [15:24] heh :) [15:25] tgardner: some folks are interested in knowing if it is well-supported in ubuntu. My suspicion is that it'll required only a few patches to get it well supported. [15:26] amitk, the default image isa 2.6.28 kernel, but I see they alaso have up to 2.6.33 on their web site [15:26] tgardner: I would just try to boot default ubuntu omap3 kernel [15:26] amitk, perhaps I should just try a Lucid omap3 rootfs? [15:27] tgardner: just boot with lucid [15:27] including the kernel [15:27] amitk, easier said then done. still figuring out how to do that. [15:27] the only thing I have no idea about is the bootloader on there.... so keep what they ship with. [15:28] amitk, I think it'll boot from micro SD [15:28] tgardner: keyword: ogra [15:28] tgardner: but yes, micro-sd is the quickest way [15:29] amitk, gotta find the rootfs first. somewhere on ubuntu.com ? [15:32] tgardner: http://cdimage.ubuntu.com/ports/releases/10.04/release/ [15:33] amitk, try the omap server install? [15:34] tgardner: yes, unfortunately we don't provide premade rootfs yet [15:34] you can create your own rootfs with rootstock scripts [15:34] amitk, so if it boots from SD, where does it install? External USB driver? [15:35] tgardner: you'll have to use netboot to get your setup on SD card. [15:35] yes, USB drive/HDD [15:36] tgardner: I'm running into the same problem install lucid UNR on beagleboard. [15:40] mpoirier, on the phone, hang on. === bjf[afk] is now known as bjf [15:46] tseliot, about ? [15:46] apw: yep [15:47] wondering if you knew what plymouth did when it is started ... whether it clears the VT it is selecting for instance [15:48] in broad terms its activity while owning the VT [15:49] tseliot, ^^ [15:51] tseliot, can i get plymouth to tell me what happened to it during a boot for instance. interested to know (as an example) if it gets a resize event on drm load [15:51] apw: plymouth gets its own "screen" that it swaps in with a black screen (at the beginning) [15:52] ah, a resize event? Why do you need to know that? [15:53] well i am trying to work out when plymouth has control over the screen and what it does during the time [15:53] it being the one which switches VT is interesting [15:54] apw: if you want some good answers you can join #plymouth and ask halfline (i.e. the author). He's very helpful === jjohansen-afk is now known as jjohansen === doko_ is now known as doko === sconklin is now known as sconklin-afk [16:07] JFo, are we having the bug chat this morning ? [16:08] no, we are having the team bug day in this channel [16:08] there was no plan for a bug chat [16:08] just coordination to keep from duplicating effort [16:08] JFo, my cal says 10am-1pm .. could my cal is misbehaving [16:09] nope, that is correct [16:09] 3 hour block per tgardner to solely work on bugs [16:09] manjo, Mine says from 5pm to 8pm, yours is in the wrong tz. ;-P [16:09] nicely blocked out on the cal by request of smb [16:09] :) [16:10] Right, at least we won't forget it then [16:10] yeah don't know why my cal is always messed up [16:10] we need utc google cal [16:10] hmmm, your times may be off. tgardner wants it to start at 8AM PST [16:10] * smb hopes manjo recognizes a joke when it passes by [16:11] heh [16:11] smb, wrong tz... ah you got me ! [16:11] sorry could not resist [16:11] manjo, the time is now 8:12 PST [16:12] smb, yeah easy target [16:12] 12 minutes past the start of the bug day [16:13] JFo, your search URL in the calendar event doesn't produce many items [16:13] apw, JFo So there one or the other where at least some issues are understood but whether there is a fix is unclear and also how much other issues are mixed [16:13] like bug 563156 [16:13] Launchpad bug 563156 in linux (Ubuntu) "[ATI Graphics][Lucid] laptop runs hot, shorter battery life, fan always on (affects: 31) (heat: 179)" [High,Triaged] https://launchpad.net/bugs/563156 [16:13] tgardner, search url? [16:13] https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-proposed+karmic&field.tags_combinator=ALL [16:14] ugh [16:14] wrong link [16:14] tgardner, http://qa.ubuntu.com/reports/jfo/kernel-Top50.html [16:14] I'll fix [16:14] tgardner, I replied to his mail with the right link [16:14] I hope to the right mail [16:14] JFo: what group membership gets all that bug mail? (I want to remove myself from the group). kernel-bugs doesn't seem to be it. [16:14] tgardner, changed it now [16:14] amitk, ubuntu-kernel-team ? [16:15] tgardner: aah, it is kernel-team? [16:15] amitk, arnt you *supposed* to be subscribed to get all bug mails ? [16:15] smb, I had a bad link in the calendar item [16:15] so I fixed it [16:15] sorry for leaving it out of the e-mail [16:15] manjo: nope, everyone in a _certain_ group gets all bug mail filed against the linux package [16:15] JFo, Oh calendar. :) Good. I saw that there was only a [1] in your mail [16:15] got in too big a hurry [16:15] amitk, I get 'em because of 'You received this bug notification because you are a member of Canonical Kernel Team' [16:16] tgardner, i think amitk is saying he no longer wishes to be "a member of Canonical Kernel Team" [16:17] bjf, I'm not sure he gets a choice there. [16:17] heh [16:17] tgardner, maybe he is giving notice :-) [16:18] bjf: I've got 24871 emails in my ubuntu-bugs folder (and growing). But yes, that'd be a nice subtle way to give notice ;) [16:18] amitk, weren't you the one promoting server side procmail ? [16:18] don't do it amitk! think of the children! ;) [16:19] tgardner: it is all filtered away nicely, but it is an eyesore [16:23] bjf: http://launchpad.net/kslm [16:24] jjohansen, thanks === sconklin-afk is now known as sconklin [16:24] bjf: also www.headinthecloud.net [16:27] jjohansen, am i missing something, that launchpad link is little more than a title [16:28] bjf: nope, that is all I have [16:28] well that and the headinthecloud.net [16:38] pgraner, http://kernel.ubuntu.com/~bradf/table.html [16:39] bjf: from what I gathered kslm doesn't do atop functionality yet "KSLM which may add similar capabilities to the kernel but in a more elegant way" [16:40] bjf: from looking around I am not sure it does anything yet, I've asked SpamapS if he has anymore info [16:40] jjohansen, from the comment on the mailing list and the lack of other information, it's vaporware [16:40] yeah, that is my impression [16:53] JFo, is there a wiki page with your "standard replies"? [16:53] there isn't one with the kernel specific ones yet [16:54] there is for regular bug comments [16:54] but I assume you want the kernel specific ones [16:54] JFo, ack [16:54] sconklin, he is deafend [16:54] actually, I seem to recall there being one in KernelTeam bjf [16:55] manjo: no biggie. [16:55] I remember ogasawara pointing me to it [16:55] JFo, i'll hunt a bit [16:55] lemme dig it up, just a sec [16:55] * manjo gets some coffee [16:56] JFo: I've seen a bunch of "Pulse audio crashes when I play something" and "PA crashes when I configure inputs for recording" bugs lately - there are patches for some of those in the pile that's waiting in stable, which will get queued after the next security update for Lucid. [16:56] excellent [16:56] thanks for the heads up sconklin [16:57] it'll be a couple of weeks at least until they hit preproposed [16:57] possibly less [16:57] bjf: https://wiki.ubuntu.com/Bugs/Responses but I don't think that has our kernel stock replies listed [16:57] amitk, is there a Freenode ARM channel? [16:58] tgardner, bing it to the sprint and we'll get the board running maverick :) [16:58] *bring even [16:59] ogra, I've got the Lucid image on SD, but can't figure out how to get it to boot it. [16:59] tgardner: #ubuntu-arm, #armlinux, #linaro [16:59] take your pick [17:00] amitk, ack [17:01] tgardner, lucid only includes bootloader binaries for bagelboards [17:01] *beagle ... (they dont have a hole :P ) [17:02] tgardner, its likely that you need another bootloader binary [17:02] ogra, bagelboards, if they don't boot you can eat em [17:02] ogra, this gizmo has x-boot and u-boot, though I don't know what is actually installed [17:03] tgardner, so you end up in a serial u-boot prompt if you fire it up ? [17:03] ogra, nope, its got a 2.6.28 kernel that brings up X. [17:03] hmm [17:04] using on-board flash that came with it pre-programmed [17:04] well, you should see the boot process on the serial console somehow [17:04] ogra, I don't have the serial adapter, Loic is bringing it [17:04] and usually u-boot has an option to stop the boot so you can input bootloader cmds [17:04] ah [17:04] yeah, without it gets tricky === psurbhi is now known as csurbhi-afk [17:05] ogra, the monitor goes white until too late. by then the kernel has booted. [17:05] i'm hoping linaro finds a way to add framebuffer console support to u-boot some day [17:05] * ogra hates serial consoles with passion [17:06] ogra, yeah, this one requires the usual square pin header [17:06] ah, i'll have mine with me [17:10] * apw notes that * psurbhi is now known as csurbhi-afk [17:12] JFo, ogasawara https://wiki.ubuntu.com/Kernel/BugTriage/Responses === amitk is now known as amitk-afk [17:13] awesoem, thanks bj [17:13] sigh [17:13] bjf that is === hrw is now known as hrw|gone [17:13] I am not a keyboard cowboy today\ [17:13] see ^ [17:21] JFo, i just worked bug 494476 a bit [17:21] Launchpad bug 494476 in linux (Ubuntu) ""Smbd","kjournald2" and "rsync" blocked for more than 120 seconds while using ext4. (affects: 5) (heat: 32)" [Medium,Incomplete] https://launchpad.net/bugs/494476 [17:21] smb: can you refresh my memory...when sending a patch to stable, should I CC everyone who signed off on the patch or just CC the maintainer? [17:21] smb: I'm basically looking at upstream commit 68f194e027ecfbbc8d5515bc40787e542eed59e9 for bug 544740 [17:21] Launchpad bug 544740 in linux (Ubuntu Lucid) (and 1 other project) "fix for iSight cameras not being recognized (affects: 3) (heat: 20)" [Medium,Triaged] https://launchpad.net/bugs/544740 [17:21] that is an interesting bug bjf [17:22] smb: and I assume stable is still accepting patches for 2.6.32.y? [17:22] ogasawara, I usually cc all on sob [17:23] ogasawara, Yes, still open. Usually if it applies to all in stable it gets applied to all. Currently .32, .33 and .34 [17:23] Not sure how long .33 goes on [17:24] smb: cool. yah my main concern is .32 for Lucid [17:24] ogasawara, As it would be mine. :) [17:28] cnd, ping [17:34] apw: do we have a kernel 2.6.35 without maverick's patches in the mainline repository? [17:34] we have 2.6.35-rcN in there yes [17:35] I'm asking because I can't find any: http://kernel.ubuntu.com/~kernel-ppa/mainline/ [17:35] tseliot, look to be there to me [17:35] apw: I can see v2.6.35-rc5-maverick [17:35] thats the one yes [17:36] apw: but isn't that based on maverick's tree? [17:36] * smb sees a faq question coming up [17:36] yes, I know that mainline kernels are supposed to come from upstream [17:36] smb, its already in the faq [17:37] tseliot, that is the release from which the configuration came [17:37] apw, I know. I should have probably said sees the pointer to faw coming [17:37] oh, "Why do mainline kernel builds have a - suffix?" [17:37] heheh yeah [17:37] * manjo getting lunch will be back soon [17:37] my sight is not good when my blood pressure is low, sorry [17:38] tseliot, No worries. Being a bit silly which I attribute to the heat [17:39] it's really too hot here in Italy [17:39] Same here in Germany [17:40] tseliot, whats the temp today? is a nice 20c here [17:40] lucky you, it's more than 32° here... [17:40] and it's humid [17:41] apw, In the sun it seems to be near 40 here [17:41] I heard they have 40° in Venice... [17:41] But 34 is probably more realistic [17:41] * apw likes the .uk [17:42] * smb will ask again when apw is drowning in rain [17:42] apw: in what part of the UK? [17:42] * bjf notes it is currently 17 C here in portland [17:42] * ogra is envious [17:42] Portland - Oregon? [17:42] tseliot, yes [17:43] smb, indeed :) tseliot in london near wimbledon tennis [17:43] ah [17:44] is Portland as rainy as London (I've never been to London or to the UK) [17:44] ? [17:44] tseliot, we have had a *lot* of rain this last 12 months [17:45] if you want to see real rain go to bergen in norway [17:45] I noticed that when I visited Portland in January [17:45] they have umbrella vending machines on every corner [17:45] hehe [17:46] * tseliot reboots [17:46] * smb thinks he did enough damage for today and relocates somewhere closer to cool drinks [17:56] * jjohansen nees to run an errand for 30 min === jjohansen is now known as jjohansen-afk [17:57] JFo: I just noticed a small typo in the KernelBugListTop50.py script which I think is preventing the Won't Fix bugs from showing up under the Closed Bugs section on the web page [17:58] hmm, I hadn't even noticed [17:58] JFo: line 217, there's as bit to check bug_task.status == "Won't Fix " [17:58] ah the space [17:58] JFo: yep [17:59] JFo: I'd fix it myself, but I don't have permissions to commit it to the canonical-qa-tracking tree [17:59] k, no sweat [18:02] ogasawara, fixed [18:03] JFo: sweet, thanks [18:03] np [18:03] may take a bit for it to pull and run === jjohansen-afk is now known as jjohansen [18:26] bjf: just got confirmation that KSLM is pie in the sky vaporware atm [18:26] jjohansen, nice! [18:33] People who include the mouse cursor in screenshots should be killed [18:33] *glares at cking* [18:35] ogasawara, are you looking at bug#589123 [18:36] apw: I was just digging into that, but it seems it's dependent on addition config options [18:36] ogasawara, ok i'll move on [18:36] Keybuk, I sent a merge request for ureadahead. did I get it right this time? [18:36] tgardner: will look later [18:37] oh, no, it's right in front of me [18:37] yes, that looks right :p [18:37] ogasawara, so this top 50, i think we want to elide the closed bugs from the top table now don't we [18:38] Keybuk, how do I test it? I installed an updated package and rebooted, but the trace buffer size is still 1408. Can I exercize ureadahead without rebooting? [18:38] apw: I thought the original consensus was to keep them there, but it's an easy tweak to omit them [18:38] i th [18:38] tgardner: sure, just run ureadahead [18:38] ;) [18:38] w/ --force-trace etc. [18:39] apw: I prefer them not showing at the top as they're displayed at the bottom as closed anyways [18:39] ogasawara, it not clear quite how we can count the active ones if the closed ones are in the top [18:39] I think 1408 kB is the default [18:39] wing-commander scott% cat /sys/kernel/debug/tracing/buffer_size_kb [18:39] 7 (expanded: 1408) [18:39] no idea what that expanded stuff means [18:39] probably the minimum size ~1.5MB [18:40] arg [18:40] make install from my kernel tree *still* doesn't work in 10.04 [18:41] Keybuk, well, regardless of what the initial value should be, ureadahead appears to be restoring it. [18:42] cool [18:42] it should [18:43] it always used to, until I deleted that code ;-) [18:43] Keybuk, shall I upload it again for Lucid? [18:43] for lucid, I'll be uploading ureadahead2 soon enough [18:44] Keybuk, just to be clear, ureadahead2 is for Maverick only? [18:45] yes [18:50] jbarnes, did we break you ? [18:51] apw: yeah I think it worked briefly [18:51] but somehow /sbin/installkernel lost its mkinitramfs and update-grub calls [18:51] apw, debian commonization? [18:52] tgardner, not sure we even supply that file [18:52] nope its part of debianutils [18:52] oh, I thought it was part of post-init [18:53] tgardner, yep we do it there as well for our kernels [18:55] * tgardner is feeling stupid, must need lunch. [18:56] jbarnes, seems to be a direct sync from debian, so i guess they are borked too [18:58] yeah maybe, I haven't tried regular debian [18:58] maybe you should use the fedora bits :) [18:58] jbarnes, heh thanks [19:02] JFo: sent you email with a patch to the KernelBugListTop50.py script to omit showing the closed bugs at the top, since we already display them at the bottom [19:02] cool, thank you [19:03] JFo, so how is the bug 'hours' going ? [19:03] are we going to get stats like we do for normal bug days ? [19:03] with little up and down arrows ? [19:03] hmm, I didn't set that up for this, but I should get that going [19:03] I actually forgot all about it [19:04] haven't been doing it for the Bug Days either [19:04] * JFo fail [19:04] JFo, ogasawara, btw currently 'Won't Fix' is not a closed state ... which is is [19:04] apw: it's a closed state, should be fixed with the patch I just sent JFo [19:05] ogasawara, cool thanks [19:05] * apw has hit 5 at least ... in two hours ... hrmph === sconklin is now known as sconklin-lunch [19:05] JFo: I'd found one other place where there was an additional whitespace inserted [19:06] k [19:09] JFo, does that mean its too late to get the before numbers ? [19:10] apw, most likely [19:10] the only thing that could be possible... [19:10] one sec.. let me check something [19:11] JFo, it nice to be able to see if anyone bothered [19:17] JFo: it might be possible to extract the before numbers by looking at http://qa.ubuntu.com/reports/jfo/kernel-buglist-Top50-archive/kernel-buglist-2010-07-13.html [19:18] yep was just looking at that === sconklin-lunch is now known as sconklin [19:51] -> lunch [20:02] hello all [20:02] who's the right person to look into https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/554099 [20:02] Launchpad bug 554099 in linux (Ubuntu Maverick) (and 3 other projects) "[PATCH] Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken in 10.04 (affects: 45) (dups: 4) (heat: 274)" [High,Confirmed] [20:02]