=== noy_ is now known as noy === doko_ is now known as doko === Daviey is now known as Da === Da is now known as Daviey === chuck_ is now known as zul === pgraner is now known as pgraner-afk === pgraner-afk is now known as pgraner === DBOut is now known as DBO [16:00] plop [16:00] o/ [16:02] ##startmeeting [16:02] #startmeeting [16:02] Meeting started at 10:02. The chair is NCommander. [16:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:02] I'm lagging hidiously [16:02] NCommander, did someone tell infinity ? [16:02] [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2011/20110609 [16:02] LINK received: https://wiki.ubuntu.com/MobileTeam/Meeting/2011/20110609 [16:03] [topic] Action Item Review [16:03] New Topic: Action Item Review [16:03] [topic] ogra to trim down desktop seed on ARM [16:03] New Topic: ogra to trim down desktop seed on ARM [16:03] infinity !!! welcome to the team !!! (officially now) [16:03] NCommander, sigh, c/o [16:03] It wasn't official before? [16:04] working on it right now [16:04] infinity, we didnt tell the community yet :) [16:04] [topic] * ogra to follow up with Linaro on binutils segfault [16:04] New Topic: * ogra to follow up with Linaro on binutils segfault [16:04] co as well [16:04] (yes i suck) [16:04] * janimo got internet connection fixed just in time for meeting [16:04] [topic] Standing Items [16:04] New Topic: Standing Items [16:04] * GrueMaster refrains from comment. [16:04] [link] http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel.html [16:04] LINK received: http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel.html [16:05] [link] http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel-oneiric-alpha-2.html [16:05] LINK received: http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel-oneiric-alpha-2.html [16:05] * NCommander just closed three work items today [16:05] some powerful cdimage dev please review my SD alignment branch kthxby [16:06] NCommander, can you please get the doc spec approved so i can finally reset the trendline ? [16:06] [action] NCommander/ogra to review janimo SD alignment branch [16:06] ACTION received: NCommander/ogra to review janimo SD alignment branch [16:06] i think we both did, no ? [16:06] ogra_: davidm on VAC so I don't know who can set it [16:06] I haven't had time to review [16:06] i said its fine to merge [16:06] [action] NCommander to get Documentation spec merged [16:06] ACTION received: NCommander to get Documentation spec merged [16:06] NCommander, once again ... slangasek owns that spec [16:06] ;) [16:06] ogra_: er, no, I do. [16:06] approver ... [16:06] k [16:07] not david [16:07] i just want to get the tracjker stuff done [16:07] anyway, netboot images are on track to be implemented next week (mostly) I hope [16:07] ogra_: how are we towards starting to build server images on OMAP? [16:08] well, the rest of my week will be dedicated to the PPA clusetr initrd scripts ... for the headless server image infinity took over the pool spec [16:09] apart from that we only need some preseeding [16:09] Is any other server-image-related stuff basically blocking on that? [16:09] could we please have a server topic instead ? [16:09] doesnt really seem appropriate for WI review [16:10] infinity, no, only the perinstalled headless images [16:10] *pre [16:10] [topic] ARM Server Status (NCommander, Daviey) [16:10] Either way, quick hack for pool stuff should land soon, and then I'll work later on a less hackish live-build implementation, so we transition smoothly when that switch happens. [16:10] New Topic: ARM Server Status (NCommander, Daviey) [16:10] There :-) [16:10] awesome ! [16:11] * ogra_ doesnt have anything else for server atm :) [16:11] [topic] Kernel Status (cooloney, rsalveti, ppisati) [16:11] New Topic: Kernel Status (cooloney, rsalveti, ppisati) [16:12] I'm sorry, I'm lagging badly today [16:12] again nothing new except for a load of CVE fixes [16:12] and a couple of config changes [16:12] one related to lxc on omap4 [16:12] and another one about a kernel panic on imx51 [16:12] * ogra_ hasnt uploaded the ac100 kernel to oneiric yet ... just FTR [16:12] btw, i saw a patch flying around that would fix one of the memory pressure problem we have on omap4 [16:13] ppisati: what problem exactly? [16:13] ah yes, and the usb omap3 problem perhaps is a toolchain issue (but i haven't investigated yet) [16:14] rsalveti: i saw a patch from... hold on... [16:14] if you have the link, even better [16:14] https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/690370 [16:15] Ubuntu bug 690370 in linux-ti-omap4 (Ubuntu) "Strange out of memory on pandaboard" [Undecided,New] [16:15] Ming Lei [16:15] hm, ok, would be good to try and also publish it at l-o [16:16] yep [16:16] as he's touching the usbnet code, not just the smsc one [16:16] btwm do we have an ETA for .39 omap4? [16:17] we had no call last week [16:17] yep [16:17] lets ask tomorrow [16:17] oooooook [16:18] can I move on? [16:19] yes [16:19] try it :) [16:19] [topic] ARM Porting/FTBFS status (NCommander, janimo) [16:19] New Topic: ARM Porting/FTBFS status (NCommander, janimo) [16:19] no progress on my side [16:19] BP work [16:20] I'm no expert in build failures, but when I'm taking sanity breaks from specs, I could have a look. [16:20] (Note: the opening statement was ironic sarcasm) [16:20] upstart really needs someones attention i think [16:20] FTBFS are not good for sanity either [16:20] infinity, http://qa.ubuntuwire.org/ftbfs/ [16:20] * janimo plans to check GL/Qt type FTBFSes [16:21] janimo: They were my life for almost a decade. Explains a lot about me, doesn't it? [16:21] only 7 armel only packages in main [16:21] that fail [16:21] infinity, I also like it sometimes but when the same bugs keep recurring it can get disappointing [16:21] telepathy-glib will get in our way at some point [16:22] and dbus too [16:22] ogra_: I'm happy to look at tp-glib, I'm an upstream committer. [16:22] isn;t that also a ld segfault one? [16:22] I think some of these are blocked on ld being borken in some way, so many test cases fail [16:22] ogra_: Err, unless it's a toolchain issue we're waiting on. :P [16:22] yes, that was the original cause for the shrink warp stuff in natty [16:22] but i thought the gcc change was supposed to fix it [16:22] if it were contained to upstream packages fixes would be nice and actually fulfilling as you'd send patches upstream [16:23] * ogra_ doesnt really get why it returned [16:23] janimo: No workarounds for the ld segv (like, is it choking on specific output from gcc, or literally everything?) [16:23] when is's a ld gcc regression it is painful [16:23] infinity, did not investigage further [16:23] Kay. [16:23] chromium is affected too [16:23] the workaround was -O0 [16:23] for telepathy-glib specifically [16:23] ogra_, this may be something else though [16:24] it solved the linker issue [16:24] more packagesa are affected an I don;t think shrinkwrap was reenabled [16:24] Well, if it's not a 100% segv, changing optimisation will often fix your issue, yes. [16:24] Cause it's choking on (probably) bad output from gcc. [16:24] yep [16:24] well, telepathy-glib, dbus, libnih and upstart are critical on the list [16:24] Granted, I'd give large bags of money to fix the segfaults in binutils so it can usefully error on bad input intead of exploding. [16:25] so anyone who feels like it, please pick one of these four first :) [16:25] Well, I may be panda-fied sometime today. If so, I'll happy to locally grind and get workarounds uploaded until the toolchain's fixed. [16:26] s/I'll happy/I'll be happy/ [16:26] note that the desktop team will drop the telepathy fix next release again [16:27] They don't believe in merges? [16:27] Or just to keep us on our toes? :P [16:27] until we have a proper upstream fix [16:27] I can just push the fix upstream instead. *cough* [16:27] Anyhow. [16:27] iirc we -O0'ed that package twice already [16:27] We'll see if I find a fix first. [16:28] NCommander, move ? [16:29] * ogra_ jumps up and down waving an NCommander flag [16:30] [topic] ARM Image Status (ogra, NCommander) [16:30] New Topic: ARM Image Status (ogra, NCommander) [16:30] * NCommander kicks the nternet [16:30] well, i just started a testbuild with the desktop seed [16:30] if that survives (which it seems to unless antimony hangs) i'll change the crontab entries [16:31] yay [16:31] so we should have desktop images from tomorrow on ... what we need to do is to go through the set of installed packages and see what we want to keep on armel [16:31] netboot images should exist today, though they'll probably be another week or so before they'll work on omap4 [16:32] i.e. do we want to have evo etc [16:32] (or TB, since i think there was a decision to switch) [16:33] We should match the desktop image. [16:33] ac100 images seem to work for everybody but NCommander and GrueMaster ... i still try to find the reason for that before adding it to oneiric [16:33] Unless we continue to use arm specifics. Which means webmail. [16:33] GrueMaster, so you want to test heavyweight mail clients ? [16:34] we can use overrides in the seed file [16:34] so we can make our pick if we want to go with the x86 one or want to replace packages [16:34] What I'm saying is that the current armel images use web apps for email & office. [16:34] yes [16:34] And if we move from that, we should use what everyone else is using. [16:34] we need to make a decision if we want to keep it that way or not [16:34] For our own sanity. :P [16:35] but that should be decided with david available :) [16:35] So c/o. [16:35] for now i'll build what we get [16:35] without touching the seeds [16:35] * ogra_ has nothing else [16:36] [topic] QA Status (GrueMaster) [16:36] New Topic: QA Status (GrueMaster) [16:36] Trying to get filesystem benchmarks running. So far phoronix-test-suite has been running filesystem tests on one panda w/ 16G class 10 since Tuesday. [16:37] Very slow. [16:37] what fs are you testing there atm ? [16:37] Baseline. [16:37] baseline ? [16:37] I am running the natty image to establish a baseline. [16:38] ah [16:38] so ext2 updated ... [16:38] Ext3, [16:38] its ext2 updated with tune2fs [16:38] Next will be backup/reformat/restore. [16:39] Well, the only difference between ext2 & ext3 is the added journal. [16:39] nope [16:39] actually it's not a surprise, arnd bergmann ha d a couple of talks @ UDS about what linux do right WRT to flash: almost nothing [16:39] there is versioning etc in the signature it doesnt get recognized the same [16:39] it's more than jyst the filesystem [16:39] yes [16:39] we should switch to ext4 soon [16:39] we had his talks at the last rally too :) [16:40] http://lwn.net/Articles/428584/ [16:40] LINK received: http://lwn.net/Articles/428584/ [16:40] Fedora announced that hey are switching to btrfs. [16:40] he spent a lot of time in the arm room :) [16:40] ah ok, then nevermind [16:40] GrueMaster, yeah, lol [16:41] Having issues with today's netbook image. oem-config seems to crash before removing packages. [16:41] On second attempt now. Still fails. [16:41] bugs :) [16:41] Testing will be severely limited next week while I am in London. [16:41] what do you mean by "todays" btw [16:42] 20110609. [16:42] i think the last two builds failed [16:42] hmm [16:42] oh, that was yesterday [16:42] nevermind [16:43] AC100 is currently hosed. No proper backup to revert to. [16:43] Have been unsuccessful in recovery efforts. [16:44] hmpf [16:44] what model was that ? [16:44] And without published images from the manufacturer, it will be hard to fix. [16:44] 10Z [16:45] k [16:45] If there are still units in London, I will try to recover next week while I am there. [16:46] I thought there was a master recovery from tobisha [16:46] that sounds like a plan [16:46] NCommander, there isnt [16:46] there is exactly *nothing* from toshiba for the ac100 [16:46] There is, but our image appears to have blasted it. [16:46] It is on a separate partition. [16:46] the image doesnt touch recovery [16:46] Hold home while powering up. [16:47] you blasted it with your android upgrade [16:47] Well, then that is on Toshiba. [16:47] the 2.2 android doesnt use the backup partition at all anymore [16:47] anyway, lets talk after the meeting [16:47] I have nothing else. [16:48] [topic] AOB [16:48] New Topic: AOB [16:49] * ogra_ has nothing [16:50] ok, then closing the meeting in 3 [16:50] 2 [16:50] 1 [16:50] #endmeeting [16:50] Meeting finished at 10:50. === ogasawara_ is now known as ogasawara === dholbach_ is now known as dholbach [17:59] hello [17:59] hello pedro_ [17:59] hello everybody [17:59] :) [17:59] hola njin :-) [18:00] ok time for the meeting [18:00] #startmeeting [18:00] Meeting started at 12:00. The chair is pedro_. [18:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [18:00] * charlie-tca waves, late again [18:00] As always the agenda is at : https://wiki.ubuntu.com/BugSquad/Meeting [18:01] [TOPIC] Updates of action items from previous meeting [18:01] New Topic: Updates of action items from previous meeting [18:01] hggdh, you around? :-) [18:01] first item there is yours [18:01] yes [18:01] darn, still pending, will do now [18:02] and announce the others [18:02] ok so i'll leave it for the next meeting [18:02] please [18:02] other action items: [18:02] bdmurray to draft a spec regarding criteria for (team) membership in ubuntu bug control: DONE [18:02] bdmurray to email bug control about spec regarding bug control membership: DONE [18:02] bdmurray to subscribe ScottK to said specification: DONE [18:03] eeek [18:03] also pending [18:03] so check your email because bdmurray sent a few emails regarding that [18:03] he's not here today though, if you have comments please reply to those emails or ping him trough IRC [18:03] * hggdh is already at the end of the list, so the above is preempting pedro_ 's question [18:03] hggdh, your last item you mean? [18:03] yes [18:03] hggdh to review all bug workflows that result with an "Invalid" status and see if using "Incomplete" makes more sense and email bugsquad regarding results <- that one [18:04] yes [18:04] ok will leave it as open too [18:04] any other pending item from last meeting? [18:05] seems not ok lets go for the next on the agenda [18:05] [TOPIC] Mentorship program discussion [18:05] New Topic: Mentorship program discussion [18:06] the item there : Make sure folks are aware that vish isn't the only Admin. [18:06] o/ [18:06] vish, please go ahead [18:06] hey.. so regarding the mentoring team, not many seem aware that there are other admins in for that apart from me :) [18:07] like every mentor there is an admin.. [18:07] and I'm not sure how i became the main admin either :p [18:07] Sense started that team and when he left he just made me admin [18:08] * charlie-tca thinks vish is very good as the main admin [18:08] [he dint ask me either.. ;) ] [18:08] charlie-tca, oh yes he's doing an excellent work [18:08] vish, do you want to send a reminder with that to the list? [18:08] so the others mentors/admins can see it [18:09] and list *all* other admins [18:09] yea, i dont mind helping it.. but somehow people seem to think I'm the driving force, it just happens that I'm a good work horse :p [18:09] and also the new folks who want to join our mentorship program [18:09] hggdh, that's actually a good idea :-P [18:09] I didn't even realize all mentors in the group were also admin [18:09] sure, i can take that as an action item.. :) [18:09] pedro_: ^ [18:10] pedro_: ^ for the action item [18:10] [ACTION] vish to send an email to the lists re mentoring team admins [18:10] ACTION received: vish to send an email to the lists re mentoring team admins [18:10] done [18:10] vish, anything else on that topic? [18:10] thx :) [18:10] any question from anybody? [18:10] nope.. :) [18:11] pedro_: i answered for everyone; noone is allowed to ask questions ;p [18:11] ok, thanks vish :-) [18:11] heh [18:12] [TOPIC] New bug control members [18:12] New Topic: New bug control members [18:12] * charlie-tca thinks that's why vish is THE admin, too [18:12] I see that Bjoern Michaelsen is a new member, welcome aboard! [18:13] and also the canonical-hw-cert [18:13] Yay! [18:13] which plenty of members, that are rocking in the Bug Days [18:13] s/which/with [18:13] brendand and roadmr are doing an *excellent* work [18:13] RedSingularity is also a new member ? :-) [18:14] if we didn't said welcome last time, welcome abord RedSingularity! [18:14] For a few weeks now [18:14] pedro_ - thanks [18:14] Thanks! Great to be a part of it!! [18:14] hggdh, charlie-tca, vish do you guys remember any other new member? [18:14] for -control? [18:14] Yes Sir [18:15] can't remember the names, but there was another one [18:15] crap [18:15] nope, those are the two.. [18:15] or I imagined it [18:16] Bjorn [18:16] he was mentioned already [18:16] I will apply soon, promise [18:16] yes, typed it and immediately saw his name in the backlog [18:16] Ok remember guys that if you're part of the Bug Control team you can also help to review the new members applications [18:17] Ricardo Salveti [18:17] so pretty please with sugar and all, if you have some time please review some and give the +1 or -1 [18:17] and, of course, the Hardware Cert Team :-) [18:17] it shouldn't take more than 10 minutes [18:18] So, I didn't imagine another one :-) [18:18] hggdh, ah yes Ricardo :-) [18:18] * hggdh had to look at the emails to find the correct spelling of Ricardo's name [18:18] ok next item [18:18] Riccardo Salvetti ? [18:18] [TOPIC] Open Discussions [18:18] New Topic: Open Discussions [18:19] in https://wiki.ubuntu.com/UbuntuBugDay/Organizing#Announcement%20E-mail can we add the mentoring team to the regular team cc list? [18:19] anything else to raise, announce, etc ? [18:19] vish, sure! i'll add it [18:19] hey [18:19] pedro_: thx :) [18:19] the mentoring team _should_ be subscribed to bugsquad, right? [18:20] not necessarily. do we have that in the requisites? [18:20] * vish checks [18:20] it seems like mentees should be part of bugsquad [18:21] vish, done, the mentoring team was added to the cc list [18:21] thx.. [18:23] the wiki page doesn't say anything about mentees being part of the bugsquad [18:23] https://wiki.ubuntu.com/BugSquad/Mentors [18:24] i don't see much diff on being part of it or not though [18:24] diff as in benefit [18:25] folks anything else you want to raise at the meeting? [18:26] Today we're celebrating a bug day, so if you have time : https://wiki.ubuntu.com/UbuntuBugDay/20110609 ; help us to squash some bugs there [18:28] pedro_: I disagree on the mentee/bugsqad member [18:28] Being a mentee says "I want to be in bugsqad and eventually bug control" [18:29] Then they should be part of the mailing list that keeps them informed of important things concerning that bugsquad [18:29] so shall we put that as a requirement? subscribe to the bugsquad mailing list [18:30] but how do we make sure they are subscribed? [18:30] we ask them to send an email saying hello? [18:30] k.. [18:31] Don't they have specific things we check already before letting them into the group? [18:31] charlie-tca: we check the CoC , but for this mailiman Bugsquad list it is not easy, for the LP team it is easy to compare numbers [18:32] the group is smaller, but bugsquad list is huge and has others as well.. [18:33] right, only the admins can check the members of a list [18:33] Oh, then make it a suggestion, maybe?> [18:34] pedro_: actually others can check too, but it is not easy to keep track. [18:34] charlie-tca, and put a 'hey if you want to keep informed of important things concerning to the bugsquad make sure to join our mailing list' [18:34] the list will show the email ids, we wont know if who is who [18:35] s/if// [18:35] then we as mentors can check again if they came up with a question in the mentoring team [18:35] that as a reminder to join the list [18:36] so what do you guys think, shall we go for the suggestion and then the double check when they start working in the mentoring team? [18:36] pedro_: we would then be asking them to join two mailing lists, not sure it is the ideal way to make people know info.. we can suggest but we can not be sure they are subscribed.. [18:37] right [18:37] don't we require the mentees to join bugsquad? [18:37] (and the ML) [18:38] nope [18:38] hggdh: nope not right now, but iirc we had that removed , i think bdmurray might know about that, if it was removed [18:38] OK. I think we should ;-) [18:39] ok shall we discuss this at the bugsquad ML ? [18:39] sounds good.. [18:39] ok lets do that [18:40] alright folks anything else to discuss? [18:40] otherwise we'll go for the last item on the agenda [18:40] [TOPIC] Chair for next meeting [18:40] New Topic: Chair for next meeting [18:41] any volunteer? [18:41] * pedro_ looks at the channel [18:42] oh well i'm sure bdmurray we'll be glad to chair it :-P [18:42] #endmeeting [18:42] Meeting finished at 12:42. [18:42] thanks for attending! [18:43] thanks pedro_ [18:43] thx pedro_ [18:43] pedro_: yeah thanks :) [18:43] you're welcome folks :-) [18:43] now lets go back to the bug day!! === jibouman` is now known as jiboumans [18:48] Thanks for chairing, ped === yofel_ is now known as yofel === kenvandine_ is now known as kenvandine === Quintasan_ is now known as Quintasan