[00:11] TheMuso, ack [00:26] ScottL: Ah I see why it was failing to build properly using an orig tarball and a diff.gz... abogani used symlinks, and a .diff.gz cannot represent symlinks. [00:46] ScottL: Ok a much improved low latency kernel now on revu. [01:13] TheMuso, outstanding! [01:13] i'll poke apw about it [01:14] ScottL: Hold up. I am going to push my changes to a git repo so he can look that over if need be. Give me a sec and I'll give you the URL for it. [01:14] okay :) [01:18] ScottL: Ok, I've pushed the current state of things to git://kernel.ubuntu.com/themuso/ubuntu-precise-lowlatency.git [01:20] afk for a bit [02:51] digging into the theme not settings, the lightdm not settings, and the xsession not settings thanks to len 's notes [17:20] i'm not sure what to do, i have ping apw (kernel UKT guy) several times about the lowlatency kernel, in particular to ask about an ETA for his check, and i've gotten no response [17:20] i really don't want to be dorky about this and make him mad by continuous pinging though [17:20] that is NOT a bridge i would like to burn [17:20] yeah... whats the timeline though? [17:22] i believe today is the feature freeze (although i could check that fact), which has been infered as the date we would need to get this done [17:22] of course, we could also file a FFe [17:22] extension? [17:22] tgardner says he will look at it though now :) [17:35] Feature freeze should be today within a few hours [17:35] Great work scott-work [17:36] ailo: thank you, but i really didn't do any _real_ work...basically it was been abogani and TheMuso [17:38] scott-work: Absolutely, but you will have done your bit to help get the kernel into the repo, which is where we need it. [17:38] agreed [20:23] scott-work: Anybody uploaded the kernel to precise yet? [20:24] scott-work: I only ask because Tim gave his ok on revu. [20:25] scott-work_: ping [20:25] TheMuso: ailo: sorry, been away doing stuff [20:26] TheMuso: i am not aware that anyone has uploaded it [20:26] TheMuso: would you like me to query a specific channel about the potential upload? [20:26] ailo: thank you for pinging me again [20:27] scott-work_: No, I don't think it would have been uploaded yet, so I will do it, and we will see how things go. I am confident it should be ok given Tim's review. [20:27] TheMuso: outstanding! [20:27] scott-work_: We only then need to get a meta package into the archive, but that shouldn't be difficult. [20:27] quite an exciting milestone for us [20:27] Indeed. [20:28] * TheMuso goes to push the button. [20:28] TheMuso: and update our seeds to include the kernel as well :) [20:28] * ailo stands ready with the champagne [20:28] TheMuso: you still need a second MOTU to review it [20:28] w00t! [20:29] micahg: Tim is a core-dev? [20:29] oh? [20:29] He didn't actually advocate on revu, but gave it a +1. [20:29] in comments. [20:30] * TheMuso checks to be sure. [20:30] yeah, he is [20:30] phew, saves me from doing it :) [20:31] Ok, will go ahead then. [20:33] abogani: Please pull from git://kernel.ubuntu.com/themuso/ubuntu-precise-lowlatency.git when you get a chance, there are some packaging changes in there that will be going into the upload to precise, and your tree is still the given tree in the Vcs-Git field. [20:34] abogani: Tim basically redid your tree, removed the quilt patch and made it a git commit. I also removed the symbolic links, as they prevented the package from being built with the upstream kernel.org tarball. [20:35] scott-work_: Longer term, I think we need to move the tree to somewhere where all three of us can colaborate on it. [20:35] scott-work_: I'm happy to do the packaging legwork if you guys maintain it. [20:37] TheMuso: do you mean in bzr or in a git repository? in the blueprint there was discussion about using git so we can easily rebase on kernel changes i believe [20:39] scott-work_: Yes git. You don't want to use bzr, and git means that you get all the commit history from the kernel team, and the upstrea kernel. [20:39] scott-work_: I was thinking we set up a team on gitorious or some such. [20:40] And, the kernel goes up with 20 minutes to spare. :p [20:55] lol [20:58] And the kernel is uploaded. [21:07] YAY! [21:07] thank you very much TheMuso and abogani for your work on this, it certainly would not have been possible without you! :-D [21:07] i need to update the blueprint as well :) [21:08] Cool. [21:08] That reminds me... [21:09] SO I take it the new kernel will show in tomorrows ISO? [21:11] len: not until we update the seeds and then update the metas [21:11] so this might be a week or so [21:11] BUT i can update the seeds for audacity and mudita during the same time [21:11] Not even then. It has to be approved in the new queue. [21:11] len: and thank you for your email for the lightdm stuff, i'm going to respond with details and i'm making the changes [21:11] We also need to upload the linux-lowlatency-meta package which abogani has in git, but that shouldn't be a problem getting in. [21:13] I am also looking at the jackd package. I am thinking we should be able to put a config file in the settings package that sets real time for jackd. [21:13] Actually it would tell the jack package we answered yes. [21:15] scott-work: I will email what I think would work. [21:16] The other area that needs looking at theme wise is the second panel. [21:17] It has a number of selections for programs that we don't ship. I can edit that file too to at least remove the stuff we don't have. [21:17] Personally, I would remove the second panel, but then I have a small screen. [21:29] scott-work_ ^^ [22:16] len: aye, as you noted previously, there are menu items that don't work as well (as with the panel) [22:16] i was choosing not to address this quite yet until we get a working live-dvd, ubiquity working, yadda, yadda [22:17] but also because i wanted to address the menu structure at the same time as these items, even though we will be touching the default-settings package again [23:15] wow!... thanks *so* much ScottL & TheMuso & micahg ...we have a kernel for RT! [23:42] Low latency anyway. [23:44] yup... it should work [23:44] our crack testing team indicates :) [23:44] It works with flying colors! [23:45] Every distro should have one! [23:46] Even better would be if the generic kernel was scalable somehow that you didn't need -lowlatency [23:46] i think we are close [23:47] i bet 14.04 doent need it [23:47] holstein: Don't bet on it [23:47] I mean, the code is already there [23:48] I don't know who controls whether a vanilla linux would be better or worse for realtime [23:48] But, as long as there is no interest for that to happen, it might only happen by chance [23:48] And in that case, it might work well for one linux version for example, but the next one not [23:49] we'll see [23:49] as long as we have our lowlatency one :) [23:50] It's not in anyway a natural direction for kernel development AFAIK [23:50] It might be. I'm just guessing [23:51] -lowlatency is pure gold