[05:06] Anyone know off the top of your head head what sorts of stuff an hid driver should do before sending usb messages to tell the device to self calibrate? [07:10] morning all [07:41] 'ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored.' [07:41] does anyone know this error when 'fdr binary-xxx' [07:50] cooloney: I saw it too, but haven't nailed down the reason yet. Remove fakeroot from your command [07:54] amitk: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544471 [07:54] Debian bug 544471 in fakeroot "cap_sys_nice on executable leads to ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored" [Normal,Open] [08:01] amitk: i am goting to 'sudo su' and build the image without fakeroot now [08:02] cooloney: it's probably worth asking on #ubuntu-devel when rest of EU wakes up [08:02] amitk: https://bugs.launchpad.net/ubuntu/+source/libavg/+bug/474004, comment #15 [08:02] Launchpad bug 474004 in libavg (Debian) (and 1 other project) "Please sync libavg 1.0.1-1 from sid (affects: 2) (heat: 24)" [Unknown,Fix released] [08:30] Anybody familiar with git-bisecting the ubuntu kernel? I'm suspecting I keep producing the same .debs over and over again… [08:44] * apw yawns [08:47] * lag tells apw to put his hand over his mouth [08:50] heh [08:56] gah its sooo hot here already today [08:57] Yep. I may have to dig the fan out from the garage in the not too distant future === ogra_ is now known as ogra [11:29] commit 6f12efee9e86b52193aa2e7e14ad013fc3153a8a [11:29] Author: Douglas Gilbert [11:29] Date: Sun Jan 3 13:51:15 2010 -0500 [11:29] skip sense logging for some ATA PASS-THROUGH cdbs [11:30] lag, so its that one in the stable tree [11:30] just tell smb that that one is linked to your bug [11:30] git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.32.y.git [11:30] lag, that is the remote i added to get the stable branch into my lucid repo === amitk is now known as amitk-afk === pgraner-afk is now known as pgraner [12:23] ogasawara, i see the kernel-janitor moving things Fix Committed, is that your doing? === oubiwann is now known as oubiwann_ === amitk-afk is now known as amitk [12:58] * apw waves to pgraner [12:58] * pgraner gives apw a shout out [12:58] man its quiet out here today [12:58] it must be the hear [12:58] heat === oubiwann_ is now known as oubiwann [13:16] apw: public holiday in some regions AIUI [13:16] ahh yes in .eu some places, i'd forgotten thanks popey [13:30] ogasawara: When're you freezing for A1? [13:31] I expect it will be based on 2.6.35-rc1? [13:39] amitk, the kernel has to be in the archive by the 1st of June, so I'd guess either 28th or 31st at the very latest [13:39] i would not be supprised if -rc1 has not yet gotten in by then [13:39] or to put it a different way, i might recommend that we stick with .34 than ship A1 with 35-rc1 [13:39] as -rc1 is normally a crashy heap [13:40] * amitk agrees, just wanted to confirm [13:40] -omap mainline flavour is almost ready and I'd like it in A1 [13:43] amitk, and i can see no issue with you being .34 and master .35-rc1 either [13:43] oh one branch ... doh [13:43] so it has to be synced :) [13:43] you just add to the weight for .34 if yours is there and working :) [13:45] bug 584330 [13:45] Launchpad bug 584330 in linux (Ubuntu) "hid-gyration does not support GYR4101US remote (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/584330 [13:45] Am I within my limits to just okay this patch? [13:46] It looks harmless [13:46] yeah that looks like a simple addition of an ID, hard to have real regression potential [13:46] I am, as yet, unsure of my bounties [13:46] if its not had a test kernel done and published I would recommend you do that [13:46] boundaries [13:46] then get it on the kernel-team list ... looks sane to my eye [13:46] Will do [13:47] Cheers apw [13:47] apw: it boots with ogasawara's latest, needs some more cherry-picking to get all the goodness. But I think I could have something by tomorrow and then let mathieu/cooloney handle it from there.. [13:48] amitk, i assume this is planned to be pulled into master? [13:49] apw: yes [13:49] amitk, how big is the delta ? i assume much of it will go away as .35 formed ? [13:50] apw: a patch or two [13:51] and yes, I only intend to cherry-pick from mainline. This kernel should strictly be the mainline version of omap [13:52] amitk, better than we could have hoped [13:56] amitk, we should start the dialog about .34/.35-rc1 for A1 wtth ogasawara when she wakes up [13:58] apw: sure, I agree that it might be good for userspace folks if we stuck to 2.6.34 so they could start fixing up their stuff and we might even boot :) [14:07] it would be a rare thing that A1 boots for sure === JFo-swap is now known as JFo [14:18] How often is git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git updated? [14:18] that is live [14:18] that is _the_ master [14:22] ie. it updates instantly when it changes, and that is manual, when smb et al push [14:23] /nick sconklin === sconklin-gone is now known as sconklin [14:24] So daily? weekly? [14:25] How do I find out the difference between my local repo and the remote one? git diff master origin/master? [14:25] I'm guessing that will diff the HEADs [14:28] git log master..origin/master should give your all the new commits IFF the origin tree hasn't been rebased. [14:30] Thanks amitk [14:31] lag, ?? lag> So daily? weekly? [14:31] I think he was asking how frequently we push to the master repo [14:31] lag if its a bare repo, you only have 'remote things' [14:31] amitk: Correct [14:31] oh thats ust as needed [14:32] when there is change, when something is ready and becomes committed, that occurs by pushing [14:32] I'm looking for an average figure [14:32] before then its just an experiemnt in 'my' local repo [14:32] its completely arbitrary, for development likely every day [14:32] for a stable release likely not at all for weeks and then big batches of stuff pushed over a few days [14:33] i.e. If I do a git log master origin/master 5 days after my last fetch and nothing's changed, I should be worried? [14:33] when security is coming silence for a while then blammo a complete release is pushed [14:33] origin/master is a just a copy of the remote side when you last ran fetch [14:33] so it provides no information on upstream [14:34] That's true [14:34] its possible git remote show origin may tell you more [14:34] but i tend to just git fetch [14:34] Okay [14:34] I'll work the rest out :) [14:34] lag: as a working practice, if you add all the trees you care about as remote, then you can start your day with a 'git remote update' to see what changed [14:35] Now this is the stuff I need [14:35] * lag writes down new commands [14:36] * abogani just noticed than section_image parameter is totally ignored... [14:36] Oh, it doesn't list, it updates? [14:36] Is that like doing a fetch on all the branches? [14:37] lag: right [14:38] And then to see what we just fetched we do a? git status, or git diff? [14:39] just see the result of the command? It will print out stuff if things changed [14:39] Cool [14:40] you can then choose to merge the remote branches into your local ones, or rebase your work on top of them. [14:40] or reset? [14:41] yeah, sometimes that too :) [14:47] pgraner, I just wanted to mention that I have yet to see a self-review in my allhands page. [14:47] been looking since the e-mails came out [14:48] JFo: ack, lemme check with HR [14:48] k, thanks [14:49] apw, yeah, I wasn't sure how to break those items out on the bug handling BP [14:50] JFo, sorry had to reformat them to get them on the list at all [14:50] JFo: you are due for one and HR is investigating :-) [14:50] apw, no sweat [14:50] pgraner, cool [14:50] hope that it makes sense how i've done it [14:50] apw, it does [14:52] What's are the fundamental differences between 'fdr binary-generic' and 'fdr binary-arch'? [14:53] binary-generic only makes one flavour [14:53] and it doesn't make any ancillary things [14:53] like the per architecture linux-tools in later series [14:54] So, if I'm not building for server etc, I need to do generic? [15:02] generic is the common flavour for both i386 and amd64 [15:02] so not a bad base choice, cirtianly i build -generic for both of those for a test kernel, thats the 90% case [15:02] * apw lunches [15:14] moin all [15:14] bjf, gm [15:14] moin bjf, manjo [15:14] amitk, long time no hear buddy [15:14] just busy slacking off :) [15:14] heh [15:15] amitk, that can be quite time consuming [15:16] you bet, sometimes just doing the work is easier the pretending to [15:21] pgraner: ping [15:21] apw, ogasawara: do we want to try to pull in upstream multitouch changes for alpha 1, or would we rather just wait for them to be pulled when we update maverick to 2.6.35? [15:31] vanhoof: poing [15:31] pong even [15:41] moin bjf [15:41] moin big guy :-) [15:41] :) [15:44] JFo, you didn't get to a point where you'd made any changes to the test ISO scripts did you? that's what I'm going to work on first this week [15:46] no, I didn't change anything [15:46] so they are still as-is [15:48] cool [15:57] apw: can you look at bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/576601 [15:57] Launchpad bug 576601 in linux (Ubuntu) (and 1 other project) "[MacBookPro 7,1]mcp89 sata link reset fails, no disks detected (affects: 58) (heat: 334)" [High,Triaged] [15:57] pgraner, whos complaining about that one now [15:57] never ever ever buy a new macbook, period. [15:57] apw: all the new mac book users [15:58] pgraner, so probabally about 10 people, is it really the highest priority bug we have? [15:59] apw: no, basically make sure its liked to upstream and have someone watch it in case a patch shows in the .35 window [16:00] pgraner, i have produced some test kernels in the past which popey ean for me [16:00] yeah it is already upstream [16:00] * popey wakes up [16:00] apw: yah I have a lp script to mark bugs fix committed as I pull patches in. I should update my credentials to not be the janitor. [16:00] amitk: I'm freezing for A1 on Friday [16:01] amitk: you mentioned you might have something by tomorrow? [16:01] ogasawara, i quite like it i wonder if it should be the norm :) [16:01] apw: cool, I'll leave it as it is then. [16:02] ogasawara, we were wondering about whether we should not go to 35-rc1 should it appear before then, as -rc1 are notorious crack [16:02] cnd: will the multitouch changes you're wanting going to land in 2.6.35-rc1? [16:03] so that A1 has a higher chance of booting [16:03] apw: yah, I'd be worried about rc-1 not booting if I rebased right before A1 [16:03] ogasawara: I would guess so [16:03] ogasawara: I might have the -omap flavour done by tomorrow [16:03] ogasawara: let me see if it's been merged already... [16:03] ogasawara, obviously its your call, not sure when -rc1 might drop anyhow [16:04] apw: I'm leaning towards not going with 2.6.35-rc1 even if it lands in time to rebase [16:05] when will we start producing daily live images for maverick? will that be alpha-1? [16:05] ogasawara: all the MT stuff that's in Jiri Kosina's HID tree have been merged into 2.6.35 [16:05] "we" as in canonical [16:06] ogasawara: however, they aren't earth shatteringly awesome, so they can probably wait until you merge -rc1 [16:06] cnd: ack [16:08] apw, thanks for running the irc meeting [16:08] bjf, no worries. i also wrote up a howto for running the meeting which you might be the right person to read over and correct [16:09] apw, you didn't read my email to you? i already had a wiki page written up on how to run the meeting [16:09] ahh bottom [16:09] https://wiki.ubuntu.com/KernelTeam/RunningTheIRCMeeting [16:09] apw ^ [16:11] bjf, mine is basically the same ... so please do zap it and point the link to yours [16:11] apw, ack [16:12] JFo, regression meeting yes/no ? [16:12] i note the email addresses arn't quite what you actually send to, you send it to ubuntu-devel and to kernel-team i think [16:12] apw, will review that [16:12] manjo, yes and no, we will be discussing possible changes to said meeting [16:12] JFo, sounds good, when ? [16:13] JFo, 12cdt ? [16:13] little under an hour [16:13] apw, i think i switched to ubuntu-platform because my email to ubuntu-devel gets moderated [16:13] * manjo bleeping google calender [16:13] though ubuntu-platform is an internal list [16:13] yeah [16:13] apw, ah [16:13] JFo, so 16:00 UTC ? [16:14] JFo, my bleeping google calendar says its 2hrs from now [16:14] sounds about right [16:14] manjo, mine could be wrong [16:14] but I don't think it is [16:14] why can't google have UTC calendar [16:14] manjo, it does [16:14] you just need to set it into that correctly, the entire calendar [16:15] msg chanserv op #ubuntu-kernel [16:15] need a slash :) [16:15] <-captain obvious [16:15] apw, I see only GMT in my settings [16:15] manjo, that is UTC within a few microseconds === bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/KernelTeam/ || Lucid Kernel Version: 2.6.32 || Ubuntu Kernel Team Meeting - May-25 - 17:00 UTC [16:16] note GMT does not change in the summer, in the UK we move between GMT and BST (british summer time) [16:19] JFo: apologies if you've already answered this, but is there a regression review meeting today? [16:19] cnd, there is [16:19] we are discussing the changes in the meeting [16:19] ok [16:20] in a little over 40 minutes [16:20] JFo: where are we holding the meeting? (mumble, skype)? [16:20] * apw votes for mumble, jfo you can make a new meeting room [16:20] mumble shoud be fine [16:20] and infact you already have one [16:20] :-D [16:21] * JFo is ahead of the curve [16:21] \o/ [16:34] manjo: did the fix for PowerDVD land in an SRU kernel for karmic? [16:34] manjo: i.e. the ironlake buffering issue [16:34] awe, yes that fix is already in karic [16:34] not sure what iron lake is [16:34] could you point me at the commit and/or kernel tag? [16:34] manjo: code name for arrandale integrated graphics [16:35] aka i915 [16:35] awe, karmic commit id is commit 78781dd5db00147ba99bb72eab1e6257b042aec8 [16:35] ubuntu!!! [16:36] crocket, yeeayy! [16:36] When I boot 2.6.32 lucid with KMS on, linux dies right after KMS turns on. [16:36] manjo, thanks!! [16:36] It happens even under recovery mode with KMS on. [16:37] I have to put "nomodeset" in every grub entry. [16:37] My graphic card is ATI Mobility X1250. [16:37] mpoirier: 2.6.34-based omap3 kernel - display and usb works, nand driver broken, but xubuntu works fine. Find it here -> http://people.canonical.com/~amitk/ti/ [16:37] With nomodeset, ubuntu lucid is better than 9.10 [16:37] mpoirier: I'll submit it for upload [16:39] mpoirier: 2.6.34-based omap3 kernel - display and usb works, nand driver broken, but xubuntu works fine. Find it here -> http://people.canonical.com/~amitk/ti/ [16:39] crocket, yeah some of the older radeon cards have had isses [16:39] crocket, kms+compiz support might be flakey on some of the older radeons [16:40] manjo, 3D games run perfectly fine in windows. I think linux needs much more driver supports than now. [16:41] I can even run halo 2 in windows vista. [16:41] manjo, compiz works fine while KMS kills linux. [16:42] crocket, sure drivers need more work [16:42] manjo, do you mean I have to buy a new laptop or a new desktop for that? [16:42] Can I put a new graphic card in my laptop? [16:43] KMS is the only pain in my ass. [16:45] The maverick kernel (2.6.35) is planned to include a lot of improvements to the ati drivers. Should be fixed then. For now, it's not really that hard to add "nomodeset" to /etc/default/grub. [16:46] stenten : I'm sad [16:48] manjo: ping [16:48] awe, pong [16:48] don't think the referenced bug fixes the issue we saw with powerdvd [16:49] we were testing with the -18.55 kernel [16:49] looks like this commit was much earlier, so should've been included in -18.55 [16:49] unless of course the commits for i915 that landed in -18.55 backed this out [16:50] awe, crap. ok I will take a closer look, but you see the two bugs and they have the exact same errors in dmesg === andreas_ is now known as anoteng === rsalveti_ is now known as rsalveti [16:52] Until 2.6.32-22, KMS used to kill linux. [16:52] With linux 2.6.34-020634-generic, KMS doesn't kill linux but doesn't work anyway. [16:52] I just see a distorted screen before I see a login screen. [16:53] I should have seen plymouth [16:54] Would KMS work on 2.6.35? [16:54] I doubt it [16:54] manjo: don't bother... the heat has been lowered on this one, as things work fine in lucid [16:54] It's just 0.0.01 version upgrade. [16:54] awe, there was a massive backport of s**t from 33 to karmic to fix a lot of these video related problems... [16:55] Anybody familiar with git-bisecting the ubuntu kernel? I suspect I keep producing the same .debs over and over again. Anybody care to take a look at my commands and check if I'm doing something stupid? http://ubuntu.pastebin.com/Rfif04jx [16:57] manjo, When do I need to use a graphic card sold since? [16:57] manjo: understood... as I mentioned though, no need to dig any deeper. [16:57] thanks for your help [16:57] Oops, it is a weird sentence. [16:58] I don't know how to express it better [16:59] crocket, can you try the mainline kernel build? http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ [17:00] manjo, Is it newer than 2.6.34-020634-generic? [17:00] crocket, that is the latest mainline kernel ... and see if that kernel works for you, if it does then 10.10 might have those patches [17:00] right it is the latest upstream kernel packaged for ubuntu [17:01] manjo, do you know a good download manager? FlashGot + cURL are awkward. [17:01] wget ? [17:01] It is also a CLI. [17:01] I want a GUI application that downloads flash videos easily so that I can use it with FlashGot. [17:02] crocket, that is question for #ubuntu channel [17:02] Gwget and downloader for X hide in traybar readily. [17:02] ok [17:02] Jesus I have 4 kernels in my system === gnomefreak76 is now known as gnomefreak [17:05] manjo, mine is amd64 ubuntu [17:06] crocket, amd64 is generic name for x64 [17:06] crocket, we follow debian naming convention [17:06] ubuntu surpassed debian, though. [17:06] However debian still presents more control. [17:06] its just legacy naming convention [17:09] dpkg -i is more convenient than ubuntu GUI package installer when installing more than 2 packages at once. [17:15] manjo, KMS looks in 2.6.24-999, but linux doesn't die. [17:15] oops [17:16] KMS looks worse in 2.6.24-999 than in 2.6.24-020634 [17:16] It means I still need UMS and uvesafb [17:17] I specified video=1024x768-24 in grub. [17:17] Should I omit it and try again? [17:21] manjo!!! [17:21] manjo, KMS worked briefly after I omitted "video=1024x768" option from grub entry. [17:21] How can I change the resolution of KMS? [17:22] plymouth showed for a second on 2.6.34-999. [17:22] I should try on 2.6.34-020634, too. [17:24] manjo, plymouth also showed for a second on 2.6.34-020634 [17:25] manjo, are you there? [17:34] crocket, this is with the lucid kernel ? [17:35] crocket: KMS doesn't work on RS600 in lucid, it'll work once 2.6.33.3 or higher drm is merged soon though [17:35] https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/544590 [17:35] Launchpad bug 544590 in linux (Ubuntu Lucid) (and 1 other project) "[RS600] video freeze with KMS (X and plymouth) (upstream patches available) (affects: 3) (dups: 1) (heat: 32)" [High,Triaged] [17:36] i'm guessing you have a dell latitude XT since thats the only machine i've seen that chipset on, AMD pulled it from the market after the merger [17:44] ogasawara: apw: omap flavour pull request sent [17:45] mpoirier: ^ [17:45] hmm === amitk is now known as amitk-afk [17:46] amitk-afk: thanks [17:48] How can I make KMS appear early? [17:48] I included "radeon" in /etc/initramfs-tools/modules, but I just see my monitor disconnected from computer for a while. [17:49] echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash then sudo update-initramfs -u [17:49] did you see what I said right before you left? [17:49] Sarvatt : no [17:49] crocket: KMS doesn't work on RS600 in lucid, it'll work once 2.6.33.3 or higher drm is merged soon though [17:49] https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/544590 [17:49] Launchpad bug 544590 in linux (Ubuntu Lucid) (and 1 other project) "[RS600] video freeze with KMS (X and plymouth) (upstream patches available) (affects: 3) (dups: 1) (heat: 32)" [High,Triaged] [17:49] i'm guessing you have a dell latitude XT since thats the only machine i've seen that chipset on, AMD pulled it from the market after the merger [17:50] Sarvatt, I use 2.6.34-999 and -020634 [17:50] well I'm just saying why the stock lucid kernel doesn't work :) [17:50] Sarvatt, I installed linux 2.6.34-999 recently. [17:51] Sarvatt, It's sudo update-initramfs -u -k all [17:52] without -k all, initrd only for the most recent kernel is updated. === oubiwann is now known as oubiwann_ === oubiwann_ is now known as oubiwann === kamal-away is now known as kamal [18:51] kernel 2.6.34-999 has a bug. [18:51] During installation of 2.6.34-999, I see this message http://www.pastebin.org/275287. [18:51] ***Kernel/Tagging has been updated*** [18:52] 2.6.34-020634 doesn't have that weird messages [18:52] JFo : what? [18:52] that wasn't for you crocket :) === amitk-afk is now known as amitk [19:06] mpoirier: yes, that is the request (omap-mainline for maverick) that I sent to the ML [19:06] feel free to test it out and comment [19:07] humm... [19:07] what did you do exactly ? [19:07] the same as me ? [19:07] the rebase I mean. [19:07] mpoirier: no, I took leann's tree and simply enabled the omap3 config [19:08] we needed it ASAP [19:08] ok [19:08] Do you have HW now? [19:08] i have a beableboard here next to my computer. [19:09] cool, so I'll move over some lucid bugs for you to look at :) [19:09] but hold on... [19:10] I understand that leann's tree (maverick) is now enabled on beableboard after your intervention. [19:10] correct ? [19:10] correct, it will be after leann pulls my patches [19:10] ok... [19:10] So you started with Leann's tree correct ? [19:10] yes [19:11] interesting. [19:11] I rebased against linus' tree [19:12] I was lead to beleive ARM was not in Leann's tree. [19:12] Once done, I was going to rebase with Leann's to get the latest and greatest changes for Maverick. [19:13] errm, what do you mean by "ARM was not in Leann's tree" [19:14] I must have misunderstood something somewhere. [19:14] I has a chat with apw [19:15] mpoirier: perhaps the variety of topic branches? [19:15] He suggested that I rebase ti-omap againts Leann's. [19:15] mpoirier: some are is in leann's tree not all [19:16] again, there must have been a misunderstanding somewhere. [19:16] mpoirier: nevermind, it was still a good exercise to get familiar with the process (kernel compile, abi, etc.) and the tools (git, etc.). And you are going to maintain this going forward. :) [19:16] well,, [19:17] I'll probably scrap what I have and rebase ti-omap against Leann's. [19:17] as an excercise. [19:17] I will then compare my work with yours. [19:18] unless you have something urgent for me to address. [19:18] probably not worth it at this point, your time will be better spent making it work well. ATM, there is some flakiness in our USB support [19:18] ATM ? [19:18] at-the-moment [19:18] ok. [19:19] is the flakiness in Ubuntu code or community ? [19:19] our configs [19:19] + possibly upstream code (not sure) [19:19] I assume you have bugs for this ? [19:19] Just grab the kernel from my people page, and run it on your beagleboard [19:20] mpoirier: https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap [19:20] that shouldn't take long. [19:20] then what ? [19:20] mpoirier: feel free to assign to yourself whichever ones you like [19:20] ok, i get it. [19:21] one more thing. [19:21] davidm is sending me some gumsticks ? [19:21] are you aware of this ? [19:22] no, but good. That way you'll have more that one omap3 platform to test the kernel on [19:22] ok, sounds good. [19:22] there are lots of people on #ubuntu-arm that want support for various omap3-based boards [19:23] it might be worth it to see if we can help mainline some of those patches and get better board support [19:24] ok [19:25] I switched to private channel - did you get it ? === bjarkef is now known as thefakebjarkef === thefakebjarkef is now known as bjarkef [19:43] Hi [19:44] linux 2.6.34 apparently tries to acquire EDID from a monitor that doesn't exist. [19:44] http://pastebin.org/275497 [19:44] Read this [19:47] crocket: irc is not good for bug reporting. [19:47] where do I report it? [19:47] launchpad if it is an ubuntu bug [19:47] upstream if you use vanilla bugzilla.kernel.org [19:48] It's 2.6.34-020634 [19:49] It's linux kernel [19:49] whatever this is a dev channel for support go to -> #ubuntu [20:02] bdmurray: can you point us to your bug gravity web pages? [20:12] ogasawara: I stopped running it since bug heat was rather close. Are you looking for the linux one specifically or something else? [20:13] bdmurray: we were interested in the linux ones, but we thought you had calculated gravity a bit differently than the bug heat. [20:14] ogasawara: some points were assigned based on the reporter for gravity and are not for bug heat [20:15] apw, JFo, cnd, manjo: ^^ [20:15] hmmm, I think that is useful [20:16] Oh and actually bug tags too aren't used by launchpad [20:16]