[01:37] i added a patch to the ardour mute bug # 581786 [02:36] persia: i received an email from luis today with a +1 [02:37] Cool. Sounds like you've collected the whole set, and win the prize :) [02:37] lol, yeah, a whole set of responsibilities ;) [02:40] however, i was also thinking of talking to #ubuntu-desktop tonight about the network-admin bug [02:40] if there anything in particular i should point out to them persia? [04:43] persia, TheMuso, jussi, i've almost finished my ubuntu membership application and I was wondering if you would be kind enough to write a testimonial for me [04:43] i should be done with it either tomorrow or the following night :) [04:44] lol, i see TheMuso is popular, he just got asked for an endorsement in -desktop as well [06:19] ScottL: well itd actually help if you linked us to your wiki page.... [09:48] kernels don't built in PPA! Sgrunt! [10:14] persia: ^ :-((((( [10:32] persia, ScottL : https://lists.ubuntu.com/archives/kernel-team/2010-May/010707.html [11:36] What! Why don't kernels build in a PPA? I thought apw did this regularly. [11:54] persia: I received this error: [11:55] http://paste.ubuntu.com/439296/ [11:58] persia: Moreover I don't think than apw really do it. [11:58] They release packages at http://kernel.ubuntu.com/~kernel-ppa/mainline/ (which it isn't launchpad). [11:58] I suppose that "ppa" should be removed for avoid confusion... [11:59] Perhaps kernel-ppa is the user who used for build kernels on Zinc (that is kernel.ubuntu.com)... [12:04] abogani: He really does it: https://launchpad.net/~apw [12:04] Hrm. Timeouts suck. Try uploading the regular kernel, and see if that makes a difference. [12:04] persia: Ok. Evidently their are some type of super powers. [12:04] I have a feeling that either there's a special hack in launchpad, or something else is wonky. [12:05] These are extendable :) [12:05] Just need to track down the cause, and then the folks in #launchpad can sort it. [12:05] persia: I have already done it: If I remove -pae images it build. [12:06] Interesting. [12:06] So it just takes too long? [12:06] persia: More than 10 hours. [12:06] On LP. [12:07] Obviously it build perfectly in two hours on my machine with pbuilder (variant=buildd) [12:07] Yeah, and it gets killed after 150 minutes. [12:07] Ask in #launchpad if there's something special for kernel builds that allows them to take longer. [12:07] if not, we can add a script that just prints something every 30 minutes or so to prevent the timeout. [12:10] persia: Asked. [12:11] persia: You mean an infinite loop with a sleep and an echo inside? [12:12] I'd probably not use an infinite loop. Make it exit after say 36 iterations (gives you 18 hours). [12:15] Sound really nasty trick [12:18] It's definitely in the deep workaround category :) Usually better to figure out why the build didn't print anything for 18 hours. [12:18] Most of the time there's some buildsystem flag that makes it more verbose, etc. [12:21] DH_VERBOSE? [12:21] persia: Full log at http://launchpadlibrarian.net/49048008/buildlog_ubuntu-lucid-i386.linux-lowlatency_2.6.32-22.38_FAILEDTOBUILD.txt.gz [12:22] DH_VERBOSE only helps for the debhelper bits. [12:23] You'd need something that made kernel-wedge copy-modules more verbose at the point where it appaers to hang for 150 minutes. [12:26] It could be very easy: place an "set -x" at top of the copy-modules should be work (and also add that file to the package changing also rules to point on this). [12:27] that's a lot cleaner than the while/sleep hack. [12:27] And probably more informative as to the cause of the underlying error. [12:27] But I'd recommend checking to see if wgrant has any other ideas before just uploading that :) [12:29] If he continue to consider me... [12:30] He knows more about the build system than the both of us combined. You might suggest the -x trick and see what he thinks. [12:30] Ok [12:30] he might have a different recomemndation, or want more time to think, or say "Go ahea and try". [12:37] jussi, here: https://wiki.ubuntu.com/ScottLavender [12:37] i originally was waiting to give the link until i completely finished it, but i cleaned up the bottom of it enough this morning though [12:37] thank you [12:38] Wow! [12:38] It seems very completed. [12:42] * abogani would want give thanks to all who correct his horrible English! Thanks! [12:50] ScottL: contributions to Ubuntu Studio *are* contributions to Ubuntu. [12:50] There's a reason we're part of a larger project :) [12:56] ScottL: I don't sit on the board that will review your application (wrong continent), but excepting the false distinction between contributions to Ubuntu Studio and contributions to Ubuntu, your application is one of the most complete and compelling I've ever seen. [12:57] * abogani agrees [13:00] but my opinion don't worth much [13:01] abogani: On the contrary. You're an Ubuntu Member, so your testimonial carries considerable weight with the approval boards. If you feel that way, please add a testimonial to ScottL's wiki page. [13:18] persia: For sure If someone review my English. :-) [13:24] ScottL, why don't you apply for MOTUship? [13:25] MOTUship? [13:28] abogani, to become ubuntu-developer [13:30] !motu [13:30] motu is short for Masters of the Universe. The brave souls who maintain the packages in the Universe section of Ubuntu. See http://wiki.ubuntu.com/MOTU [13:30] quadrispro: So perhaps it is a mentoring program? [13:31] abogani, there was a mentoring program, I think persia knows much more about it than me [13:35] persia: (re -preempt) I suppose than they meant "remove for main git tree". [13:39] abogani: I know, and you know, but I want them to know that :) [13:39] persia: :-) [13:39] lol [13:39] My fear is that they will decide they get to ignore it just because it's a different source package. [13:39] And then leave known bugs in it. [13:40] bye guys [13:40] I'm kinda against the mentoring program. [13:40] I used to be a mentor (one of my mentees is in the channel), but I think folks who want to be MOTU do better just qworking with other MOTU. [13:40] It is exactly what I expect from them. [13:41] persia: ^ [13:41] That said, MOTU is *not* the only way to become a developer these days. [13:41] quadrispro: Ciao! [13:41] abogani: That would be sad, really, but yes. [13:43] persia: I would want let you notice than I totally ignored in #launchpad (for build kernel in PPA) and in #ubuntu-kernel (for new kernel). What you would do in my shoes? [13:43] I don't think you were ignored in #launchpad. [13:43] I saw some traffic. [13:43] That nobody who was around had a good answer is a different matter. [13:44] At least two active Soyuz developers did talk to you about the issue. [13:45] I've also seen a fair bit of commentary about the new kernel in #ubuntu-kernel. If they folks there don't sponsor your upload, try pointing imbrandon at it (he said he was interested in that class of kernels) [13:48] persia: I _really_ more and more appreciate imbrandon help but .... [13:48] persia: Did you notice than kernel people have got a very big ego? If I bypass them I can incur in some problems in future... [13:49] Most of them can't upload anything at all. [13:49] Do you feel that the earlier discussion was sufficient that they expect a new kernel to be uploaded? [13:49] Do you really think they care how it gets uploaded, as long as you work with them on it otherwise? [13:53] :-( [13:53] What? [13:53] It may be because I'm a bit distracted, but I'm not understanding the issue. [13:58] The issue is than I don't know what is the right way to do this things. So I can't know how answer to your questions. [13:58] Simply I'm trying to do things in most reasonable way. [14:03] By the way, Anyone could review my English for Scott's application? [14:08] In my opinion, the right way is to do what it takes to get stuff done, trying to involve as many folks as possible for comment in the process. [14:08] And if anyone objects to anything, discuss it reasonably and get it fixed. [14:08] Especially at the beginning of a cycle, it's usually better to just do stuff and then fix it. [14:09] Things can be undone later, but once freezes begin to arrive, it's hard to do new stuff. [14:16] I agree with you but We should in two for "discuss". For example the last wgrant's suggestion was "abogani: You should prevent it from taking that long." It isn't seems a discussion to me. [14:17] scott-work: Dow you have a minute for me? [14:18] abogani: certainly :) [14:19] scott-work: Could you review English on my comment about your application? :-) [14:20] abogani: i am always happy to review your English on anything :) [14:22] scott-work: ;) [15:50] *sigh* [15:50] persia, i've attempted to talk to the #ubuntu-desktop people a few times about the network-admin bug and i'm not receiving much response [15:50] i'm going to look for someone to contact directly unless you have a better suggestion [17:09] scott-work: I'd recommend checking with the changelog owner for the changelog entry dropping the patch. [17:09] If they don't respond, just do it (as it indicates a lack of interest on their part) [17:09] i shall [17:10] If they object to just doing it, the discussion has started. As long as you're respectful from that point, the result should remain good. [18:29] persia: smb is volunteer to update linux-rt (in Lucid), apw is volunteer for review and find someone with upload rights for -lowlatency. [18:30] persia: At the moment miss only the right man for upload upgrades in Maverick. [18:30] persia: About -rt I meant. [18:32] persia: Tomorrow I'll try to request that to imbrandon. [18:32] The only other kernel uploaders are tgraner and ogarasawa [18:33] ogarasawa is busy in the role of primary uploader: I'm not sure she'll have time. [18:33] And tgraner is always too busy. [18:33] persia: I don't think to have chance with them. [18:33] I'd go with imbrandon, unless you expect someone will complain. [18:33] persia: I am too slow in typing... [18:33] :-) [18:34] Given that you're actively working with the security team, I doubt they will have any issues if someone else uploads, as long as it's a good upload. [18:34] And I'm fairly certain that by working with these folks, you can improve your developer application, and be able to upload directly in a couple months. [18:35] persia: At the moment I would want only let our users in a better situation (my application could wait). [18:37] I know. It's just awkward hunting sponsors in a narrow domain, because so many folks are afraid to upload kernels. [18:37] So things will be easier once that's also sorted. [18:41] I hope. [18:46] Indeed. We'll see.