=== nixternal is now known as handbag_henry === handbag_henry is now known as nixternal === m4v_ is now known as m4v === imlad|away is now known as imlad === dholbach_ is now known as dholbach === imlad is now known as imlad|away [11:57] hi,can anyone tell me when is next meeting for ubuntu asia oceania? [12:08] hi [12:08] hi indus.. [12:09] hello [12:09] did any asia-oceania meetings happen today? [12:09] i wanted to become ubuntu member so iam not sure whats going on where [12:10] indus: did you mail them like I suggest4ed to you the other day as the wiki had not been updated. [12:10] yes i believe,in fact one of the guys is a friend of mine [12:11] but they all seem busy with their work [12:11] fridge says asia oceania meet today 10 am gmt [12:11] i probably missed it [12:11] damn [12:12] no meeting happend at 10am today going by the logs [12:12] ok a question is, do they have any group email so i can send? [12:13] popey: do you know if the Asia meting board has a group mail [12:13] their meeting is on the 1st sept [12:13] https://wiki.ubuntu.com/Membership/RegionalBoards/EMEA [12:13] indus: there you go [12:14] er [12:14] oops [12:14] wrong one [12:14] np,iam sending from launchpad [12:14] sorry, their next meeting isn't listed [12:14] indus: they have a mailing list [12:14] popey: they dont [12:14] so it says on launchpad [12:14] they do [12:14] its not on launchpad [12:15] one moment [12:15] where is it [12:16] czajkowski: hi how r u,thanks for the other day :) [12:17] ubuntu-membership-board-asia-oceania@lists.ubuntu.com [12:17] omg thats long [12:17] indus: no problem. [12:18] ok ill email them later evening [12:18] last question,what are you guys hanging in here for? any meetings? [12:19] i lurk in many channels [12:19] ok [12:19] bye for now [12:19] indus: I watch the meetings as more often than not then are interesting , tb is unteresting, foundation has wit, and the kernel team runs swiftly. [12:32] "tb is unteresting" could be taken two ways.. very tactful ;) [12:32] bah [12:33] should be interesting! [12:33] http://www.urbandictionary.com/define.php?term=Unteresting :) [12:33] popey: sfw ? [12:33] dunno [12:33] play it safe :) [12:34] http://pastebin.ubuntu-uk.org/57169 is SFW [12:34] copy/pasted :) [12:36] heh === fader|away is now known as fader === imlad|away is now known as imlad === imlad is now known as imlad|away === marjomercado is now known as marjo === imlad|away is now known as imlad === ian_brasil is now known as IAO [15:58] * lool hey! [15:58] * slangasek waves [15:58] * fader waves [15:59] * kenvandine waves [15:59] * czajkowski wonders is the mexican wave about to kick off in here [15:59] afternoon [16:01] * robbiew does a cartwheel [16:01] \o [16:01] * kenvandine dives to avoid robbiew [16:02] * robbiew turns an ankle and lands hard on his @$$...vowing never to try that again [16:02] :P [16:02] is it Friday yet? [16:03] Riddell, marjo, sbeattie, soren, Hobbsee, rtg, apw, njpatel: here? [16:03] o/ [16:03] hey [16:03] slangasek: Riddell is offline until Sunday [16:03] ok [16:03] * rtg is here [16:03] marjo waves [16:03] * ogra sniffs ... [16:03] #startmeeting [16:03] Meeting started at 10:03. The chair is slangasek. [16:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:03] smells like release meeting here [16:04] [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-08-28 [16:04] LINK received: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-08-28 [16:04] [TOPIC] Actions from previous meetings [16:04] New Topic: Actions from previous meetings [16:05] cjwatson: I saw mail to Gustavo about landscape, any answer yet? [16:05] fader: any progress on working around that nautilus crash (now that seb128 is back from vac)? [16:06] We're still seeing the bug crop up but seb128 has been on holiday so we haven't discussed it. [16:06] slangasek: I thought seb was back on Monday... [16:06] fader: oh, right [16:06] nevermind then :) [16:06] :) [16:06] slangasek, he appeared briefly yesterday [16:06] but not really here [16:06] * slangasek nods [16:06] Ah, I didn't see him then :( [16:06] slangasek: unfortunately not; however I'm not convinced we need to track this here [16:07] we've delivered something on request of the Landscape team; if it's broken or inadequate then it's their responsibility to let us know :-) [16:07] cjwatson: ok [16:07] +1 [16:08] soren: did the AWS page get published? [16:08] soren: and do we have eucalyptus seeded now? [16:08] euca is seeded [16:08] excellent [16:08] * cjwatson watches it being sucked down in his jigdo run [16:10] slangasek: the page has not been published yet [16:11] (oh, I guess soren's not here, there was a conditional in that mail) [16:11] dendrobates_: soren is following up? [16:11] slangasek: but smoser followed up with Amazon and is waiting for a response to Amazons internal escatation, [16:11] ok [16:11] # njpatel to file bug against unr-default-settings for tracking of message indicator status [16:11] njpatel: ^^ did that get done? [16:11] slangasek: lool did it during the meeting last week [16:12] one sec, let me get the # [16:12] thanks [16:12] [TOPIC] QA Team [16:12] New Topic: QA Team [16:12] njpatel: (we'll move on, drop the bug # when you have it) [16:12] marjo, fader: hello [16:12] Hardware certification [16:12] http://people.canonical.com/~fader/hw-testing/current.html [16:12] LINK received: http://people.canonical.com/~fader/hw-testing/current.html [16:12] No real changes. The only failure result we're seeing is still nautilus leaving logs in /var/crash [16:13] mathben, our intern, is running tests on netbooks and laptops today, so some of those 'untested' results will fill in throughout the day [16:13] However some of them may not due to issues with the ISOs (particularly UNR seems to be having trouble installing today; I've asked davmor2 to see if he can reproduce the install issues and we'll file bugs if so) [16:13] #417001 fix-released [16:13] mathben has also verified that bug 404264 seems to be fixed -- the install is proceeding past the network initialization stage but the system is failing an fsck after install, which should be unrelated. We will investigate the fsck failure and update 404264. [16:13] Launchpad bug 404264 in linux "karmic installer fails to detect Intel 82567 network card" [High,In progress] https://launchpad.net/bugs/404264 [16:13] Spec progress [16:13] karmic-qa-extended-audio-testing: this is 'beta available' -- I have written tests to hit a lot more of the detected audio hardware as well as some tests that can be run automatically in the certification machines we have in the lab and datacenter [16:13] (I won't bore you with a list or gruesome details unless anyone is particularly interested) [16:13] (that's it from me modulo questions) [16:14] ok, spec status: [16:14] * karmic-qa-increase-apport-adoption - Requested current status and plan with the the LP team. [16:15] General spec status can be seen here: https://wiki.ubuntu.com/QATeam/RoadMap [16:15] That's it. [16:15] any questions? [16:15] thx folks [16:15] [LINK] https://wiki.ubuntu.com/QATeam/RoadMap [16:15] LINK received: https://wiki.ubuntu.com/QATeam/RoadMap [16:16] no questions here [16:16] anyone else? [16:17] [TOPIC] Desktop Team [16:17] New Topic: Desktop Team [16:17] marjo, fader: thanks [16:17] kenvandine: hi [16:17] :) [16:17] davidbarth, njpatel: also hi :) [16:18] hi [16:18] slangasek, so do i go over the items here? or just highlight issues? [16:18] kenvandine: there's an up-to-date team wiki page about release status? [16:18] yes [16:18] [link] https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus [16:18] LINK received: https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus [16:18] [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [16:18] LINK received: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [16:18] right :) [16:19] the DX status covers both desktop and unr [16:19] davidbarth: Thanks BTW [16:19] kenvandine: if there are specific points on there that you think need to be discussed - need more resources from outside your team, or there's something that may affect release scheduling - please highlight those [16:19] slangasek, ok... no issues atm [16:21] nothing at risk for the release [16:21] davidbarth, you have any? [16:21] on the dx side, there is a current regression with the session menu [16:21] pidgin does not reflect its status on the menu [16:22] the risk is limited as the code is there but a bug still prevents the connection [16:22] davidbarth, empathy too [16:22] I see the firefox bookmark syncing package landed in my package list recently, does that mean we might get it? [16:22] we'll add a bug to track that for the UIF [16:22] lool, no [16:22] well [16:22] it won't be in by default [16:22] ok [16:22] installed via apturl from a u1 utility [16:23] davidbarth: UIF isn't in effect yet; opening a bug report for tracking is good anyway, but won't this be fixed before then? [16:23] on the indicator-messages, we also have to update PK calls to the new API (tracked in the MIR) [16:23] And/or indicator-session? [16:24] davidbarth, i think that is indicator-session [16:24] not messages [16:24] I think I was this mentionned in -session's MIR [16:24] indicator-session sorry, i-msg doesn't use that [16:24] Rigt [16:24] but that is for beta [16:25] indicator-session was the hot topic for this milestone, but is now safe in main [16:26] kenvandine: I'm confused about the PolicyKit->PolicyKit-1 migration status; if hal is not being switched, and we've gotten as much hal out of karmic as we can already, does this mean we have to ship both policykit and policykit-1 by default in karmic? [16:26] slangasek, i don't think so... pitti's plan is just policykit-1 [16:26] afaik [16:27] ok, so presumably the bits of hal we have to keep don't need PK [16:27] btw, n-osd and notifications patches are also safe in karmic; monitoring some regressions; also won't be able to support keyb brightness notifications (upstream regression) [16:27] we still have indicator-session depending on policykit though, it needs to be updated to -1 [16:27] slangasek, i assume [16:27] kenvandine: yes [16:27] the current hal package still depends on policykit, though, so I guess there's cleanup to be done there [16:27] slangasek, ok, we should double check with pitti [16:28] although i am sure he is aware [16:28] * slangasek nods [16:28] on the topic of kubuntu integration, agateau has provided all the critical parts, and upstream'ed as much as possible; the default settings will depend on upstream's final take on them [16:29] kenvandine: on the filtered spec list I see 'desktop-karmic-integrating-with-ubuntu-one' marked as Essential, but delivery status is 'started' - is that just an inaccurate spec status? [16:29] There is currently a fair amount of grumbling from early users about their default on status. [16:29] finally, xsplash: we released some performance improvements and fixes, but it's there to be fine tuned before UIF [16:29] that should be beta available [16:29] * kenvandine fixes [16:30] ScottK: yes, agateau mentionned it; I trust your judgment to enable them where you see fit [16:30] ScottK: that's grumbling that notify-osd is on by default? [16:31] slangasek: Grumbling that messaging menu is turned on by default. [16:31] davidbarth: keyboard brightness notifications... so we aren't going to have those at all in karmic? [16:31] We don't have notify-osd in Kubuntu [16:31] slangasek, i can't change the status, but will have it done [16:31] davidbarth: I think it's fine for now for testing. [16:31] [ACTION] kenvandine to get status of desktop-karmic-integrating-with-ubuntu-one fixed up [16:31] ACTION received: kenvandine to get status of desktop-karmic-integrating-with-ubuntu-one fixed up [16:32] slangasek: nope, there's no such thing in DK atm; njpatel may provide add. details in the bug report [16:32] davidbarth: which bug report? [16:33] slangasek, blueprint updated :) [16:33] slangasek: don't have it listed now; can take the action to fwd it [16:33] kenvandine: thanks [16:34] [ACTION] davidbarth to find bug report regarding keyboard brightness notification regression [16:34] ACTION received: davidbarth to find bug report regarding keyboard brightness notification regression [16:35] ok, think I've managed to absorb everything in the report, at least regarding the desktop [16:35] anyone have questions? [16:36] You want Kubuntu stuff now? [16:36] yes, please [16:36] KDE 4.3.1 got tagged yesterday [16:36] We expect to have it uploaded before the milestone freeze on tuesday [16:36] spec status is at https://wiki.kubuntu.org/Kubuntu/Todo/Karmic [16:36] [LINK] https://wiki.kubuntu.org/Kubuntu/Todo/Karmic [16:36] LINK received: https://wiki.kubuntu.org/Kubuntu/Todo/Karmic [16:37] A few things got deferred, but nothing essential. [16:37] Kubuntu Netbook is going well. [16:37] Upstream is planning on a plasma-netbook sprint next week. [16:37] So I'll be trying to work snapshots from the sprint in around the freeze. [16:37] ok [16:38] I think that's it. [16:38] alrighty [16:38] I guess I'll add that upstream coordination on the netbook stuff is going very well. One of the upstream devs is in #kubuntu-netbook and our buglist is his work list for next week. [16:39] ScottK: heh, nice :) [16:39] We should be ~6 months ahead of any other distro with a KDE netbook flavor. [16:40] [TOPIC] Mobile Team [16:40] New Topic: Mobile Team [16:40] kenvandine, ScottK: thanks [16:40] lool, davidbarth: hello (again) [16:40] [link] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic [16:40] LINK received: https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic [16:40] dx back on stage again, with njpatel [16:40] * News: switched to v7 buildds, v7 toolchain uploaded, new armel+dove image (relatively broken), new moblin-remix image (very broken) [16:41] * Oliver is looking for some skilled oo.o person to help debug #417009 (oo.o apps crash on startup on armel); ccheney reports being busy and doko is on VAC; cjwatson suggested rickspencer might know [16:41] ah no rickspencer [16:41] * tracking DX/UNR integration: had a meeting to review any potential integration backlog with dbarth and njpatel and we took various actions to review the current seeds, gconf settings, and we are now reviewing UNR status every week in the mobile IRC meeting; we will also start attending the desktop/DX integration weekly calls starting next week; happy to also cover this in the release meetings [16:41] * I'd like to know whether we want to track moblin-remix status here just like UNR -- it's a lesser priority spin and an unsupported one though and the meeting is quite long already [16:41] * not sure how much of low resolution application patches we can still merge before UIF, but that's low prio [16:43] Oh on UNR integration I forgot to mention we actually believe to be up-to-date for everything; I think njpatel was trying out the latest config this morning [16:43] seeds etc. are all up-to-date [16:43] yep, we're up-to-date with everything. more releases next week with more bugs fixed, though :) [16:44] So no more "Why isn't this DX thing in UNR or why isn't this enabled in UNR?" :) [16:44] lool: moblin-remix status> if it's going to be a deliverable for karmic, we should track any problems with it here in the meeting [16:44] we had 2 criticals on UNR, both are fix committed, and fix-released as we speak: #351527 and #411530 [16:45] slangasek: Ok; it's a soft deliverable, unsupported, built from PPA; I think we want to move as much as possible into Ubuntu but it remains a "nice to have" [16:45] I will give updates here [16:45] oh, built from ppa - do we build that on antimony? [16:45] Yes [16:45] huh, ok [16:46] slangasek: I had the same reaction :) [16:46] [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus [16:46] LINK received: https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus [16:46] (relevant here too) [16:47] davidbarth even pointed me at https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus#Netbook%20%28UNR%29 earlier [16:47] slangasek: sure, mostly bug fixes, no new features [16:47] davidbarth: I think a couple of netbook-launcher are still to land next week but that's about it? [16:47] +features [16:48] lool: yes, but the upcoming releases don't contain additional features [16:48] Oh ok I misunderstood then [16:48] davidbarth: thanks [16:48] yep netbook-launcher, window-picker-applet, maximus will get updates next week. Most all fixes. [16:49] ok, looks good [16:49] any questions on mobile? [16:49] [TOPIC] Kernel Team [16:49] New Topic: Kernel Team [16:49] [link] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic [16:49] LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic [16:49] lool, davidbarth, njpatel: thanks [16:50] Not all of the release meeting bugs are on that page. Here is up-to-the-minute status: [16:50] bug #359338 - no progress [16:50] bug #290153 - still in progress (Andy is on vacation through next week) [16:50] bug #409233 - no progress, need to reconfirm with newer kernel releases [16:50] bug #404264 - patch upstream, definitely in 2.6.31-rc8 [16:50] bug #410198 - fix released [16:50] Launchpad bug 359338 in linux "apparmor paths are broken when using ecryptfs on jaunty" [High,In progress] https://launchpad.net/bugs/359338 [16:50] bug #418265 - should be fix released, will confirm with ogra [16:50] Launchpad bug 290153 in linux "Fails to find boot device in Intel D945Gnt" [High,In progress] https://launchpad.net/bugs/290153 [16:50] Launchpad bug 409233 in linux "[Regression] Bluetooth Causes Suspend to fail" [High,Triaged] https://launchpad.net/bugs/409233 [16:50] Launchpad bug 404264 in linux "karmic installer fails to detect Intel 82567 network card" [High,Fix released] https://launchpad.net/bugs/404264 [16:50] Launchpad bug 410198 in linux "'modprobe aoe' on Karmic kernel oopses with AOE device from Jaunty" [High,Fix released] https://launchpad.net/bugs/410198 [16:50] Launchpad bug 418265 in linux-fsl-imx51 "Warning in ehci-hcd.c:911 on kernel 2.6.31-5-imx51" [High,Confirmed] https://launchpad.net/bugs/418265 [16:50] Working on 2.6.31-rc8 which it has a critical inotify regression. [16:50] Dropped KSM patch set pending more rigorous testing [16:50] Working with mobile team to improve the ARM platform kernels. [16:50] rtg: you shorted me a bug in that report :) - bug #418265? [16:51] * Xtreme_Great wonders if this channel holds official ubuntu meetings [16:51] (and hmm, agenda editing fail; 410198 should obviously not have been in the list) [16:51] slangasek, I see it in the scroll back [16:51] Xtreme_Great: yes, and is doing so right now, so please only interrupt if you have relevant information :-) [16:51] rtg, fixed for me, broken for GrueMaster [16:51] * Xtreme_Great apologizes [16:51] rtg: ah yes - not on the wiki page [16:52] slangasek, right, its not one I've been tracking. [16:52] rtg, might be a different issue though, we both havent seen the warning message anymore [16:52] thats mostly it from me [16:52] ogra: different issue how? [16:53] slangasek, GrueMaster cant get USB NICs to work for some unknown reason (the ones i tested here work fine for me) [16:53] ogra: ok, but if it's not with this error message anymore... [16:53] slangasek, these arm platforms are notoriously unstable IMHO [16:53] AIUI USB disks are working for him now [16:53] slangasek, xactly [16:54] so I think that should be marked as fixed, and a separate bug opened for the NIC issue? [16:54] Maybe I can best describe the issue. I have two usb nics, one is a Pegasus, the other is a DM9601 (drivers). Both work fine in UNR, but they fail to detect mac addresses in arm. [16:54] * ogra would like to see tobins final comment before setting it fixed [16:55] GrueMaster, but you dont see ehci warnings anymore anywhere, right ? [16:55] The ehci bug was a kernel oops tat is no longer happening. [16:55] s/tat/that [16:55] good [16:55] slangasek, can be closed then [16:56] I'll file a new bug on the nic issue. [16:56] yeah [16:56] i'D still like to see the -source package come back for imx51 and i think slangasek had concerns about -docs [16:56] rtg: is bug #395358 on anyone's radar, btw? I suspect, but haven't proven, that this is also the root cause of bug #397698 now [16:57] Launchpad bug 395358 in linux "thinkpad fn+f5, Asus fn+f2: regression, rfkill toggling in the kernel instead of userspace" [Medium,Triaged] https://launchpad.net/bugs/395358 [16:57] Launchpad bug 397698 in linux "isAnyWirelessPoweredOn in state-funcs always returns 1 in karmic" [Medium,In progress] https://launchpad.net/bugs/397698 [16:57] we dont have a bug for that yet, i'll file one and might attach a patch for the packaging [16:57] ogra: yes, please follow up via LP for that [16:57] slangasek, I've not noticed that one. too damn busy with arm kernels. [16:58] rtg: anyone on the team not too damn busy with arm kernels who might take a look? :) [16:58] slangasek, I'm short handed right now [16:58] * slangasek nods [16:58] maybe I can get ogasawara to look at it [16:59] though smb's name is assigned. I'll prod him [16:59] ok [16:59] any other questions on kernel today? [17:00] [TOPIC] Server Team [17:00] New Topic: Server Team [17:00] rtg: thanks [17:00] dendrobates_: hi [17:00] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus [17:00] A couple things: [17:00] [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus [17:00] LINK received: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus [17:00] LP: #419515: OpenLDAP 2.4.18 upgrade, needed to complete server-karmic-directory-enabled-user-login [17:01] Virtual appliance features (not filed yet), needed to complete server-karmic-virtual-appliance [17:01] both are in need of FF. [17:01] Hopefully they can be completed next week during the server sprint. [17:02] that's all for me. :) === dendrobates_ is now known as dendrobates [17:03] no questions here [17:03] anyone else? [17:04] [TOPIC] Foundations Team [17:04] New Topic: Foundations Team [17:04] thanks, dendrobates [17:04] cjwatson, robbiew: hi [17:04] [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic [17:04] LINK received: https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic [17:04] the bug statuses there should be largely up to date; there's quite a few of them at the moment but we are making reasonably steady progress [17:05] if mvo's around, I wouldn't mind a quick discussion about whether bug 353534 is worth fixing in update-manager [17:05] Launchpad bug 353534 in linux "dapper->hardy->intrepid upgrade path leaves user with unmaintained kernel" [High,Fix released] https://launchpad.net/bugs/353534 [17:05] cjwatson: I'm around [17:05] cjwatson: sorry that I have not replied earlier [17:05] and if anyone has an SSD convenient for testing, it would be useful to me if somebody could volunteer to have it abused for testing bug 415888; especially if you have an SSD matching that in the report [17:05] Launchpad bug 415888 in parted "Installation fails on Crucial/Micron M225 256gb SSD" [High,Triaged] https://launchpad.net/bugs/415888 [17:05] cjwatson: I can add code to update-manager that deal with the kernel update if needed [17:06] mvo: do you think it makes sense? I wonder if we should have a general practice of trying to get people onto the current optimal kernel, whenever the rules change [17:07] cjwatson: I think its best to select the optimal kernel based on the cpuinfo content (unless it is a self compiled kernel) [17:07] now the probelm seems to be that its not trivial to find a good mapping of cpuinfo to best kernel :) [17:08] right, that's exactly the problem that the base-installer code should solve for you [17:08] unfortunately it will probably involve cloning-and-hacking it right now [17:08] though it's designed to be called as a quasi-library (albeit in shell), so you could do a ubiquity-style thing of including the whole source package in yours as a submodule or something ... [17:09] cjwatson: I like that, that sounds sensible [17:09] better than to copy it [17:09] I mean, to copy it only once [17:09] or else change base-installer to deliver a .deb as well [17:10] anyway, whatever's most straightforward [17:11] cjwatson: I will go with the include-as-submodule approach then I think [17:11] cjwatson: thanks, I will work on it today [17:11] (and update the bugreport) [17:11] ok, great [17:11] Robbie said he'd do the feature status side of things [17:11] [ACTION] mvo to include base-installer as update-manager submodule for CPU->kernel mapping [17:11] ACTION received: mvo to include base-installer as update-manager submodule for CPU->kernel mapping [17:12] howdy [17:12] python-robust-packaging is still waiting on mvo update ;) [17:13] mvo: any news? [17:13] but not really anything there that's in jeopardy, AIUI, since the agreement is to not change the stack [17:13] I think so [17:14] right, though it will affect several reasonably core components (by definition) [17:14] at least as of the last discussion we had [17:14] robbiew: yes, we will package stuff that is criticial infrastructure with "include-links" and defer the rest (debian is in the middle of a discussion about it) [17:15] mvo: so we'll need an FFE for this stuff, right? [17:15] robbiew: well, I would say its more a bugfix, but I let slangasek decide [17:15] they're bugfixes - so no [17:15] ok [17:16] the landscape stuff is done, at least in my opinion [17:16] * mvo nods [17:16] cloud-setup-in-installer is progressing [17:17] cjwatson can speak more to that...but nothing alarming at the moment [17:17] same with grub2 [17:17] and I'll let slangasek cover multiarch ;) [17:17] he's doing very well [17:17] I've never seen anybody work on multiarch this long whilst retaining their sanity [17:17] there are a couple of bits left of cloud, specifically the code to actually go and discover nodes on the local network and add them, and some more debconf questions in eucalyptus-{cloud,cc} [17:18] if those require FFes, let me know [17:18] multiarch - shown in red on the report, and that's accurate :( [17:18] and I asked a similar question by mail about grub-reboot/grub-set-default in grub2, which I think is making progress upstream [17:18] oh and Keybuk is landing a ton of boot stuff that will need FFEs [17:18] I'm landing them bits at a time [17:18] and maybe a call for testing via the ubuntu-boot ppa [17:19] through ubuntu-boot first [17:19] so there will be "new stuff in ubuntu-boot, plz test" ... then an FFE ... then move to main [17:19] while people are testing, I'll queue the next lot up in a second ppa [17:19] slangasek: is multiarch a deferral at this point? :-/ [17:19] since this is a blocker for proper sane fixing of alsa on amd64, I followed up to ubuntu-devel and proposed TheMuso a slightly less painful workaround [17:19] cjwatson: I have a weekend yet before I have to decide that [17:19] :) [17:19] Keybuk: posting to ubuntu-devel? [17:19] robbiew: yes [17:20] cool, thx [17:20] slangasek: alsa> I think I agree [17:20] obviously don't install from there just yet [17:20] ack [17:20] which is unfortunate, we were trying to *reduce* ia32-libs' size, but hey-ho [17:20] cjwatson: my fortune cookie yesterday said I could take on and accomplish ANYTHING I want to, so I figure that means multiarch will be done by Monday [17:20]