=== dholbach_ is now known as dholbach === yofel_ is now known as yofel === Quintasan_ is now known as Quintasan === txwikinger2 is now known as txwikinger === macer1-zlyklon is now known as macer1 [14:58] fnop [14:59] #startmeeting [14:59] Meeting started Thu Sep 22 14:59:22 2011 UTC. The chair is NCommander. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. [14:59] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [14:59] * davidm waves [14:59] hrm, the bot ene upgraded [14:59] seems like [14:59] https://wiki.ubuntu.com/ARM/Meeting/2011/20110922 [15:00] we have no action items from last meeting so [15:00] #link http://people.canonical.com/~platform/workitems/oneiric/ubuntu-arm.html [15:00] #link http://people.canonical.com/~platform/workitems/oneiric/ubuntu-arm-ubuntu-11.10-beta-2.html [15:00] hello [15:01] i guess we need to start the postponing fun [15:02] hrm, the tracker is only showing me and infinity [15:02] ogra_: fix it :-P [15:02] ?? [15:02] i wonder where you look at [15:02] i see the whole team [15:02] oh [15:02] nm [15:02] http://people.canonical.com/~platform/workitems/oneiric/ubuntu-arm-ubuntu-11.10.html - I typed the wrong page in my browser [15:03] GrueMaster, your update-initramfs test can be set to done if you made a succwessfull install ;) [15:03] workitem wise, we're not too bad off. I have a few stranglers which will die soon (and some I should have marked DONE already) [15:04] infinity, do we plan to still see the apt ship pool whatever changes ? [15:04] looks to me like thats P material [15:04] ogra_: Yeah, I'd like to land them early next week, I think. [15:04] (pool works as is) [15:04] But I could defer. [15:04] hmm [15:05] its really late and we should all concentrate on bugs from now on [15:05] Pool works, but tasks are broken, which is pretty annoying for server. [15:05] and given that it works atm ... [15:05] I'd prefer to postpone none critical items until next cycle [15:05] right [15:05] Lets clean up, get RC solid and be happy [15:05] right [15:05] * infinity shrugs. [15:05] Happy to defer, though that is a bug. :P [15:06] [topic] ARM Server Status (NCommander, Daviey) === meetingology changed the topic of #ubuntu-meeting to: ARM Server Status (NCommander, Daviey) [15:06] infinity, is it big enough to SRU later? [15:06] GrueMaster, postzpone the preinstalled stuff for jasper too, unless you want to actually test preinstall commands on kernel cmdline (that works since forever) [15:06] davidm: SRUing it's not really an option, IMO. [15:06] w.r.t. to omap guided partitioning, I *finally* got partman-uboot ina state where it does what it should. I need to cook off a new partman-reciepes, but that shouldn't be too hard. I'll give GrueMaster a modifiednetinstall to test today or tomorrow. [15:07] ok [15:07] NCommander, you still have three open items too [15:07] server kernel is on the schedule for P, i think you can postpone that [15:08] the other two look pretty well, like paperwork [15:08] yup, will do. [15:08] infinity, OK then not that critical I suspect [15:08] paperwork fortunately isn't affected by freezes [15:08] ppisati, the kernel config WI is also covered by a UDS session [15:08] i'm unsure if thats a :-) or a :-( [15:08] I'm going to mark iSCSI as done. The only remaining issue was booting from iSCSI and that is being worked on in the server team. [15:08] ppisati, so i'd say postpone that [15:09] ogra_: WI? [15:09] * ogra_ guesses that were all WIs that were left [15:09] ah [15:09] i must say we did pretty well given the sheer amount of crao we had after UDS :) [15:09] work item [15:09] right [15:09] ppisati, see the link above [15:09] you have one open item that can be postponed [15:09] NCommander, move ? :) [15:10] [topic] Kernel Status (cooloney, ppisati) === meetingology changed the topic of #ubuntu-meeting to: Kernel Status (cooloney, ppisati) [15:10] nothing exciting this week [15:10] * janimo working on getting ac100 new kernel packaged and uploaded [15:10] on my side [15:10] woohoo [15:10] i'm working on the sd removal bug [15:10] (and i found the problem) [15:11] wow, that was fast [15:11] janimo: Didn't you have an mx5 kernel incoming for me too? [15:11] infinity, jcrigby is handling that [15:11] yep, but i don't know yet how to properly fix it (because that would be a layering violation) [15:11] janimo: Shiny. [15:11] his git tree and processes, I had no idea how to make even such a small change [15:11] yeah, its tricky if you are not used to it [15:12] which is sad. One line change and a bugfix that can be expressed clearly in a single sentence (turn on CONFIG_LDBAF) needs a lot of legwork [15:12] and even if you know how to do it ... you will fall flat on your face if it doesnt work right :) [15:12] sincer these scripts are pure mystery [15:12] *since [15:13] well, some of the docs help, but not everything is documented [15:13] yeah [15:13] worse there is more than one way to do it [15:13] hehe [15:13] linux is all about choice ;) [15:13] NCommander, ? [15:13] yes, and it is refelcted by the awesome market share [15:14] ogra_: ? [15:14] * ogra_ puts NCommander on wheels so he starts moving [15:14] :) [15:15] [topic] ARM Porting/FTBFS status (NCommander, janimo) === meetingology changed the topic of #ubuntu-meeting to: ARM Porting/FTBFS status (NCommander, janimo) [15:15] gobject-introspection fails :( [15:15] The rebuild test is finally done, we should be combing through the results as quickly as we can. [15:15] I tentatively looked at postgres failing. [15:15] and postgres might be intresting for the server side [15:16] right [15:16] (looking at the ftbfs list) [15:16] I'd say it is essential? [15:16] beyond that, main looks as good as universe looks bad [15:17] we should all try to paticipate in the 5 a day project cjwatson started ... ate least with one or two packages per week or so [15:17] _*at [15:17] more if you can :) [15:17] [topic] ARM Image Status (ogra, NCommander) === meetingology changed the topic of #ubuntu-meeting to: ARM Image Status (ogra, NCommander) [15:18] 2 packages per week is not participation in 5 a day project :) [15:18] janimo, more than nothing :) [15:18] that is true [15:18] images look okayish [15:18] they *should* be better at this point of the release though [15:18] desktop really fell behind [15:19] Need to reenable swap, at least on omap. [15:19] but overall they are fine [15:19] yeah [15:19] i think infinity committed to fix that properly yesterday [15:19] mx5 is a bit in a weird state [15:19] GrueMaster: Did I get a bug report? [15:19] needs kernel to test properly [15:19] we know it works but it didnt survive the switch to ext4 [15:20] ogra_: I suspect mx5 will be Just Fine with the new kernel, but hard to tell without. [15:20] infinity: I was asleep when you responded, and still on my first cup of coffee, so...not yet. [15:20] infinity, i thought janimo did a local ext3 test [15:20] GrueMaster: Kay. :) [15:20] ogra_, GrueMaster did a test, and so did I [15:20] k [15:20] that should be enough [15:20] looked reasonable [15:21] we just need to convince skaet that it is ;) [15:22] * skaet is a bit worried about mx5 for good reason.... :P [15:22] Any chance of getting a new kernel and a new image today to make release? [15:22] skaet, its all fine, but we only discovered during milestone testing that ext4 support is missing [15:22] GrueMaster, no, builds to long [15:23] k [15:23] Broken kernel configs are easy to fix. I'm not terribly concerned. Yet. :) [15:23] skaet: The image was fine Monday prior to EXT4 switch (and ubiquity churn). [15:23] thanks GrueMaster. :) [15:23] skaet, we will have to skip B2 for it, but from monday lates iot shoudl be fine, its a "community supported" image anyway [15:24] *latest [15:24] save for archive skew :) [15:24] hehe [15:24] since the upload floodgates are open again for the desktop team :) [15:24] * ogra_ has nothing else for images ... if NCommander wants to move ... [15:24] [topic] QA Status (GrueMaster, mahmoh) === meetingology changed the topic of #ubuntu-meeting to: QA Status (GrueMaster, mahmoh) [15:25] * GrueMaster wakes up to respond. [15:25] * janimo was conned into signing in to iso.qa [15:25] Release testing went...Well it happened. [15:26] I really do not feel as good about this release as I have in prior releases this late in the cycle, due to lack of dep testing. [15:26] *deep [15:27] agreed [15:27] My focus next week will be dedicated to desktop deep testing to see what I can squeeze out. We don't have a lot of time left to shake out any bugs, so stay in touch. [15:27] that needs fixing in P [15:28] Beyond that, I don't have anything else. mahmoh? [15:28] nothing here GrueMaster [15:29] moving on.... [15:30] * GrueMaster listens to the silence. Somewhere in the distance, a cricket chirps. [15:30] [topic] Linaro Updates (rsalveti) === meetingology changed the topic of #ubuntu-meeting to: Linaro Updates (rsalveti) [15:30] hey [15:31] first is the request to help sponsoring the libjpeg-turbo package [15:31] package at revu already, and skaet agreed that it would be good to publish it at least to universe, if possible [15:32] during last week at the release meeting [15:32] What is it, exactly? [15:32] rsalveti: what is it and why do we want to uploadless than 15 days from release? [15:32] if anyone with time to review it, please :-) [15:32] An ABI-compatible accelerated replacement for libjpeg is how I'd read it from just the name. [15:33] rsalveti, speaking of which , there should be an organized linaro sponsoring process. As it is now the requests ar ead-hoc and left to the developers themselves, who often do not dare asking or know where to do it, and are content with the many ppas [15:33] libjpeg62 replacement, with simd support [15:33] NCommander, its universe ... there will likely still be plenty of packages :) [15:33] s/packages/new packages/ [15:33] neon and such, for those who want to try at arm devices [15:33] I'd say lets go for it if skaet is OK with it [15:33] indeed [15:33] skaet already gave OK [15:33] simd support is very good [15:34] rsalveti: Too late now, of course, but why aren't the changes in libjpeg itself? :P [15:34] was discussed during last release meeting [15:34] I have plenty of jpg images to put it through some paces. [15:34] infinity: long history [15:34] default at firefox, chromium and fedora already [15:34] * skaet nods, its universe, so low risk. [15:34] GrueMaster: Porn is not a test framework. [15:34] infinity, this is an upstream fork not a linaro one, linaro contributed though lately [15:34] yup [15:35] libjpeg-turbo is quite old already [15:35] aww. [15:35] janimo: yeah, planning to discuss that at UDS [15:35] ok [15:35] there was some discussion over email already, will see how it goes [15:36] also worked to get 4460 working with our images [15:36] support is quite broken atm, need kernel and u-boot fixes [15:36] * ogra_ wishes we could test that already :P [15:36] rsalveti, but no new packages, they still go to omap4 right? [15:36] do we want/need to make the support for the release? [15:36] janimo: no new package, just bugfixies [15:36] if possible sure [15:37] rsalveti, depends on the impact [15:37] Want, sure, need, no. [15:37] otherwise the borad will appear and there will be no ubuntu support for them till april [15:37] And yes, depending on impact. [15:37] For 4460? If we can get it in before release, it would be awesome. [15:37] kernel should be fine, as it's specific to a board revision [15:37] is this quad-core or merely dual? [15:37] below 200 LOC might be ok :) [15:37] u-boot should be tricky [15:37] or we can point folks at Linaro bootloads with instructions on how to fix image [15:37] janimo, still A9 [15:37] but will get it working here first, and open the bugs for them [15:37] ogra_, even if obfuscated and 80 columns wide ascii art 200 LOC ? [15:38] then you can decide based on the amount of required changes [15:38] davidm: That gets ugly. I am already doing that for Maverick and Natty. [15:38] janimo, i dont care,i dont have to review it *g* [15:38] we can always point to linaro images, as they are usually more up to date, true [15:38] janimo, hmm ? [15:38] how can they be more up to dayte if they are a release behind ? [15:39] we're also creating oneiric based images now [15:39] and hope to switch to it next month [15:39] we'll see how it goes [15:39] they are based on a release behind but ahead with platform support stuff [15:39] anyway, that's most of ti [15:39] old evince, new kernel uboot X [15:39] we're preparing the release, so everybody is busy atm [15:39] I know I'd pick the second set if only that works on my board :) [15:40] depends what you want :) [15:40] ogra GrueMaster do you have 4460 boards yet [15:40] nope [15:40] not yet. [15:40] Yea, thats what I thought [15:40] nicolas wanted to ask around once again [15:40] i'll ask him tomorrow again :) [15:40] I got an email asking for shipping addresses which I provided [15:40] ah [15:40] but nothing so far then [15:40] Ooo, new toys? [15:41] same toys, new heart :) [15:41] Apparently not .... [15:41] infinity: you should join the ti call ;-) [15:41] yeah [15:41] if you like to get up in the middle of the night :) [15:41] rsalveti: That would involve one more meeting a week. [15:41] (And that) [15:41] first issue is that the led gpio is now connect at the mpu o_O [15:41] so once you boot the board, and the led is on, it'll basically turn itself off [15:42] fun ! [15:42] fixed already, but was fun :-) [15:42] anyway, I'm done [15:42] sorry about that [15:42] my laptop suddenly decided that it didn't have a wifi card [15:43] NCommander, we didnt notice [15:43] but yuo can move ;) [15:43] *you even [15:44] rsalveti, do linaro have beagle images too? [15:44] omap3 I mean [15:45] NCommander, moving on [15:45] [topic] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [15:45] janimo: yes [15:45] janimo: igep, overo, beagle, panda, and so on [15:45] no pandas this cycle for armel builds? We carry the timed out builds to P [15:45] ?? [15:46] we are already building on pandas [15:46] partitally at least ... until infinity needs them [15:46] one question I had, are we really planning to go just with armhf for next cycle? [15:46] half/half? [15:46] half half [15:46] just because it'll be a lts [15:46] janimo: We have a bunch. Though once armhf toolchain changes land, they'll get repurposed to armhf. [15:46] was always the plan [15:46] but was initially for this cycle [15:46] we have to pick which one is the default [15:46] rsalveti: "Hope" is a better word than "Plan" with al the delays we've had. :/ [15:46] and have only armfh for next cycpe [15:47] infinity: yeah =\ that's why I'm asking [15:47] no, you need at least one release where you have them in parallel [15:47] so was getting all the pandas in the build farm online. [15:47] infinity: what's the current status on that? [15:47] rsalveti: Need to land a GCC change, test it, re-bootstrap, and go. [15:48] * janimo wonders if giving back packages that fail after 10 hours hoping they land on a panda this time is a good use of build resources [15:48] Well, can probably skip most of re-bootstrapping with a compat symlink for a while. [15:48] a gcc change after b2 ? [15:48] ok, cool [15:48] ogra_: One that only affects a new architecture. [15:48] ah, k [15:48] janimo: No. If you want that to happen, talk to me, and we'll force it. [15:49] Much as I personally hate to say it, I think we will need to make both armel and armhf images for testing next cycle. [15:49] yes [15:49] infinity, good. Last time you said it is only possible if everythng is on manual, which is a hassle. I'll check the list to see what the latest status is [15:49] We already knew that. [15:49] but we will only release one of them [15:49] We have to test both until some arbitrary cutoff point where we choose one for release. [15:49] and will only test one of them :D [15:49] and are we supporting both as LTS? [15:49] janimo, nope [15:49] or just armel [15:50] janimo: It *is* only possible with everything on manual. :P [15:50] rsalveti, unlikely that we support both [15:50] janimo: But that's not rocket science either. [15:50] guess a good discussion for uds [15:50] we cant destabilize server [15:50] so hf needs to be rock solid before we switch [15:50] rsalveti: We won't really know by UDS. But we'll support the one that doesn't suck. [15:50] * janimo thinks of the churn in debian packaing to replace/amend armel ifdefs with armhf [15:51] hehe [15:51] janimo, the debian hf port should have a good bunch already [15:51] infinity, what are the suckage risks? Toolchain issues? [15:51] janimo: Honestly, my only concern is having it all built in a couple of months. [15:52] Whenever the armel buildds are idle, I intend to steal most of them for armhf to try to speed that process up. [15:52] We'll see how that works out. [15:53] rsalveti, we'll make at call at freature freeze which will be what we go out with for ARM [15:53] is buying setting up 20 or more boards to help such an obstacle? [15:53] once we choose, we will stop testing images on the other arch [15:53] davidm: fair enough [15:53] we seem to spend more in man hours trying to cater for that deficiency [15:54] janimo, getting pandas is VERY hard again [15:54] imx53 is a *lot* easier now [15:54] janimo: We have systems that aren't online yet. It isn't due only to a lack of boards. [15:54] and with sata [15:54] I'm hoping something else will pop up soonish [15:54] I'd happily take a bunch of mx53s. [15:54] GrueMaster, hence my 'setting up' in the question [15:54] rsalveti, well, it hads to proove stable first :) [15:54] *has [15:55] janimo: Manpower is also a big limiting factor. [15:55] indeed, lots of mx53s are good to, it;s not like we used dual cores so fa [15:55] r [15:55] with things like ext4 support missing in the kernel i wouldnt go for a buildd on it yet :) [15:55] well, at least you'll have support from linaro :-) [15:55] GrueMaster: Other than the master/slave in the DC being fiddled with for the "PPA cluster", we have others not online? [15:55] GrueMaster, right but seems a lot of manpower - albeit that of different men - is wasted to work around such issues, and to twddle thumbs while waiting [15:55] iirc, we have 5 in a sudo state. [15:56] We can discuss offline. [15:56] infinity, GrueMaster lets take this off-line and talk to the folks that know whats going on [15:56] * infinity nods. [15:56] GrueMaster, sudo state - the one in which a person gets you a sandwich without opposition? [15:56] like a trance you mean? [15:57] NCommander: Close? [15:57] closing in 3 [15:57] 2 [15:57] 1 [15:57] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [15:57] Meeting ended Thu Sep 22 15:57:28 2011 UTC. [15:57] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-09-22-14.59.moin.txt [16:14] @defaultcapability remove misc.last [16:14] AlanBell: The operation succeeded. === macer1-zlyklon is now known as macer1 [18:00] * pitti waves [18:00] \o [18:01] so, just the two of us plus half a cjwatson [18:01] heh. yeah, not sure where Keybuk is. [18:03] 1/2 of me [18:03] hey mdz [18:03] who is chairing? [18:03] I didn't notice anything on the lists recently [18:03] mdz: I don't think we picked a chair last time as we just skipped the meeting [18:03] I was out last meeting; was there a summary sent? [18:03] no, there was nothing happening [18:04] we just stated that cjwatson's item (brainstorm) was/is happening [18:04] * kees nods [18:05] my only agenda item is that I'm disappointed that we haven't kept up with the brainstorm reviews [18:05] we made a public commitment to do it once a quarter and we haven't met that commitment [18:06] the previous one was...March? [18:06] is there some kind of infrastructure or reporting we could put in place to help stay on schedule? [18:06] a calendar would do [18:06] we noted on the agenda when the next one was due [18:06] but apparently it was dropped now [18:06] I think I put it on the ubuntu engineering calendar as well [18:06] pitti: ah, like a count-down? [18:07] I think whenever we do one we shold bump the date there, not drop the item completely [18:07] i. e. * Brainstorm review [next due: Month Year] [18:10] so the normal cycle would have been to have the next one nowish, right? [18:10] so we should do the next one over christmas? [18:13] pitti: yeah, seems right [18:14] * pitti adds it back then [18:15] done [18:15] so I guess that's a wrap? [18:17] so, good night everyone! === doko_ is now known as doko === plars is now known as plars-afk === yofel_ is now known as yofel