[15:57]  * lool waves
[15:57] <rickspencer3> hi lool
[15:57]  * slangasek waves
[15:58] <fader> o/
[15:59] <mvo> hello
[16:00] <mvo> I'm covering today for colin and robbie
[16:01] <slangasek> pgraner, ogra, Riddell, marjomercado, sbeattie, dendrobates, soren, Hobbsee, ScottK, apw: ping
[16:01] <soren> o/
[16:01] <rickspencer3> hi marjo
[16:02] <marjo> hi rickspencer3
[16:02] <pgraner> slangasek: rtg & apw will be covering for me
[16:02] <slangasek> pgraner: ack, thanks
[16:02] <Riddell> hola
[16:02] <njpatel> hey hey
[16:02] <rickspencer3> slangasek: I'll be covering for pitti
[16:03] <ogra> slangasek, lool is back so i think he will take mobile again from now on
[16:03] <slangasek> rickspencer3, ogra: ack
[16:03] <lool> ogra: You mean you dont attend all release meeting??
[16:03] <lool> :-P
[16:03] <slangasek> #startmeeting
[16:03] <ogra> i lurk
[16:03] <MootBot> Meeting started at 10:03. The chair is slangasek.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-08-21
[16:03] <ogra> but you got the info
[16:03] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-08-21
[16:03]  * apw waves
[16:04]  * apw is covering kernel
[16:04] <slangasek> [TOPIC] Actions from previous meetings
[16:04] <MootBot> New Topic:  Actions from previous meetings
[16:04] <rickspencer3> hi apw!
[16:04] <slangasek> unfortunately most of these action items were for people who aren't here today
[16:04] <soren> I can fill in for ttx.
[16:04] <slangasek> fader: did you and seb128 come up with a plan yet for the nautilus failures in the hw lab?
[16:05] <fader> slangasek: Not yet, no.
[16:05] <slangasek> ok, leaving that on the list then
[16:05] <slangasek> soren: right, did ttx follow up with you regarding the UEC setup doc? :)
[16:05] <rickspencer3> slangasek: fader: not that seb128 is on holiday next week as well
[16:05] <slangasek> rickspencer3: ok
[16:06] <fader> rickspencer3: Ah, thanks.
[16:06] <soren> slangasek: Er... Yes. About the AWS page:
[16:06] <soren> AWS pages for the 32 and 64 bit alphas have been submitted to amazon on Tuesday 9/18.  On the submission page it says "Important: After submitting your  information, it will be reviewed by AWS, during which time you will not be able to view or edit your submission. "  At this point I am 'not able to view'
[16:06] <soren> I == smoser. I'm just relaying stuff here. :)
[16:06] <slangasek> ok, so we're waiting on Amazon
[16:06] <soren> Yes.
[16:06] <soren> If nothing has happened yet on Monday, we'll go and poke them.
[16:07] <slangasek> how about the UEC setup doc?
[16:07] <soren> As for UEC setup page, I haven't personally worked on it. FeatureFreeze is a-coming, so it's been deferred a little bit.
[16:07] <slangasek> ok
[16:07] <soren> I have, however..
[16:08] <soren> Written a script that does almost all of it. It just needs some polish. I expect I'll put it in the eucalyptus package, so it should be /really/ simple from there.
[16:08] <slangasek> ah, spiff
[16:09] <slangasek> so it should be a short doc when the time comes :)
[16:09] <soren> Precisely.
[16:09] <slangasek> ok, moving along
[16:09] <slangasek> [TOPIC] QA Team
[16:09] <MootBot> New Topic:  QA Team
[16:09] <slangasek> fader, marjo: hello
[16:09] <fader> Howdy :)
[16:09] <fader> Hardware testing:
[16:09] <fader> http://people.canonical.com/~fader/hw-testing/current.html
[16:09] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:09] <fader> No new distro bugs have turned up this week.  We are still seeing the nautilus crash, but only on a subset of the systems that were showing this issue last week.  (Including in desktop image tests of two of the VMWare virtual machines.)
[16:09] <fader> I am monitoring this to see if the problem is simply intermittent or if it has actually been resolved on some systems.
[16:09] <fader> This past week mathben, our intern in the Montreal office, helped verify the existence or closure of some outstanding bugs on the System76 systems we have in the lab, adding logs and further testing to the bugs.
[16:09] <fader> https://bugs.launchpad.net/system76/+bugs
[16:10] <fader> Right now mathben is testing the updated kernel images from ogasawara for bug 404264.
[16:10] <fader> During this week I have been working with manjo to make a new and improved version of a bootable USB hardware testing image.  This will be used at the upcoming Atlanta Linux Fest to test a variety of available hardware.
[16:10] <fader> The intent here is to gather hardware compatibility data and, as much as is possible at the show, file bugs from the affected hardware.
[16:10] <fader> cr3 has recently added functionality in Checkbox to allow bug filing when a test failure occurs, so we will be using this feature to get bugs filed.
[16:10] <fader> Spec progress:
[16:10] <fader> karmic-qa-extended-audio-testing
[16:10] <fader> This is targeted for Alpha 5 and is on target.  The automated portion is complete, and the manual portion is mostly done.  I need to extend the manual test cases somewhat to ensure that they cover as many inputs and outputs on audio hardware as possible, after which the spec will be complete and ready for addition to Checkbox.
[16:11] <rickspencer3> (note even)
[16:11] <fader> Any questions about the testing or the checkbox audio spec?
[16:12] <slangasek> fader: nope - were you going to give status updates for the other specs on the list as well, or will marjo, or do we wait until next week for that?
[16:12] <marjo> * karmic-qa-increase-apport-adoption - Brian Murray worked with the Ubuntu Documentation team cleaning up the http://wiki.ubuntu.com/ReportingBugs page to address usability issues.
[16:12] <marjo> I will continue to nag the LP team.
[16:13] <marjo> * karmic-qa-metrics-based-testing - Beta available. Marc is in Phase I.I.
[16:13] <slangasek> I.I.?
[16:14] <slangasek> ah, that's in the spec :)
[16:14] <marjo> any questions?
[16:14] <slangasek> marjo: should the milestone target for karmic-qa-metrics-based-testing be pushed back to alpha-5 (or alpha-6)? it's evidently not done for alpha-4
[16:14] <cr3> slangasek: phase I has been done for a while, it should've probably been two specs
[16:14] <marjo> slangsek: I will look into that & update later
[16:15] <marjo> thx!
[16:15] <slangasek> cr3: ok - perhaps splitting it now is worthwhile, so I'm not polling about it for these meetings ;)
[16:15] <cr3> slangasek: sounds reasonable, will do. no objections marjo?
[16:16] <marjo> cr3: none; thx
[16:16] <slangasek> fader, marjo: thanks for the status update
[16:16] <slangasek> bit of agenda-shuffling, now; soren who's covering for the server team has asked to move up due to schedule conflicts, so we'll take him next
[16:17] <slangasek> [TOPIC] Server Team
[16:17] <MootBot> New Topic:  Server Team
[16:17] <slangasek> soren: go ahead
[16:17] <soren> server-karmic-eucalyptus-in-main: MIR processing in progress, unfortunately most of MIR team were in vacation recently
[16:17] <soren> and...
[16:17] <soren> server-karmic-cloud-cluster-computing: classads has been uploaded, condor is almost ready
[16:18] <slangasek> soren: what does that mean as far as mpich, which is mentioned prominently in the spec?
[16:18] <lool> There's a separate MIR for vtun
[16:18] <lool> Is this under control?
[16:18] <slangasek> for the MIR processing, do you think the remainder is on target for alpha-5?
[16:18] <lool> vtun is not very welcome in main, so I was wondering whether this was being discussed with the upstream euca folks
[16:19] <soren> slangasek: I'm not sure, to be honest. I believe so, but it's in the hands of the MIR team.
[16:19] <lool> slangasek: I'm not sure all of it will make it for A5, but probably some 2/3; we can probably bump stuff to main and milestone the final reviews for A6 in the worst case
[16:19] <soren> lool: It is being discussed, yes.
[16:19] <soren> I'm curious..
[16:19] <lool> There are some security reviews and simply a lot of packages
[16:20] <soren> Will we be considering the MIR process part of the various freezes as well?
[16:20]  * lool has no opinion on this
[16:20] <slangasek> soren, lool: ok, someone should take an action to get eucalyptus seeded in time for A5, and ask the archive admins to promote the other packages that are still MIR pending
[16:20] <slangasek> soren: should that be you, or do you want to give that to someone else on your team?
[16:20] <soren> I'm just wondering since AFAIR we didn't used to consider moves to main for the various alphas.
[16:20] <lool> Do we have the final version of euca in main yet?
[16:21] <soren> slangasek: I can take that action.
[16:21] <soren> lool: No.
[16:21] <slangasek> soren: if you mean the milestone freeze, no, we don't stop fixing up package components in freeze
[16:21] <lool> I'm not sure: do we want to promote the current and AFAICT completely unrelated version of euca to main?!
[16:21] <lool> Or will the new one land before A5?
[16:21] <slangasek> [ACTION] soren to get eucalyptus seeded in advance of A5 (~1 week before), and ask the archive admins to promote the other packages that are still MIR pending
[16:21] <soren> slangasek: Ok, didn't think so. Thanks for clarifying.
[16:21] <MootBot> ACTION received:  soren to get eucalyptus seeded in advance of A5 (~1 week before), and ask the archive admins to promote the other packages that are still MIR pending
[16:22] <soren> lool: The new one will land today.
[16:22] <lool> Ah that clarifies, thanks
[16:22] <soren> lool: Or Sunday... Before Monday, for sure! :)
[16:22] <slangasek> :)
[16:22] <slangasek> anything else we need to cover with the server team?
[16:23] <lool> soren: Sounds like a good week-end   :-)
[16:23] <soren> lool: I'm inches away from being done, I just have a load of real world things to deal with today and tomorrow :)
[16:24] <slangasek> [TOPIC] Desktop Team
[16:24] <MootBot> New Topic:  Desktop Team
[16:24] <slangasek> soren: thanks, you're off the hook now :)
[16:24] <slangasek> rickspencer3: hi
[16:24] <rickspencer3> hi
[16:24] <rickspencer3> I've made comments about each release bug here:
[16:24] <rickspencer3> https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:24] <rickspencer3> There are only two I am worried about:
[16:25] <soren> slangasek: Thanks, and thanks for adjusting the agenda.
[16:25] <rickspencer3> bug #403549
[16:25] <rickspencer3> as it is stuck upstream
[16:25] <rickspencer3> and
[16:25] <rickspencer3> bug #394447
[16:25] <rickspencer3> as we don't have the capability to debug ourselves - lack the hardware
[16:25] <rickspencer3> in terms of changes ...
[16:25] <rickspencer3> Expect some possible regressions as we land updates over the next few days:
[16:25] <rickspencer3> New Mesa (7.6)
[16:25] <slangasek> rickspencer3: well, I have the hardware and could arrange to give remote access to it if that were useful
[16:25] <rickspencer3> Possible new -intel
[16:25] <rickspencer3> Session menu
[16:25] <rickspencer3> desktopcouch on CD (via evolution-couch)
[16:26] <rickspencer3> CUPS 1.4 from svn head will be uploaded before FF (as it's final code, but not marked as such)
[16:26] <rickspencer3> slangasek: yes, if you could arrange that with Till, would be fabulous
[16:26] <slangasek> has he said that's what he needs to work on this?
[16:26] <rickspencer3> I think he has some confidence that upstream will fix it, but I get concerned when we don't have the capability ourselves
[16:26] <slangasek> [ACTION] slangasek to follow up with Till regarding hardware access for bug #394447
[16:26] <MootBot> ACTION received:  slangasek to follow up with Till regarding hardware access for bug #394447
[16:26] <rickspencer3> slangasek: yes, and also that hp often fixes these themselves
[16:27] <rickspencer3> also note from the Ubuntu desktop side:
[16:27] <rickspencer3>  No change to X server (sticking with 1.6)
[16:27] <rickspencer3> Somewhat above burndown, but team expects lots of work items to be closed over next week:  http://piware.de/workitems/desktop/karmic/report.html
[16:27] <slangasek> rickspencer3: why does desktopcouch landing warrant highlighting as a possible regression?  seems to be a small new package?
[16:28] <rickspencer3> slangasek: good point
[16:28] <rickspencer3> not a regression really, just a visible change
[16:28] <slangasek> oh; but it pulls in couchdb which isn't so small :(
[16:28] <rickspencer3> will interact with evolution and such
[16:28] <slangasek> ok
[16:28] <rickspencer3> yes, exactly ... it is new core technology on the desktop, you should be aware
[16:28] <rickspencer3> Riddell: do you want to cover Kubuntu status?
[16:29] <rickspencer3> (note that we've added Kubuntu release status to the desktop team release status page)
[16:29] <slangasek> [LINK] http://piware.de/workitems/desktop/karmic/report.html
[16:29] <MootBot> LINK received:  http://piware.de/workitems/desktop/karmic/report.html
[16:30] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:30] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:30] <Riddell> shall I paste the kubuntu points?
[16:30] <rickspencer3> Riddell: yes
[16:30] <rickspencer3> imho
[16:30] <Riddell> Kubuntu networking working well thanks to asac and others
[16:30] <Riddell> Impact of xsplash on Kununtu not clear, need to follow up with keybuk next week
[16:30] <Riddell> CD building currently broken on nvidia-common and python-apt
[16:30] <Riddell> Kubuntu Council voted for return to Konqueror as default browser
[16:30] <Riddell> Message Indicator KMail support waiting for new libindicate upload
[16:30] <Riddell> Currently blocking on GPSD main inclusion report Bug #409796
[16:31] <mvo> Riddell: could you tell me about the issue with python-apt (after the meeting or out-of-band)?
[16:31] <davidbarth> Riddell: on xsplash you can follow-up with agateau next week; he can help with integrating kubuntu reqs
[16:31] <Riddell> mvo: see the CD build logs, packagekit issue
[16:32] <Riddell> davidbarth: ok, I also scheduled a meeting with keybuk inviting you a few minutes ago
[16:32] <slangasek> rickspencer3: mm, the comments on bug #396448 on the status page are wrong; this bug causes an intrusive popup at every login for the users affected (not the same as bug #386699, which has the same comment)
[16:32] <mvo> Riddell: oh, right - glaztor is on it
[16:32] <Riddell> mvo: I never doubted him :)
[16:33] <rickspencer3> slangasek: ok ... I just copy and pasted from pitti's last comment, as it seemed he wasn't too concerned
[16:33] <slangasek> Riddell: what's broken with python-apt?  I saw that nvidia-common is being resolved
[16:33] <rickspencer3> can we give pitti an action to follow up?
[16:33] <mvo> slangasek: it break packagekit (it uses some internal api) - I can have a look later
[16:34] <slangasek> ah, mvo asked that question while I was wading in scrollback ;)
[16:34] <slangasek> ok
[16:34] <slangasek> [ACTION] pitti to follow up on bug #396448, which should not be marked as "not a release blocker" in the status report
[16:34] <MootBot> ACTION received:  pitti to follow up on bug #396448, which should not be marked as "not a release blocker" in the status report
[16:34] <slangasek> rickspencer3: done
[16:34] <rickspencer3> kthx
[16:35] <slangasek> rickspencer3: regarding the upstream bug 402169, 402175 - they're also trivial patches; if you want support from foundations on this to work up the patches, we can probably oblige
[16:35] <rickspencer3> slangasek: ok
[16:36] <rickspencer3> that would be sweet
[16:36] <slangasek> [ACTION] slangasek to look at Foundations providing patches for the 64-bit build failures
[16:36] <MootBot> ACTION received:  slangasek to look at Foundations providing patches for the 64-bit build failures
[16:36] <slangasek> (probably means me, as the erstwhile Debian Alpha porter :)
[16:36] <slangasek> anyone else have questions for Desktop Team?
[16:37] <rickspencer3> slangasek: can you give slangasek an action to make those patches
[16:37] <rickspencer3> ;)
[16:37] <slangasek> rickspencer3: btw, if gpm is no longer handling brightness, what is?  The last I saw (during the sprint), gpm /was/ still doing it, and if it's going elsewhere I'll need to know for follow-through on a couple of unrelated bugs :)
[16:38] <rickspencer3> slangasek: I forget, but that's on the Dx team's plate, really
[16:38] <rickspencer3> davidbarth should be able to speak to that
[16:38] <rickspencer3> we're just waiting on them
[16:38] <slangasek> ok; will follow up out of band
[16:39] <slangasek> [TOPIC] Mobile Team
[16:39] <MootBot> New Topic:  Mobile Team
[16:39] <slangasek> lool: hi
[16:39] <lool> hey
[16:39] <lool> [link] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic as usual; with a new per spec sub report (with its own bugs  :-)
[16:39] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic as usual; with a new per spec sub report (with its own bugs  :-)
[16:39] <slangasek> rickspencer3, Riddell: thanks
[16:39] <lool> Highlights:
[16:39] <lool> - good progress on getting final kernels (with naming etc.) in archive
[16:39] <lool> - livefs builder fixed; first working imx51 image came out today
[16:39] <lool> - armv7 buildds being deployed
[16:39] <davidbarth> rickspencer3: the patch is on the packaging queue, in the bug report
[16:39] <lool> - overall still relatively short on ARM developer hardware as the boards get obsoleted and new+working boards remain hard to get
[16:39] <lool> - UNR in a good shape, except for a bunch of small bugs introduced with the new upstream versions; being worked on by njpatel

[16:40] <mdz> bug 410655 is one davidm mentioned he was concerned about
[16:40] <ogra> heh
[16:40] <mdz> though it's not on your status page or on https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus
[16:40] <lool> Yes, it's one of these bugs we have with UNR
[16:40] <mdz> dbarth? njpatel?
[16:40] <lool> The new UNR introduced a lot of crashers in various places
[16:40] <njpatel> mdz: I thought I'd fixed it but apparently it's still there. I'll reconfirm and try to fix it again
[16:41] <ogra> why is that still private thogh
[16:41] <ogra> *though
[16:41] <lool> Some were addressed just after A4; others are still being addressed
[16:41] <ogra> retrace is done
[16:41] <mdz> (I've fixed the privacy flag now)
[16:41] <ogra> thanks
[16:41] <njpatel> mdz: I've updated that page with the bug when I was made aware it was still an issue
[16:41] <slangasek> lool: any idea how long the armv7 buildd roll-out is going to take?  IIRC the toolchain defaults were targeted for alpha5, so the buildds obviously need to be up and running before that
[16:41] <lool> mdz: milestoning it, thanks
[16:41] <davidbarth> mdz: we've had a couple like this one and njpatel is looking into it
[16:42] <lool> slangasek: IS said about 2 weeks last week
[16:42] <lool> So should happen over next week
[16:42] <slangasek> so, cutting it rather close for A5
[16:42] <slangasek> are the toolchain changes themselves staged somewhere and ready to be uploaded?
[16:42] <lool> slangasek: As I note,I think we'll change them just after A5 rather than just before
[16:42] <slangasek> ok
[16:42] <lool> Doesn't gain us anything just before
[16:42] <lool> slangasek: No, we will push them to a PPA as soon as the buildds appear
[16:43] <lool> The flags are documented in a toolchain discussions bug
[16:43]  * slangasek nods
[16:44] <mdz> lool/davidbarth/njpatel: can you speak to the messaging indicator in UNR (or lack thereof)? Mark asked about this the other day
[16:44] <davidbarth> mdz: yes, the design is compatible
[16:44] <njpatel> mdz: I need to update the default panel configuration with it. Also need the new FUSA, so was waiting for that to be included in main before re-doing the gconf-defaults in ubuntu-netbook-remix-default-settings
[16:45] <lool> mdz: Sorry which package is that?
[16:45] <mdz> so this is planned to do before FF?
[16:45] <lool> netbook-remix: * (indicator-messages)
[16:45] <njpatel> mdz: yes
[16:45] <lool> Oh in the config
[16:45] <lool> Right that's an omission
[16:45] <njpatel> lool: indicator-applet
[16:45] <njpatel> & indicator-messages
[16:45] <ogra> + fusa :)
[16:46] <njpatel> well, indicator-applet-session or something like that afaik
[16:46] <lool> I'd like to note that we discussed a long term fix for seeds getting out of sync during the sprint
[16:46] <njpatel> :)
[16:46] <ogra> yeah
[16:46] <ogra> new name ...
[16:46] <njpatel> new code
[16:46] <ogra> new world \o/
[16:46] <lool> And cjwatson said we needed a new germinate feature to do this properly which would take a couple of months to happen and we agreed we'd simply continue manually syncing until then
[16:47] <lool> (But here it's gconf settings not packages so not the same things again)
[16:47] <mdz> lool: in the meantime, we'll need to track this more closely I think
[16:47] <lool> Yes, I did ask for a heads up when things would be landing but I realize it's not proper tracking
[16:48] <lool> Perhaps I should add that to our weekly meetings or similar; suggestions welcome
[16:48] <lool> For the seeds I'll subscribe to the desktop ones and read commits
[16:48] <slangasek> should there be an action item for this messaging indicator discussion, or is there a bug # that should be targeted to karmic & milestoned?
[16:49] <njpatel> slangasek: I should file a bug and target it. there wasn't a blueprint
[16:49] <njpatel> lool: what should I file against?
[16:49] <lool> I guess we could track it as a bug or as an action item that we're waiting on new FUSA and will change the gconf settings afterwards
[16:49] <lool> njpatel: unr-default-settings
[16:49] <njpatel> lool: coolio, I'll do that before I log off today
[16:50] <slangasek> [ACTION] njpatel to file bug against unr-default-settings for tracking of message indicator status
[16:50] <MootBot> ACTION received:  njpatel to file bug against unr-default-settings for tracking of message indicator status
[16:50] <slangasek> anything else to cover for Mobile?
[16:50] <ogra> there will be lots of armel bugs coming in shortly now that we actually can build images
[16:50] <lool> Filed as 417001
[16:51] <lool> Just got word that oo.o doesn't start on armel in the new image produced today
[16:51] <slangasek> [TOPIC] Kernel Team
[16:51] <MootBot> New Topic:  Kernel Team
[16:51] <lool> Will file a bug
[16:52] <lool> Well ogra will  :)
[16:52] <slangasek> lool: oh, do we need to discuss that further?
[16:52] <lool> No, too early
[16:52] <lool> Just discovered
[16:52] <slangasek> ok
[16:52] <slangasek> lool, ogra: thanks
[16:52] <slangasek> rtg, apw: hello
[16:52] <ogra> i booted the first armel image 30min ago :)
[16:52] <ogra> give me some time ;)
[16:52] <apw> slangasek, here
[16:52] <apw> Overall kernel team status is summarised at the URL below,including the bugs called out. AppArmor has patches in testing.  Eucalyptus aoe panic has fixes ready for commit.  The installer bug has patches out for testing.  The remaining two are pending.
[16:52] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[16:52] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[16:52] <lool> ogra: You have, just wanted to mention it
[16:52] <apw> All items which impact the distro release schedule seem to be on track at this time.  The ARM enablement branches have undergone some major work this week getting the naming acceptable to the archive admins and the installer.  We should see uploads for both soon.
[16:54] <apw> All the issues which were preventing packages being accepted (lost copyright etc) should be resolved now and in the new uploads.
[16:55] <slangasek> apw: status on the top two kernel bugs seems unchanged since last week (and for several weeks before); are these bugs really as stalled as they appear from Launchpad?
[16:55] <slangasek> thats bugs #359338, #290153
[16:55] <apw> the first one has progressed, the status should end 'patches for the workaround are in progress'
[16:56] <slangasek> ok
[16:56] <apw> the second is stalled currently, though symptoms are majorly improved in karmic latest kerenls
[16:56] <apw> that should have been 'in testing'
[16:57] <apw> we have a fair number of regression-potentials which are in work
[16:57] <apw> the enablement branch work has thrown a number of things off track in the short term
[16:58]  * slangasek will triage the regression-potential list further this week, to get higher visibility on some of those for the release
[16:59] <slangasek> any other questions for the kernel team?
[16:59] <slangasek> I think everyone involved has a good idea where the armel packages stand at this point, at least :)
[16:59] <ogra> yes
[16:59] <ogra> should all be good now
[16:59]  * apw crosses everything
[17:00] <ogra> thanks a lot for a few weeks of hard work to the kernel team
[17:00] <ogra> that was quite some effort
[17:00] <apw> it _was_ a lot of work, but going forward we should be in a more maintainable place
[17:00] <ogra> (meta just hit the archive for imx51
[17:00] <ogra> )
[17:00] <slangasek> yes, thanks to everyone who's been putting work in on those packages
[17:00] <ogra> it would really be good to be able to build images earlier next release and i think the decoupled trees will make that possible
[17:01] <ogra> simply we can acrry them forward outdated for the first alphas until the new patcsets are there
[17:01] <ogra> *carry
[17:01] <apw> yes we can cope with more deviant invasive code in this new model without impacting x86
[17:01] <slangasek> [TOPIC] Foundations Team
[17:01] <MootBot> New Topic:  Foundations Team
[17:02] <mvo> Up-to-date status can be found here:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic
[17:02] <slangasek> apw: well, let's hope we might also have less deviant code in the future. :)
[17:02] <slangasek> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic
[17:02] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic
[17:02]  * apw will die if we don't
[17:02] <ogra> high hopes :)
[17:02] <mvo> >   * Foundations
[17:02] <mvo> >    * Bug:384579: Linux thinks there’s a floppy drive when there’s not. Probing slows down bootup by almost a minute
[17:02] <mvo>        No updates this week.
[17:02] <mvo> >    * Bug:403021: OEM install: black screen with cursor on login
[17:02] <mvo>        Developer (evand) assigned for investigation.
[17:02] <mvo> >    * Bug:402178: gzopen64 implicitly converted to pointer
[17:02] <mvo>        Not investigated yet. The package seems to be related to X stuff, so
[17:02] <mvo> maybe Bryce should look at this.
[17:02] <mvo> >    * UbuntuSpec:foundations-karmic-apturl-policy (overdue, mvo on leave)
[17:02] <mvo>        Should be moved to "Implemented" (its currently in beta-available), the code changes to software-properties seem to work fine
[17:02] <mvo> >    * UbuntuSpec:foundations-karmic-robust-python-packaging
[17:02] <mvo>        Slow progress, Debian is working on it, in the meantime we will convert critial packages to use DH_PYCENTRAL=include-links
[17:02] <mvo> >    * UbuntuSpec:foundations-karmic-upgrade-support-in-landscape
[17:02] <mvo>        The update-manager side of the implementation is ready to use for landscape
[17:02] <mvo> >    * UbuntuSpec:foundations-karmic-cloud-setup-in-server-installer
[17:02] <mvo>        On track for delivery in Alpha 5
[17:02] <mvo> >    * UbuntuSpec:foundations-karmic-grub2
[17:03] <mvo>        Practically done, but there are some additional changes that enhance the
[17:03] <mvo>        boot experience that are targeted to be in for Alpha 5.
[17:03] <mvo> >    * UbuntuSpec:foundations-karmic-multiarch-support
[17:03] <mvo>        Slow progress on the apt side
[17:03] <mvo> slangasek: you may want to add more info about the multiarch spec :)
[17:03] <slangasek> multiarch - slow progress; Guillem has had limited availability to work on the dpkg side, as of yesterday he's done some more work but it's too early to tell if we'll really have something that can land in time for karmic
[17:04] <mvo> on the bright side, lots of interesst in it now, if it does not make karmic, we should get it for karmic+1
[17:04] <slangasek> TheMuso has posted to ubuntu-devel about hedging bets against multiarch by getting pulseaudio building with biarch, the list of packages affected makes me cringe and inspires me to try harder on multiarch :(
[17:05] <lool> on Bug:384579 I think there's a confirmed upstream patch; would be nice to pull it
[17:06] <sbeattie> lool: actually, on bug 384579, I've pulled it and packaged it; just needs sponsorship.
[17:06] <lool> sbeattie: Yeah that's how I noticed
[17:06] <slangasek> mvo: bug #402178> yes, it's an X dependency, but given that I'm already volunteering to take on the even more desktopy build failures, I figured that one was definitely up our alley :)
[17:06] <lool> Didnt see it was just waiting for sponsorship though
[17:07] <mvo> slangasek: ok
[17:07] <slangasek> mvo: bug #384579 - seems sbeattie has a patch, perhaps someone should look at sponsoring this
[17:07] <mvo> slangasek: I can have a look after the meeting
[17:07] <slangasek> ta
[17:07] <slangasek> mvo: alternatively, I'll be seeing sbeattie in person in an hour or so and could sponsor it in realtime there :)
[17:08] <mvo> slangasek: either way is fine, lets see who manages to upload it first ;)
[17:09] <slangasek> ok, I'm done digesting
[17:09] <slangasek> anyone else have questions for Foundations?
[17:10] <slangasek> mvo: btw, if you think foundations-karmic-apturl-policy should bemoved to 'Implemented', I can think of no better person to switch it? :)
[17:10] <mvo> slangasek: heh :) I will do that, I tend to leave my stuff too long in beta-available (just as my version number are below 1.0)
[17:11] <slangasek> :)
[17:11] <slangasek> [TOPIC] MOTU
[17:11] <MootBot> New Topic:  MOTU
[17:11] <slangasek> mvo: thanks
[17:11] <slangasek> ScottK2: around?
[17:12] <slangasek> any other motu-release folks in the room?
[17:12] <slangasek> (ISTR from the mailing list discussion that this was about the time ScottK2 was going to have limited availability)
[17:12] <slangasek> [TOPIC] AOB
[17:12] <MootBot> New Topic:  AOB
[17:13] <slangasek> anything else that we should discuss here?
[17:13] <slangasek> some may notice "ISO size" dropped off the agenda
[17:13] <slangasek> I decided it wasn't worth having a monologue from me every week about the importance of controlling ISO size
[17:14] <slangasek> but it's still important, I'm just not going to harp on it to no effect every week :)
[17:14] <apw> slangasek, perhaps just report the delta?
[17:15] <slangasek> apw: well, the key point is "everything's too big, we have no room for langpacks", and that's been status quo for weeks
[17:16] <slangasek> #endmeeting
[17:16] <MootBot> Meeting finished at 11:16.
[17:16] <lool> slangasek: thanks
[17:16] <slangasek> I see everyone's wandered away from their desks already for coffee, then. :)
[17:16] <apw> thanks slangasek
[17:16] <slangasek> thanks, folks
[17:18] <mvo> thanks slangasek!
[17:57] <indus> hi