[03:22] <BoNiTo> hi
[03:22] <BoNiTo> I need some help :)
[03:23] <BoNiTo> I installed ubuntu-x-swat repository trying to fix the flickering or my video card
[03:23] <BoNiTo> now it just dump me to the text login screen
[03:24] <BoNiTo> some1 know if I can ppa-purge this repository?
[12:36] <apw> tseliot, i seem to be having trouble with the dell 10v dead area stuff
[12:36] <apw> its doesn't seem to be taking my area thingy, has anything changed there?
[12:37] <apw> yeah feels like its not longer a feature
[12:37] <apw> could we have lost the patch?
[12:43] <apw> tseliot, user error ... that 8 is an input channel and mine have randomly moved about today
[13:16] <tseliot> apw: the patch should be there. Did you execute the xinput command in a script (pointing to device 8)?
[13:17] <apw> yeah i used 8, which its not now, its 6, but that command takes the name as text, much better
[13:24] <tseliot> right
[14:01] <apw> tseliot, bryce, either of you got any bluetooth keyboards/mice ?  considering some fixes for them as they apparently appear but never dissappear and fill the X device slots ...
[14:01] <apw> so wondering if either of you have stuff you could test the proposed fixes with?
[14:02] <tseliot> apw: sorry, I don't have any
[14:02] <apw> damn i was hoping you of all people might have
[14:07] <tseliot> let's wait for bryce
[14:07] <tseliot> tjaalton: do you have one? ^^
[14:08] <tjaalton> tseliot: nope..
[14:09] <tseliot> ok, thanks anyway
[14:10] <tjaalton> should get one for my ps3 though
[15:06] <Ng> so if you'd been dragging a window around with alt-button1 and X got a bit confused and kept that pointer and wouldn't let you click on anything, what would you do? :)
[15:06] <Ng> your available tools are a terminal and/or a console :)
[15:09] <Ng> it appears to persist across suspending
[15:22] <apw> try hitting all the meta keys, crtl, alt etc to make sure they are all released
[15:23] <Ng> no joy :/
[15:23] <jcristau> sounds like the window manager getting confused and not releasing a grab
[15:30] <Ng> jcristau: another interesting idea. bouncing compiz in the face didn't help (although maybe it wouldn't)
[17:19] <bryce> no bluetooth gear myself
[17:51] <bryce> jbarnes, mind taking a look at https://bugs.freedesktop.org/show_bug.cgi?id=24383 ?   It's our one last release-important X bug on -intel
[17:51] <bryce> there's a patch for it, however I don't want to include it without upstream's review
[17:54] <jbarnes> sounds like the regen bug?
[17:54] <jbarnes> oh hm yeah the patch makes some sense
[17:55] <jbarnes> bryce: I'll push that patch upstream
[17:55] <jbarnes> feel free to include it
[17:56] <bryce> jbarnes, excellent thanks
[19:00] <jcristau> jbarnes: maybe cherry-pick to 2.9 as well?
[19:00] <jbarnes> jcristau: sure I guess that makes sense
[19:13] <rickspencer3> bryce, hi, have all three of those radeon bugs been resolved now?
[19:14] <bryce> rickspencer3, 2 of them have.  Need to check in on the 3rd
[19:14] <rickspencer3> is the third one for that ancient chip?
[19:14] <bryce> rickspencer3, aforementioned discussion is regarding the KDE/X bug listed on your karmic status page; fix was taken upstream so I'm uploading it presently.  :-)
[19:14] <bryce> rickspencer3, that's right
[19:15] <rickspencer3> so is the last bug a ship stopper?
[19:15] <bryce> rickspencer3, also I took a look at his configuration closer and it's a bit non-standard so I'm having him create a cleaner test environment to re-verify.  I'll follow up.
[19:15] <rickspencer3> ok
[19:15] <rickspencer3> so, seems that there are no further issues?
[19:15] <bryce> not in my opinion
[19:16] <rickspencer3> and xorg stack is more or less in the can, modulo this upload that you would be dong if I weren't pestering you for status?
[19:16] <bryce> there are still some bugs that people are passionate about, but to be honest I think people have some widely varying ideas of what constitutes "show stopper"
[19:16] <rickspencer3> hmm
[19:16] <rickspencer3> are these bugs new due to the mesa update, or unrelated?
[19:16] <bryce> oh completely unrelated
[19:17] <rickspencer3> well then
[19:17] <rickspencer3> that's just normal "fix bugs in priority order" work
[19:17] <bryce> most of these that I'm looking at right now are long-standing issues that have had patches posted to them in recent months, that I just hadn't had time to review before now
[19:17] <bryce> right
[19:17] <rickspencer3> alrighty, talk to you later
[19:17] <bryce> I'm just harvesting targets of opportunity that look safe
[19:17] <rickspencer3> righto
[19:17] <bryce> rickspencer3, great, cya
[19:17] <rickspencer3> sounds great
[20:23] <ilmari> huh, X eats 100% CPU and can't switch VTs when started before acpid
[20:23] <jcristau> it has nothing to do with acpid.
[20:23] <ilmari> restarting X after acpid has started or adding "and started acpid" to the gdm upstart job fixes it
[20:24] <jcristau> it still has nothing to do with acpid.
[20:24] <ilmari> might be something else that it needs to wait for
[20:25] <jcristau> that's bug 439138
[20:26] <ilmari> cryptsetup?
[20:28] <ilmari> ah
[20:30] <ilmari> okay, but X still complains about not being able to open acpid.socket
[20:30] <ilmari> (if gdm is started before acpid, that is)
[20:31] <ilmari> what does X not being able to open ACPI affect?
[20:31] <jcristau> nothing
[20:32] <jcristau> well it generates wrong impressions like yours that it matters
[20:34] <ilmari> why does it try to open acpi or apm then?
[21:03] <Afzal> hi! need help for nouveau-kernel-source & xserver-xorg-video-nouveau in my newly upgraded ubuntu9.10
[21:03] <Afzal> any suggestion  is appreciated


[10:38] <aryanharitsh> Hii everyone..I am a Google Code In Aspirant...I Want To Contribute To Your Projects..Can Anyone Help Me?


[09:49] <huats> morning
[15:59] <seb128> hey
[15:59] <robbiew> 0/
[15:59]  * marjo waves
[15:59]  * robbiew settles in
[16:00] <robbiew> for the ride...yeehaw!
[16:00] <Daviey>  o/
[16:00] <robbiew> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is robbiew.
[16:00] <jdstrand> o/
[16:00] <ogra> moo
[16:01]  * mathiaz waves
[16:01]  * robbiew will officially start meeting in 4min
[16:02] <robbiew> 3min
[16:03] <robbiew> 2min
[16:04] <robbiew> 1min
[16:04]  * jdstrand wonders if there will be a 10 second countdown
[16:04] <robbiew> lol
[16:04] <ogasawara> the suspense is killing me
[16:04] <ScottK> \o
[16:04]  * jdstrand is ready to jump out of the gate
[16:05] <robbiew> [TOPIC] 10.10
[16:05] <MootBot> New Topic:  10.10
[16:05] <jdstrand> \o/
[16:05] <robbiew> I'm not going to paste the usual links...they are in the agenda
[16:05] <robbiew> so let's jump in
[16:05] <robbiew> [TOPIC] QA Team Report
[16:05] <MootBot> New Topic:  QA Team Report
[16:06] <marjo> # Hardware testing
[16:06] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:06] <marjo> Laptops
[16:06] <marjo>     passed   43 (91%)    failed    0 ( 0%)    untested  4 ( 9%)
[16:06] <marjo> Servers
[16:06] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:06] <marjo>     passed   56 (86%)    failed    0 ( 0%)    untested  9 (14%)
[16:06] <marjo> Netbooks
[16:06] <marjo>     passed   14 (93%)    failed    0 ( 0%)    untested  1 ( 7%)
[16:06] <marjo> Desktops
[16:06] <marjo>     passed    9 (60%)    failed    0 ( 0%)    untested  4 (40%)
[16:06] <marjo> results are looking good, except for desktops blocked on resources; been escalated
[16:07] <marjo> Boot Performance Week of 5/08/2010-12/08/2010
[16:07] <marjo> ---------------------------------------------
[16:07] <marjo> http://people.canonical.com/~cr3/daily-bootcharts/averages.html
[16:07] <marjo> Total number of systems with regressions: 1 out of 49 systems
[16:07] <marjo> Specific System(s):
[16:07] <MootBot> LINK received:  http://people.canonical.com/~cr3/daily-bootcharts/averages.html
[16:07] <marjo> Asus Eee PC 900 (Laptop)[1]     Desktop regressed: 10.39s
[16:07]  * slangasek sneaks into the back
[16:07] <robbiew> do we do any bluetooth testing as part of the hardware tests?
[16:08] <marjo> robbiew: manual testing only
[16:08]  * jdstrand nods to slangasek
[16:08] <robbiew> how recently have we tested it...because it appears to be broken currently :/
[16:08] <robbiew> though I know it WAS working
[16:09] <marjo> robbiew: we're going to do manual testing based on alpha3, so we'll report again later
[16:10] <robbiew> ok...I think I already know the results :P
[16:10] <robbiew> one more question
[16:10] <robbiew> are all the machines in the daily-bootcharts running Ubuntu Desktop?
[16:10] <robbiew> or are some running UNE
[16:10] <fader_> robbiew: We do bluetooth as part of the manual tests
[16:11] <robbiew> is there an echo in here?
[16:11] <robbiew> lol
[16:11] <fader_> Heh, sorry, missed marjo's answer :)
[16:11] <marjo> robbiew: per earlier agreement, we run desktop edition on desktops & UNE on netbooks
[16:11] <ameetp> robbiew:  daily-bootcharts some run UNE
[16:11] <robbiew> okay, perfect
[16:11] <marjo> robbiew: is this report format ok with you?
[16:11] <robbiew> could we somehow note the ones running UNE...doesn't need to be fancy
[16:12] <robbiew> a simple "*" by the name would work for me
[16:12] <ameetp> robbiew: ack.  I will make that edit
[16:12] <robbiew> thnx
[16:12] <marjo> robbiew: we'll do for next report
[16:12] <marjo> Spec Status
[16:12] <marjo> http://people.canonical.com/~pitti/workitems/maverick/canonical-platform-qa-ubuntu-10.10-beta.html
[16:12] <marjo> qa-maverick-mago-daily, 17% complete
[16:12] <marjo> qa-maverick-automated-server-testing, 0% complete, Stalled due to UEC testing.
[16:12] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-platform-qa-ubuntu-10.10-beta.html
[16:12] <robbiew> marjo: yeah...looking good
[16:13] <marjo> robbiew: that's it for 10.10
[16:13] <robbiew> ameetp: would also be good if we could have separate averages for machines running Ubuntu Desktop and those running UNE
[16:13] <robbiew> marjo: thnx
[16:14] <robbiew> ameetp: asking so that we can catch any regressions that affect UNE or Desktop *only*...helps in chasing down the problem
[16:14] <robbiew> any questions for QA?
[16:14] <ameetp> robbiew: sure
[16:14] <ScottK> There was some discussion about getting some Kubuntu boot charts in there a few weeks ago.
[16:14] <ScottK> That'd still be nice.
[16:15] <robbiew> there was?.../me must have been out
[16:15] <marjo> ScottK: agree, still investigating
[16:15] <ScottK> OK.
[16:15] <robbiew> ScottK: sorry...or I would have made a note of it
[16:15] <ScottK> No problem.  marjo's on it.
[16:15] <robbiew> and by marjo...that means ameetp :P
[16:16] <robbiew> [TOPIC] Security team update
[16:16] <MootBot> New Topic:  Security team update
[16:16] <marjo> robbiew: of course, everyone knew that!
[16:16] <robbiew> heh
[16:16] <jdstrand> hi
[16:16] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Maverick
[16:16] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Maverick
[16:16] <jdstrand> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-security.html
[16:16] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-security.html
[16:16] <jdstrand> No milestoned bugs. As I've mentioned before, blueprints for the cycle are generally slipping due to high/complicated security update load. That said, we pushed before FF for several time-sensitive work items and got them in. For what remains we will continue to get to what we can while postponing others.
[16:17] <jdstrand> Next week, mdeslaur will be uploading -proposed packages for security-m-tls-renegotiation-updates, our last remaining essential blueprint.
[16:17] <jdstrand> As for milestoned blueprints, I finished the libvirt 0.8.3 merge this week and kees is continuing to work on his 4 remaining work items for the arm security blueprints. It is slow going without physical access to hardware though.
[16:17] <jdstrand> We have one release-targeted bug: bug #545795. There is a patch for pci devices, but it needs upstream review, which I hope to push upstream today or early next week. I just need to find the time to work on the hostdev part.
[16:18] <jdstrand> that's it from me
[16:18] <robbiew> thnx jdstrand
[16:18] <robbiew> questions for security?
[16:19] <robbiew> [TOPIC] Kernel team update
[16:19] <MootBot> New Topic:  Kernel team update
[16:19] <ogasawara> Overall Kernel Team status is summarised at the first URL below, including the item(s) called out in the agenda.  Our burndown chart for Beta is at the third URL, and our overall burndown chart is at the fourth:
[16:19] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[16:19] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[16:19] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10-beta
[16:19] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-ubuntu-10.10-beta.html
[16:19] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg
[16:19] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10-beta
[16:19] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-ubuntu-10.10-beta.html
[16:19] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg
[16:19] <ogasawara> On the specs noted in the agenda, status is as follows:
[16:19] <ogasawara> * kernel-maverick-apparmor: 83% complete.  The remaining userspace log parsing bits are progressing nicely and should be compelted by Beta.
[16:19] <ogasawara> * kernel-maverick-pv-ops-ec2-kernel: 75% complete.  The -virtual kernel has been enabled as a pv-ops kernel on EC2.  This does not include the pv-on-HVM drivers which are required for Amazon's Compute Cloud.  pv-on-HVM is currently being evaluated and we expect this to be completed in time for Beta.
[16:20] <ogasawara> On the bugs noted in the agenda, status is as follows:
[16:20] <ogasawara> Bug 591941 - mpoirier is discussing a resolution with the upstream developers.  It appears this issue was the result of a separate upstream fix.
[16:20] <ogasawara> Bug 595489 - A patch has been accepted upstream and expected to land in upstream stable v<IP_ADDRESS>. We'll rebase Maverick to v<IP_ADDRESS> which will subsequently resolve this issue.  I expect this to be resolved prior to Beta.  For Lucid, the patch is already Fix Committed and undergoing the SRU process.
[16:20] <ogasawara> Bug 605488 - Currently assigned to lag and under investigation.  It's proving difficult to reproduce at the moment.
[16:20] <ogasawara> Bug 605739 - Believed to be resolved in the latest linux-ti-omap4-2.6.34-903.7 kernel. Just awaiting verification before closing.
[16:21] <ogasawara> Bug 554569 - The patch in question is already included in the latest Maverick kernel. I've posted a comment to the bug and marked it Fix Released.
[16:21] <ogasawara> As a general status, we've stabilized on upstream v2.6.35 final and will pull 2.6.35.y stable updates from here on out.  We've already rebased to upstream stable v<IP_ADDRESS>, ie linux-2.6.35-15.21, and I expect upstream stable v<IP_ADDRESS> to land relatively soon.  We are above the trend line for our Beta release burndown chart but below the trend line overall.  The remaining Beta release work items are not release critical.
[16:21] <ogasawara> Questions?
[16:22] <robbiew> and we are waiting for the TB's decision on dropping SPARC and IA64?
[16:22] <ogasawara> robbiew: yes, per ScottK's request.
[16:22] <ScottK> It's on their agenda, so it seemed reasonable.
[16:22] <ogasawara> robbiew: but I'm ready to pull the trigger :)
[16:23]  * robbiew thought they already decided this via a vote on the mailing list...but maybe that was a vote to start the process
[16:23] <robbiew> ScottK: ack...no worries
[16:24] <robbiew> any questions for kernel?
[16:24] <robbiew> thanks ogasawara
[16:24] <robbiew> [TOPIC] Foundations
[16:24] <MootBot> New Topic:  Foundations
[16:24] <robbiew> cjwatson is out
[16:25] <robbiew> and I don't think there's a fill-in
[16:25] <robbiew> luckily I know the team lead VERY well...;)
[16:25] <Daviey> O_o
[16:26] <ScottK> Issue for foundations.  I think Bug #617359 needs cjwatson to have a look.
[16:26] <robbiew> noted
[16:26] <robbiew> [ACTION] Foundations needs to review bug #617359
[16:26] <MootBot> ACTION received:  Foundations needs to review bug #617359
[16:26] <jdstrand> I actually have something for foundations
[16:26] <robbiew> go ahead...I'll try to cover
[16:26] <jdstrand> I was going to ask the server team, but foundations is probably who will fix it
[16:27] <jdstrand> basically, bug #563916 and the related bug #613562 are *really painful* for servers on lucid and presumably maverick
[16:27] <Daviey> jdstrand, Thanks.. I'll make a note to track them.
[16:29] <robbiew> jdstrand: thnx...I'll chase them down
[16:29] <jdstrand> I really just wanted to bring those up since it affects server systems primarily, but also others where you can't use plymouth themes
[16:29] <jdstrand> (well)
[16:29] <jdstrand> robbiew: thanks
[16:30] <jdstrand> it is kinda important to be able to interact with fsck, whether one uses plymouth themes or not
[16:30] <robbiew> [ACTION] Foundations needs to follow-up on bug #563916 and #613562
[16:30] <MootBot> ACTION received:  Foundations needs to follow-up on bug #563916 and #613562
[16:31] <robbiew> any other work you folks want to assign me?
[16:31] <robbiew> :P
[16:31]  * jdstrand looks around
[16:31] <robbiew> heh
[16:31] <ScottK> We need to talk about Python too.
[16:31] <robbiew> okay
[16:31] <robbiew> talk away
[16:31] <robbiew> :)
[16:31] <ScottK> doko and barry want 2.7 as a supported (but not default) version in Maverick.
[16:32] <ScottK> I agreed not to curl up in a ball and scream over it since barry promised to fix stuff.
[16:32] <slangasek> jdstrand: AFAIK there's no situation in which you can't use a plymouth theme that will let you interact with fsck; this is entirely an artifact of the choice to disable 'splash' at boot time (and even then, hitting 'esc' is enough to pull up the regular theme)
[16:32] <ScottK> We're now past FFe and it didn't get enabled as a supported version.
[16:32] <slangasek> jdstrand: (I absolutely agree with you that this is a problematic bug, I just disagree with your characterization of it, which is a common one :)
[16:32] <robbiew> hmm...fair point
[16:33] <ScottK> So that needs to get decided and decided soon.
[16:33] <robbiew> agreed
[16:33]  * ScottK isn't screaming NO, but isn't so enamored of the idea that he's going to be the one to do the upload.
[16:34] <ScottK> That's all I have on that.
[16:34] <jdstrand> slangasek: if you see my comments in the second bug, I came across some situations that were a problem. but ultimately, I have no fsck output. it could be sitting there waiting for me to interact with it. I can't. Maybe I'll remember 'Esc' or 'M' or whatever, maybe not. it is a poor user experience
[16:34] <robbiew> well...having shared the pain of past Python transitions....I understand ;)
[16:34] <seb128> seems we should delay that to next cycle, will create lot of rebuilds, extra CD uses, etc
[16:34] <robbiew> ack
[16:34] <jdstrand> slangasek: the first time someone hits it, they are really mad, and probably will remember for next time. I thnk we can do better
[16:34] <slangasek> jdstrand: yep, it is :(
[16:35] <seb128> we seems to be running behind already and some teams lack staff to fill in gaps
[16:35] <seb128> we should really focus on stabilizing now
[16:35] <robbiew> [ACTION] robbiew to discuss postponing Python 2.7 as supported with barry and doko
[16:35] <MootBot> ACTION received:  robbiew to discuss postponing Python 2.7 as supported with barry and doko
[16:35] <ScottK> Note the lack of pushing back from me on seb128's points.
[16:36] <slangasek> :-)
[16:36]  * robbiew isn't pushing back either ;)
[16:37] <robbiew> ANY thing else?
[16:37] <robbiew> no?
[16:37] <robbiew> good
[16:37] <robbiew> :)
[16:37] <robbiew> [TOPIC] Server team status
[16:37] <MootBot> New Topic:  Server team status
[16:37] <Daviey> Hello o/
[16:37] <Daviey> https://wiki.ubuntu.com/ServerTeam/MaverickReleaseStatus
[16:37] <Daviey> http://people.canonical.com/~pitti/workitems/maverick/canonical-server-ubuntu-10.10-beta.html
[16:37] <Daviey> The above two URL's describe the situation pretty well.  We are generally on track.  We have had 3 engineers at a conference in the last week (and we are now one extra down). We've made some excellent leaps forward in UEC, particualry with the help from upstream Eucalytpus.  The major bugs that were concerning us, seem to be fixed - pending further testing (QA & Daviey).
[16:37] <Daviey> server-maverick-community - 0% complete - Might be a small blueprint, some progress - i believe waiting on a discussion with IS for feasibility.   Jorge to update some wiki/docs.
[16:37] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-server-ubuntu-10.10-beta.html
[16:37] <Daviey> Bug 572317 - image-store does not support images without a ramdisk (niemeyer): might use a workaround instead, discussions ongoing.  Requires some input from Gustavo.
[16:37] <Daviey> Bug 313812 - umount of ecryptfs does not automatically clear the keyring (can be mounted by root later) - currently stalled (https://bugs.edge.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/313812/comments/24)
[16:37] <Daviey> Bug 570870 - pxe boot doesn't work with kvm (Serge), Fix proposed - requires decision and testing
[16:38] <Daviey> Those seem to be the crucial, and input from other team points.. The other items are pretty well covered on the MaverickReleaseStatus page.
[16:39] <Daviey> Questions?
[16:40] <robbiew> thanks Daviey
[16:40] <Daviey> Some of the team have also been split between some out of platform work, and research.
[16:40] <robbiew> ack
[16:40] <robbiew> [TOPIC] Desktop team status
[16:40] <MootBot> New Topic:  Desktop team status
[16:40] <seb128> hey
[16:41] <seb128> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:41] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:41] <seb128> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-ubuntu-10.10-beta.html
[16:41] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-ubuntu-10.10-beta.html
[16:41] <seb128> our beta trend is a bit behind on the graph but it's not true
[16:41] <seb128> we have some server team items on there
[16:41] <seb128> otherwise we got quite a lot done this week
[16:41] <seb128> xorg transitioned to the new 1.9
[16:41] <seb128> GNOME has been updated
[16:42] <seb128> (now that GNOME decided to pull a stable 2.32)
[16:42] <seb128> the gobject introspection stack has been updated
[16:42] <seb128> didrocks put lot of efforts to get openoffice updated in maverick as well
[16:43] <seb128>
[16:43] <seb128> specs are on shape
[16:43] <seb128> we postpone the language selector changes to next cycle
[16:43] <seb128> and the empathy ones
[16:43] <seb128> software-center ui is feature complete for maverick
[16:44] <seb128>
[16:44] <seb128> that's it
[16:44] <seb128> questions?
[16:44] <seb128> (I guess Riddell or ScottK will do a Kubuntu update)
[16:44]  * ScottK looks at Riddell.
[16:45]  * ScottK imagines Riddell went for a coffee and starts.
[16:45] <ScottK> Got KDE 4.5.0 final in now.
[16:45] <ScottK> Still blocked on armel by kdebindings.
[16:45] <ScottK> We have yet to have an armel image this cycle, so this is getting to be a really big deal.
[16:46] <ScottK> Riddell is working on updating the KDE Ubiquity front end to match the new design.
[16:46] <ScottK> That's all.
[16:46] <ogra> ScottK, hmm, i thought qt was fixed to not expose the qreal issues anymore
[16:46] <ScottK> ogra: I don't think we can do that without breaking ABI.
[16:47] <ogra> which is what upstream requested from us, but NCommander was blocking it
[16:47] <ogra> and since he is the QT/KDE expert in our team ...
[16:47] <ScottK> I don't have a strong opinion on how to solve it.  It's getting critical to get it solved one way or the other.
[16:48] <ScottK> If we're going to have to rebuild all the Qt reverse build depends, we need to get started ...
[16:49] <ScottK> robbiew: Could we have an action assigned with a deadline to someone who can solve this?
[16:49] <Riddell> doh, missed my slot, sorry
[16:49] <ogra> well, there are just two options, a) update QT as upstream asked for b) update *all* the kde patches we carry to work again
[16:49] <ogra> NCommander, wanted to go for b) but then got some additional work to do that requires a lot of travelling
[16:49] <ScottK> OK.  Pick one and let's move forward.
[16:50] <ogra> i cant really judge how much time he will have for it but would actually like to leave it in his hands
[16:51] <Riddell> why do KDE patches need to be updated?  rather I think b) is keep writing patches as problems occur
[16:51] <Riddell> (we don't carry much in the way of patches, they go upstream)
[16:51] <ScottK> So far kdebindings is the only known issue in Main.
[16:51] <ogra> Riddell, afaik we have all these patches for qlist/qreal vs double already
[16:51] <ScottK> ogra: Most of them have gone upstream.
[16:52] <ogra> but since kdebindings ftbfs on such an issue something seems wrong with the patches
[16:52] <ScottK> kdebindings is specially full of fail.
[16:52] <ScottK> It's just a tough one.
[16:53] <ogra> well, NCommander wrote the patches initially, no matter where they live, he is surely the best to update them
[16:53] <ScottK> Right so it would be nice if his work prioritization was such that he could do that.
[16:54] <ogra> i cant move any of his new items atm and he doesnt seem to be here to talk for himself
[16:54] <ogra> lets take it to a mail discussion
[16:54] <ogra> so we can move on
[16:55] <slangasek> is there a summary of this issue written down somewhere?  We might find someone among the Linaro folks who would be willing to help work through it
[16:55] <ScottK> Nothing to discuss.
[16:56] <slangasek> but I wouldn't like to point them at "Qt+KDE" without an explanation of what needs solving
[16:56] <ogra> slangasek, well, it was always in NCommanders hands and i doubt he wroite down what he did
[16:56] <ogra> slangasek, asac has had lots of discussions witrh QT upstream though, he can give you some insight on the linaro side
[16:56] <slangasek> ok
[16:56] <ScottK> dyfet has also looked at it some.
[16:57] <ogra> dyfet, couls you take that task and fix kdebindings ?
[16:57] <ogra> *could even
[16:57] <ScottK> The actual build failure in kdebindings seems a knock on effect of problems in sip4, but I don't know details.
[16:58] <dyfet> ogra: yes, I recall it was a sip related/prototype issue
[16:58] <ogra> dyfet, awesome
[16:58] <ogra> ScottK, so dyfet is your man ;)
[16:59] <ScottK> ogra: I don't control anyone's work schedule that can fix it.  I just want it done.
[16:59] <ogra> ScottK, indeed
[17:00] <robbiew> so what's the plan here
[17:00] <ogra> robbiew, dyfet takes care
[17:01] <robbiew> dyfet: is that correct?
[17:01] <dyfet> yes
[17:01] <ogra> probably together with someone from linaro if slangasek agrees
[17:01] <slangasek> I don't control the work schedule of most of the people who would work on Qt, either :)
[17:02] <slangasek> but if someone can define the problem for me, I can poke around
[17:02] <ogra> right, asac can define the problem and both solutions, he knows even more details than me
[17:03] <ogra> but in any case we have an owner of the task now, so i think we're good to move on
[17:04] <robbiew> [ACTION] dyfet to solve all ScottK's problems :)
[17:04] <MootBot> ACTION received:  dyfet to solve all ScottK's problems :)
[17:04] <ogra> lol
[17:04] <ScottK> Ooh.
[17:04]  * ScottK starts a list.
[17:04] <dyfet> all??! ;)
[17:04] <robbiew> anything else for Kubuntu?
[17:04] <ScottK> Not from me.
[17:04] <robbiew> questions for Desktop?
[17:05] <seb128> I guess that's a no ;-)
[17:05] <robbiew> seb128: btw, I mentioned the bluetooth issue to superm1...he noted that the plumbing stuff 18hrs ago
[17:05] <robbiew> :/
[17:05] <seb128> what 18 hours ago?
[17:06] <seb128> you mean it's due to yesterday's update?
[17:06] <seb128> we need somebody to maintain the bt userland stack
[17:06] <seb128> I was talked to rickspencer3 earlier about that
[17:06] <robbiew> agreed
[17:06] <robbiew> neither Foundations nor Desktop has anyone to do it
[17:07] <seb128> if you have a bug due to the update please assign to the desktop team
[17:07] <seb128> we will deal with it
[17:07] <robbiew> rickspencer3 and I know we need to sort this out
[17:07] <seb128> ok, thanks
[17:07] <robbiew> between the hiring we both have...there's no reason why we can't
[17:08] <robbiew> [TOPIC] DX team update
[17:08] <MootBot> New Topic:  DX team update
[17:09] <tedg> Ah, that's me I guess :)
[17:09] <seb128> hey tedg ;-)
[17:09] <seb128> tedg, that's where you do a summary of what dx did this week and where your specs stand
[17:09] <tedg> So there's this Unity thing you guys may have heard about, yeah, so we're doing that ;)
[17:10] <robbiew> heh
[17:10] <seb128> tedg, usually status is similar to https://wiki.ubuntu.com/DesktopExperienceTeam/MaverickReleaseStatus
[17:10] <seb128> not sure there is one this week
[17:10] <seb128> dbarth has been sprinting and is travelling now
[17:10] <tedg> I think overall we're in good shape.  Sound has started to work with MPRIS v2 which is probably going to need a feature freeze exception.
[17:11] <tedg> But, the MPRIS v1 stuff is in good shape overall now.  Even if v2 is better.
[17:11] <tedg> We've also update indicator-application to add some oft requested features, which required an lib bump, shouldn't be a big deal, but might require some rebuilds.
[17:12] <tedg> I imagine most things will get rebuild by themselves in time anyway, but we should watch to make sure the old lib leaves.
[17:12] <slangasek> (.oO "message passing really ionizes sound"?)
[17:13] <tedg> On the appmenu front we've been working on performance and other clean up issues.
[17:13] <tedg> The big bug there is the desktop menu which will require a patch to nautilus.
[17:14] <tedg> I think we're at the point of determining whether indicator-datetime is in desktop, and I'm guessing that decision is a no?
[17:14] <tedg> As we weren't able to complete the Evolution integration needed for the desktop release.
[17:14] <robbiew> is there a blueprint for indicator-datetime?
[17:14] <seb128> yeah, that's a "no"
[17:15] <tedg> robbiew, Yeah, let me look for it.
[17:15] <seb128> robbiew, https://blueprints.launchpad.net/ubuntu/+spec/dx-m-indicator-clock
[17:15] <seb128> tedg, ^
[17:15] <tedg> But, I think that's everything that's RT related.  Any questions.
[17:15] <tedg> Thanks seb128
[17:15] <robbiew> seb128: thnx
[17:16] <robbiew> no questions?....moving along
[17:16]  * robbiew skips UX as they don't send folks...but I've followed up via email on some 0% complete items
[17:16] <robbiew> [TOPIC] ARM team status
[17:16] <MootBot> New Topic:  ARM team status
[17:16] <ogra> \o/
[17:16] <ogra> Detailed status at: https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Maverick
[17:16] <ogra> ...
[17:16] <ogra> Short summary:
[17:16] <ogra>  * omap3/4 images for alpha 3 were released last week
[17:16] <ogra>  * ubuntu-netbook-efl-default-settings is pending fixes to the default 2D session
[17:16] <ogra>  * ongoing "normal" work on main ftbfs
[17:16] <ogra>  * apparently a security kernel upgrade killed babbage boards, the issue was researched together with freescale and a fix was found which is about to be applied to a lucid SRU
[17:16] <ogra>  * work on images is blocked due to Bug #616581 (oem-config does not start), research for the cause of the breakage is still going on
[17:16] <ogra>  * the resizing process of the preinstalled images was reworked and we gained a massive speedup of the resizing procedure (from 10-15min per 4G to about 2.5min overall)
[17:17] <ogra> ...
[17:17] <ogra> Beta status:
[17:17] <ogra> http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10-beta.html
[17:17] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10-beta.html
[17:17] <ogra> ...
[17:17] <ogra> Beta targeted specs:
[17:17] <ogra> https://blueprints.launchpad.net/ubuntu/+spec/mobile-m-omap-edid-autodetection
[17:17] <ogra> https://blueprints.launchpad.net/ubuntu/+spec/mobile-maverick-arm-improved-subarch-detection
[17:17] <ogra> ...
[17:17] <ogra> There are 10 Beta targeted bugs
[17:17] <ogra> ...
[17:17] <ogra> 2 Blocker Bugs:
[17:17] <ogra> bug 605739
[17:17] <ogra> bug 616581
[17:18] <ogra> any questions ?
[17:19] <robbiew> I think ScottK already had his...heh
[17:19] <robbiew> thnx ogra
[17:19] <ogra> heh
[17:20] <robbiew> [TOPIC] MOTU update
[17:20] <MootBot> New Topic:  MOTU update
[17:20] <ScottK> http://qa.ubuntuwire.com/ftbfs/ and http://people.canonical.com/~ubuntu-archive/NBS/ have me slightly concerned.  It gets more sporting if we throw Python 2.7 in the mix.
[17:20] <MootBot> LINK received:  http://qa.ubuntuwire.com/ftbfs/ and http://people.canonical.com/~ubuntu-archive/NBS/ have me slightly concerned.  It gets more sporting if we throw Python 2.7 in the mix.
[17:20] <robbiew> heh...okay okay
[17:20] <robbiew> we get it
[17:20] <ScottK> There's a lot to do.  We'll see how it goes.
[17:20] <robbiew> Python 2.7 will be postponed ;)
[17:20] <ScottK> So far the community members of the release team are keeping up with the flow of FFe's OK.
[17:21] <sistpoty|work> o/
[17:21] <ScottK> Help is, of course, appreciated from other release team members as they are available.
[17:21] <ScottK> sistpoty|work: Did you have anything else?
[17:21]  * robbiew isn't officially part of the release team....but can help
[17:21] <sistpoty|work> nah, just trying to get an overview after some ubuntu hiatus
[17:22] <ScottK> WIth pitti and slangasek focused on other things, we might consider adding someone more.
[17:22] <sistpoty|work> robbiew: that'd be excellent, I think we'll soonish be stuffed with workload on the FFe side
[17:23] <slangasek> I have a few FFes to request on behalf of linaro, so I'll at least be putting in my share of work to be FFe-neutral :P
[17:23] <sistpoty|work> heh
[17:23] <robbiew> heh
[17:23] <robbiew> [ACTION] robbiew to work on growing the release team
[17:23] <MootBot> ACTION received:  robbiew to work on growing the release team
[17:24]  * ScottK waves to skat__.
[17:25] <ScottK> I think that's it.
[17:25] <ogra> she carries a long tail aroung it seems :)
[17:25] <robbiew> heh...she will be helping for sure
[17:25] <robbiew> [TOPIC] Derivatives
[17:25] <MootBot> New Topic:  Derivatives
[17:26] <robbiew> I got tired of tracking Linaro items...plus they do it themselves anyway :)
[17:26] <robbiew> so just linked to their status in the agenda
[17:26] <robbiew> [TOPIC] 10.04.1
[17:26] <MootBot> New Topic:  10.04.1
[17:26] <ScottK> robbiew: If we are going to keep a derivatives section, you might want to advertise it more widely.
[17:26] <robbiew> WILL IT EVER COME!!!!! <sigh>
[17:26] <slangasek> robbiew: oh, I didn't see any link to Linaro status in the email :)
[17:27] <slangasek> (and therefore didn't know what page to update this week while JamieBennett was off, doh)
[17:27] <robbiew> slangasek: as usual...t's in the wiki ;)
[17:27] <ScottK> robbiew: You need to send slangasek on vacation without internet so he stops adding stuff.
[17:27] <skat__> ScottK_: waves back... :)
[17:28] <robbiew> ScottK: heh..I can't...doesn't work for me anymore ;)
[17:28] <slangasek> "what do you mean you don't see it, it's right there in the fridg^Wwiki"
[17:28] <robbiew> plus I need him to help with 10.04.1
[17:28] <robbiew> https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone=27565
[17:29] <slangasek> I'm working on getting right-sized live images today
[17:29] <robbiew> \o/
[17:29] <slangasek> required some seed->task changes, which I had to work out how to make happen
[17:29] <slangasek> apparently by hacking cron.germinate to manually point it at lucid
[17:29] <mathiaz> slangasek: so you'll be responsible for spinning isos?
[17:30] <slangasek> the need for seed changes is because firefox, xulrunner, linux, and linux-firmware have all gotten bigger since 10.04
[17:30] <slangasek> this is not a good trend
[17:30] <ogra> only the right sized ones, not the left sized ones :P
[17:30] <slangasek> mathiaz: yessir
[17:31] <ScottK> Do we need to add a space reservation for respins in future LTS releases?
[17:31] <slangasek> I think our SRU tracker should spit out a warning about significant size increases in packages in main
[17:31] <ScottK> If so, someone should write that down so we remember in a year and a half.
[17:31] <slangasek> so that we can figure out what the deal is /before/ we get to a week before point release
[17:31] <jdstrand> unfortunately, the firefox ones were security updates
[17:32] <slangasek> ScottK: IMHO the size increases are too unpredictable to make it worthwhile to reserve space
[17:32] <robbiew> slangasek: who maintains the SRU tracker?
[17:32] <slangasek> robbiew: "the release team" (primarily pitti in the past)
[17:32] <jdstrand> (don't know if the SRU tracker would pick them up, presumably not)
[17:32] <slangasek> sorry, "the SRU team" :)
[17:32] <slangasek> jdstrand: dunno if it does
[17:32] <ScottK> OK.
[17:32] <slangasek> jdstrand: security updates> obviously - but why do security updates have to be bloated :)
[17:33] <ScottK> Because it's Firefox.
[17:33] <jdstrand> talk to mozilla
[17:33]  * slangasek nods
[17:33] <robbiew> [ACTION] robbiew to talk to pitti about if the SRU tracker can "spit out a warning about significant size increases in packages in main"
[17:33] <MootBot> ACTION received:  robbiew to talk to pitti about if the SRU tracker can "spit out a warning about significant size increases in packages in main"
[17:33] <jdstrand> it is going to be the same with chromium too, fwiw
[17:34] <slangasek> anyway, I should get candidate images out by end of day today
[17:34] <robbiew> slangasek: when's the last time we audited the packages in main?
[17:34] <robbiew> are we still sure we NEED them all there?
[17:34] <ScottK> robbiew: We did an audit of minimal/standard at the last UDS.
[17:35] <slangasek> robbiew: not so long ago - and this isn't even about all packages in main, this is the stuff in the default install, which does get a good deal of regular scrutiny
[17:35] <robbiew> ack
[17:35] <jdstrand> the server team reviewed their bits at UDS too
[17:35] <robbiew> can we make CDs just hold more data?
[17:35] <robbiew> lol
[17:35] <slangasek> yes
[17:35] <slangasek> but cjwatson didn't want to go that route ;)
[17:35] <robbiew> heh
[17:36] <slangasek> (the sizing we use for our CDs is for least-common-denominator CDs; most CDs and CD drives handle a good 4MB more, IIRC)
[17:36] <robbiew> well..once Google and Verizon spread tiered internet around the world and we pay for Faster speeds...we can move to just DVDs
[17:36] <slangasek> so, we'll have images, and I'll post them to the tracker, but I guess we won't really have anybody available for testing until Monday?
[17:36]  * jdstrand chuckles thikning about firefox gobbling that up immediately
[17:37] <marjo> slangasek: ack
[17:37] <robbiew> marjo: come on...weekend work is fun! :)
[17:37] <robbiew> okay..running over
[17:37] <robbiew> anything else for 10.04.1
[17:37] <marjo> robbiew: will test ISOs on the plane to oxford
[17:37] <robbiew> marjo: thnx!
[17:37] <robbiew> lol
[17:37] <robbiew> #endmeeting
[17:37] <MootBot> Meeting finished at 11:37.
[17:38] <robbiew> whew!
[17:38] <robbiew> thanks all
[17:38] <slangasek> marjo: let us know how the wifi onboard handles the torrent
[17:38] <slangasek> :-)
[17:38] <robbiew> slangasek: I thought Till saved us some space with his compression work
[17:38] <czajkowski> long meeting.
[17:38] <slangasek> robbiew: for 10.10 only, yes?
[17:38] <robbiew> bah!
[17:39] <slangasek> regardless, we're still about 10MB oversized from where we really want to be
[17:39] <slangasek> (i.e., we'd like to have a good set of langpacks present on the CD)
[17:39] <robbiew> understand
[17:40]  * ScottK wonders how much switching from firefox to abrowser would save.
[17:41] <slangasek> abrowser is free as in free space
[17:42] <sistpoty|work> the release name indicates yet a different browser though, that would save even more space :P
[18:01] <barry> doko: hi