[15:57] <pitti> hello
[15:58] <czajkowski> pitti: hey
[15:59] <slangasek> morning
[16:01] <lool> Wee
[16:02] <cjwatson> hi
[16:02] <slangasek> #startmeeting
[16:02] <MootBot> Meeting started at 10:02. The chair is slangasek.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <njpatel> hello
[16:02] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-09-25
[16:02] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-09-25
[16:03] <slangasek> in we go!
[16:03] <slangasek> [TOPIC] action items
[16:03] <MootBot> New Topic:  action items
[16:03] <slangasek>     * cjwatson to *possibly* look at dbus on ia64
[16:03] <slangasek> I'm told this is resolved
[16:03] <cjwatson> yes
[16:04] <slangasek> so, yay :)
[16:04] <cjwatson> turned out to be easy
[16:04] <slangasek> (ScottK sends his regrets for this meeting, btw, work conflict)
[16:04] <slangasek> agenda at https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-09-25, for those just arriving
[16:04]  * ogra is half way here
[16:04] <slangasek> [TOPIC] QA Team
[16:04] <MootBot> New Topic:  QA Team
[16:05] <cr3> * Hardware testing
[16:05] <cr3> We have one new bugs
[16:05] <cr3> #435257 - Karmic takes forever to install on a Toshiba NB 200
[16:05] <cr3> One solved bug:
[16:05] <cr3> #432497 - unable to install on Acer Aspire One because of broken SSD
[16:05] <cr3> And one outstanding:
[16:05] <cr3> #431970 - internal microphone not working on HP Mini Bixby and Toshiba NB100
[16:05] <cr3> Any Qs on bugs?
[16:05] <cr3> I'm actually dismantling the Aspire One to replace the drive as we speak, so we should have results next week
[16:06] <mdz> bug 435257, bug 432497, bug 431970
[16:06] <mdz> cr3, all three need triage
[16:06] <cr3> mdz: will do
[16:06] <slangasek> cr3: well, 435257 shouldn't have taken 2 days until the weekly release meeting to get targeted to karmic (I've just targeted it now)
[16:06] <slangasek> part of the larger triage question, yes
[16:07] <cr3> ok, onto specs
[16:07] <cr3> * UbuntuSpec:karmic-qa-increase-apport-adoption
[16:07] <cr3> No news.
[16:07] <cr3> * UbuntuSpec:karmic-qa-extended-audio-testing
[16:07] <cr3> cr3 and fader to coordinate on testing a few laptops before integrating into the automated process.
[16:07] <cr3> * UbuntuSpec:karmic-qa-metrics-based-testing-phase-2
[16:07] <cr3> On the client side, Phoronix has been integrated to run a few suites. On the server side, there were a few architectural problems but these are solved and now working on migration scripts.
[16:08] <cr3> Any Qs on specs?
[16:08] <mdz> cr3, no news on apport adoption?
[16:08] <mdz> didn't we make a major change in that area recently (the filebug redirect)?
[16:08] <pitti> we discussed that a lot in this week's desktop meeting
[16:09] <cr3> mdz: I thought that was done last week, my mistake.
[16:09] <pitti> right, we discussed the impact, and how to make it less strict
[16:09] <mdz> cr3, I think it was, but surely there has been some activity following that?
[16:09] <mdz> I would expect it to generate some discussion
[16:09] <pitti> so far the consensus was to not enforce it for ~ubuntu-bugcontrol, AFAIK
[16:09] <mdz> and for the QA team to be evaluating the results
[16:10] <cr3> mdz: I haven't received such information in time for this meeting, my apologies :(
[16:10] <pitti> https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-09-22 "Changed bug reporting process", FTR
[16:11] <mdz> cr3, please take an action to ensure that the QA team collects and processes feedback about this change
[16:11] <cr3> mdz: and where shall I follow up with this information?
[16:11] <slangasek> [ACTION] cr3 to ensure that the QA team collects and processes feedback about the filebug redirect change
[16:11] <MootBot> ACTION received:  cr3 to ensure that the QA team collects and processes feedback about the filebug redirect change
[16:11] <mdz> cr3, ubuntu-devel seems like an appropriate choice
[16:11] <cr3> mdz: will do, thanks
[16:12] <pitti> cr3: bug 432088 , FYI
[16:12] <mdz> cr3, where is the latest hardware test report?
[16:13] <cr3> mdz: fader is on vacation, so I suspect his last report will date back to Wednesday. I'll try to find the url
[16:13] <mdz> we should have a report at every release meeting
[16:14] <mdz> even if fader happens to be away
[16:14] <slangasek> http://people.ubuntu.com/~fader/hw-testing/current.html is the permanent "current" report, which includes tests as recent as the 23rd
[16:14] <MootBot> LINK received:  http://people.ubuntu.com/~fader/hw-testing/current.html is the permanent "current" report, which includes tests as recent as the 23rd
[16:14] <cr3> slangasek: thanks
[16:15] <slangasek> all the failures in that table are covered by the bugs mentioned earlier; there are a handful of "untested"s with documented reasons
[16:16] <mdz> we seem to still have some netbooks missing from the report
[16:16] <mdz> I've written to Marjo about that already, but we need to see it fixed for the next meeting
[16:16] <cr3> mdz: I'll double check the report reflects what we have in certification
[16:16] <slangasek> which ones are missing?
[16:17] <mdz> the report is a bit misleading because it doesn't include all of the models we're supposed to be testing for 9.10
[16:17] <mdz> slangasek, off the top of my head, the mini 10v
[16:17] <mdz> there's a full gap analysis in my email to marjo
[16:17] <slangasek> ok
[16:17] <cr3> mdz: we don't have a mini 10 though, just a 9
[16:18] <mdz> cr3, exactly!
[16:18] <mdz> it is a target which is not only untested, but we don't even have the hardware yet, i.e. it is way behind schedule
[16:18] <slangasek> [ACTION] cr3, marjo to follow through on netbooks missing from the hw certification lab
[16:18] <MootBot> ACTION received:  cr3, marjo to follow through on netbooks missing from the hw certification lab
[16:18] <cr3> mdz: ah, I thought you meant we weren't reporting on the hardware we had on hand, I was scared for a bit
[16:19] <mdz> cr3, no, I've requested that we report on the goals for the release
[16:19] <slangasek> well, not having the hardware that needs to be tested is also scary; but we have an action item for that now, so I think we can move on?
[16:19] <mdz> yes
[16:19] <slangasek> anything else for QA?
[16:20] <mdz> we're missing test cases for eucalyptus
[16:20] <cr3> not from me
[16:20] <mdz> kirkland, cjwatson, et al have worked on this a little
[16:20] <mdz> I think help from the QA team would be appreciated
[16:20] <cr3> mdz: will this require integration work across systems, or can it be self contained in a single standalone system for testing?
[16:20] <mdz> cr3, it requires a minimum of two computers
[16:21] <pitti> would two VMs suffice?
[16:21] <mdz> pitti, two VMs can work for testing the installation portion only (you can't start VMs inside a VM yet)
[16:21] <mdz> but they need to be connected to a common virtual LAN
[16:21] <pitti> ah, of course
[16:21] <mdz> the setup is non-trivial in either case
[16:21] <davmor2> mdz: I can do some work on that I'll have a chat with cjwatson and kirkland as too what they need
[16:21] <mdz> which is why we need a clear documented test plan
[16:22] <cr3> mdz: I'm afraid this will be difficult to automate for the karmic cycle
[16:22] <mdz> cr3, I am not looking for automation
[16:22] <slangasek> we're not looking for automation, we're looking for documentation
[16:22] <cr3> excellent, just checkin
[16:22] <mdz> we need to create a test plan before we can even think about automation
[16:22] <mdz> davmor2, thank you
[16:23] <mdz> davmor2, do you have two computers you can use for this testing?
[16:23] <cr3> this use case will be good for discussion during the next uds for automation
[16:23] <davmor2> 6
[16:23] <mdz> davmor2, ok, please work with ttx on this
[16:23] <davmor2> mdz: 6 but 4 on lan
[16:23] <davmor2> mdz: np
[16:23] <slangasek> [ACTION] davmor2 to work with ttx on creating a test plan for eucalyptus
[16:23] <MootBot> ACTION received:  davmor2 to work with ttx on creating a test plan for eucalyptus
[16:23] <mdz> he can point you to the existing documentation and forward test reports showing our current methodology
[16:24] <slangasek> davmor2: thanks for stepping forward
[16:24] <mdz> nothing more from me for QA
[16:24] <slangasek> anyone else?
[16:25] <slangasek> [TOPIC] Desktop Team
[16:25] <MootBot> New Topic:  Desktop Team
[16:25] <slangasek> pitti: hello
[16:25] <pitti> as usual, https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus has all the details
[16:25] <pitti> This week we finally got the Karmic artwork from the Design team, and integrated the new icon theme, wallpaper, and usplash logo.
[16:25] <pitti> The session and messaging indicators landed a lot of urgent fixes and are in good shape for beta now. Empathy also got some bug fixing love; audio calls are now working reasonably stable, video is still brittle (currently being debugged).
[16:25] <pitti> We fixed 5 RC bugs, and got two new ones.
[16:25] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:25] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:26] <pitti> I just heared that we probably need to squeeze a new gdm artwork into beta, will chat with slangasek about that after meeting
[16:26] <slangasek> ok
[16:26] <pitti> for final I'd like to finish the polkit-1 migration, so that we don't need to carry the old polkit stack in the default installation any more
[16:26] <slangasek> what remains to be converted there?
[16:27] <pitti> this should be relatively easy to do, but doesn't quite count as "bug fixing"
[16:27] <pitti> slangasek: screen-resolutions-extra is one
[16:27] <slangasek> (we can take that offline to #ubuntu-release after, if you wish)
[16:27] <pitti> the other is checkbox
[16:27] <pitti> checkbox doesn't "really" use polkit
[16:27] <pitti> I opened a bug and sub'ed cr3, I'd like to discuss it with him first
[16:27] <pitti> slangasek: yes, let's
[16:27] <pitti> too much detail for this meeting here
[16:28] <pitti> any questions?
[16:29] <pitti> oh, and of course the most critical bug EVER has been fixed: the nm-applet icon for ethernet which looked like a stray pacman ghost :-)
[16:29] <ogra> \o/
 hearts
[16:30] <pitti> Riddelll said that polkit-qt-1 won't make it, so we probalby have to live with bug 256245
[16:30] <slangasek> that's an o-o-b discussion, though ;)
[16:30] <pitti> slangasek: hearts> already fixed
[16:30] <slangasek> ok
[16:30] <pitti> slangasek: alex did a followup upload which pretty much changes it back to "normal"
[16:30] <pitti> no hearts for us, sorry
[16:31] <slangasek> pitti: could you go ahead and mark 256245 as 'wontfix' for karmic w/ explanation, then?
[16:31] <pitti> slangasek: will do
[16:31] <slangasek> no sense in tracking it if we know it's blocked on other bits
[16:32] <slangasek> any other questions from Desktop?
[16:32] <slangasek> s/from/for/
[16:32] <pitti> (done)
[16:32] <Riddelll> I need to check the upgrade script for Kubuntu some more
[16:33] <Riddelll> tseliot just fixed the intel-crash-on-logout bug which is great, although we now have another bug with KDM
[16:33] <Riddelll> otherwise Kubuntu is in decent shape
[16:33] <slangasek> great
[16:33] <pitti> I'm still testing jockey
[16:33] <pitti> Apport works for me now
[16:33] <pitti> (in KNE)
[16:33] <Riddelll> jockey worked for me, once I gave it network
[16:34] <pitti> ok, cool
[16:35] <slangasek> pitti: what's still beta wrt desktop-karmic-gnome-speech-replacement?
[16:35] <pitti> slangasek: it still needs a test plan/release note AFAIK
[16:35] <slangasek> ok
[16:35] <pitti> similar for the other specs
[16:35] <pitti> it's by and large "testing", "test plan", etc.
[16:36] <slangasek> seems like we'd want to have those for beta
[16:36] <slangasek> are we likely to have them?
[16:36] <pitti> ok, will make sure that we will have them
[16:37] <slangasek> thanks
[16:37] <slangasek> [TOPIC] DX Team
[16:37] <MootBot> New Topic:  DX Team
[16:37] <pitti> ACTION: pitti to ensure that we have test plans/release ntoes for all specs
[16:37] <davidbarth> As usual, the status report is at: https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus
[16:37] <slangasek> [ACTION] pitti to ensure that we have test plans/release notes for all specs
[16:37] <MootBot> ACTION received:  pitti to ensure that we have test plans/release notes for all specs
[16:37] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus
[16:37] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus
[16:37] <davidbarth> mostly bug fixes
[16:37] <davidbarth> of note
[16:38] <davidbarth> indicator-session gained a user session menu to switch to open new session; that was in fusa/jaunty though
[16:38]  * slangasek nods
[16:38] <davidbarth> also support for locking the session on suspend/user-switch
[16:38] <davidbarth> that may help with #407315
[16:39] <davidbarth> xsplash was impacted by recent gdm patches for autologin
[16:39] <davidbarth> so we now have a nasty flicker; we've decided to work on that once the beta is out, to get a good baseline for a fina lset of fixes
[16:40] <davidbarth> the list of bugs on our radar is on the report
[16:40] <davidbarth> of note: #435522 - "xsplash timing out too early"
[16:40] <pitti> ^ especially on live system
[16:40] <davidbarth> #433719 - "indicator-applet crashed with SIGSEGV in g_str_hash()"
[16:40] <davidbarth> pitti: yep...
[16:40] <davidbarth> #430904 - Menu ordering gets "out of whack"
[16:41] <davidbarth> and a new unr crasher: #420478 - "netbook-launcher crashed with SIGSEGV in g_cclosure_marshal_VO..."
[16:41] <davidbarth> that njpatel is furiously working on
[16:42] <lool> Thanks for the nice bug fix releases along the week BTW
[16:42] <davidbarth> questions on DX?
[16:43] <Riddelll> in Kubuntu: agatau fixed a bug in kmail MI and I had to work around konversation not compiling with MI support (agateau to find a proper fix), so we're in decent shape.
[16:43] <davidbarth> Riddelll: yes, thanks for pointing this out
[16:44] <slangasek> davidbarth: please make sure that your release-targeted bugs get targeted to the release in launchpad (you can grab me or any other ubuntu dev to target them); that prevents us having two different lists that we're watching for "critical" bugs
[16:44] <Riddelll> KDM could do with upstart-ification at some point post-beta, nixternal has a script done already but needs keybuk and me to look over, but I believe our ksplashx stuff should work fine after that
[16:44] <davidbarth> slangasek: ok
[16:45] <slangasek> Riddelll: post-beta, not pre-beta?
[16:45] <cjwatson> I was wondering that too
[16:46] <cjwatson> not being upstartified presents some ... significant challenges to the installer
[16:46] <cjwatson> although I must admit that the "Install Kubuntu" option appears to actually work in today's image
[16:46] <Riddelll> well I could upload it quickly today, but I've not had a chance to test it yet
[16:46] <pitti> also, it's quite an intrusive change which could use the testing in beta?
[16:46] <slangasek> Riddelll: I can review it in the queue and poke Scott in person if I have doubts
[16:47] <Riddelll> and keybuk doesn't seem to be around to check with
[16:47] <slangasek> Riddelll: so I would favor having it uploaded today
[16:47] <pitti> I guess he's travelling back from LinuxCon
[16:47] <Riddelll> ok I'll get testing on it now
[16:47] <slangasek> AFAIK he's still /at/ plumbers :)
[16:47] <pitti> oh, ok; last plumbers was Tue-Thu
[16:47] <pitti> anyway
[16:47] <pitti> wrong, Wed-Fri
[16:48] <slangasek> anything else for DX?
[16:48] <slangasek> [TOPIC] Mobile Team
[16:48] <MootBot> New Topic:  Mobile Team
[16:48] <lool> hey
[16:48] <ogra> here i am !
[16:48] <slangasek> hello
[16:48] <ogra> [link] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic
[16:48] <ogra> - Various bugs were fixed this week, good work was done to identify the armel openoffice breakage, workaround in progress
[16:48] <ogra> - work on moblin is ongoing, images build again
[16:48] <ogra> - UNR still in good shape even after lots of updates (we're making ourselves jobless here, should consider to add some artificial brekage :P )
[16:48] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic
[16:48] <ogra> - closed spec on rootstock (offline-installer-gui)
[16:48] <ogra> - closed specs for marvell and freescale desktops
[16:49]  * ogra cant mention often enough how grateful we are for doko being with us on openoffice !
[16:50] <cjwatson> yes, he's been hoovering up a lot of toolchain stuff this week
[16:50] <ogra> and keeping all armel HW in the company busy with testbuilds :)
[16:50] <ogra> and i mean *all*
[16:51] <slangasek> is there an OOo workaround known now?
[16:51] <lool> Yes
[16:51] <pitti> \o/
[16:51] <lool> binutils' change has been identified
[16:51] <slangasek> the last workaround doko suggested was "ship a copy of old binutils with the OOo source package" :)
[16:51] <slangasek> ah, much better :)
[16:51] <ogra> heh
[16:51] <lool> I think we can revert it and rebuild oo.o
[16:51]  * pitti updates that on DesktopTeam/ReleaseStatus
[16:51]  * ogra guesses doko isnt happy having that sentence in the logs :P
[16:52] <lool> Sadly, the binutils change is likely exposing a bug in another place
[16:52] <lool> So we'll be hiding the real issue
[16:52] <slangasek> ok; but we're at least closer
[16:52] <ogra> but oo.o will run on armel
[16:52] <doko> no  OOo b-d on binutils-source, nobody will notice the extra build time ;p
[16:52] <lool> slangasek: yes; instead of knowing it's a toolchain change, we know now which part and which change
[16:53] <pitti> doko: gentoobuntu?
[16:53] <doko> genTOOobuntu
[16:53] <cjwatson> :-)
[16:53] <lool> haha
[16:53] <slangasek> lool: I see bug #430277 marked as "discussion ongoing" in the status report
[16:53] <lool> slangasek: So I escalated that bug via phone to design team on Monday evening
[16:53] <slangasek> lool: what's holding up bringing this to a conclusion?
[16:53] <lool> They wanted to chat with Mark about it and others
[16:53] <lool> and I pinged them again over email today
[16:53] <ogra> "the theme will be improved"
[16:54] <rickspencer3> presumably this issue now effects the desktop as well
[16:54] <ogra> discussion about *how* :)
[16:54] <pitti> will U1 get gray as well?
[16:54] <lool> slangasek: We need to know whether we want coloured icons for everything notification area, or always black and white (runtime desaturation) or a miw (what we have)
[16:54] <pitti> everything else is now
[16:54] <slangasek> lool: ok, have they been given a deadline for that to happen, so we're not trying to land these changes e.g., the week of RC?
[16:54] <lool> pitti: Exactly the problem
[16:54] <lool> pitti: many icons are visible only from time to time
[16:55] <lool> such as tomboy, rhythmbox, bluetooth...
[16:55] <rickspencer3> I feel that if it's a simple matter of changing to a thematically matching icon, we may as well get that in asap
[16:55] <lool> Not really
[16:55] <rickspencer3> but if it's about dynamically displaying different icons in different situations, then it's out of scope for Karmic
[16:55] <lool> I think the proper fix is to either use colours or to runtime transform the icons
[16:55] <rickspencer3> and we should stick with what he have and ship
[16:55] <lool> I dont think we can live with all icons being b&w because it's too hard to distinguish them, and the mix is ugly
[16:56] <rickspencer3> lool, right, my point is that it's too late to discussing "run time" fixes
[16:56] <lool> rickspencer3: Well instead of patching a bunch of icons we'd be patching code
[16:56] <lool> rickspencer3: Not sure why you feel it's harder
[16:56] <rickspencer3> lool, my point exactly
[16:56] <rickspencer3> because beta freeze was *yesterday* and it's time to stop making changes and fix crashers
[16:56] <lool> Problem is that we dont have a finite list of icons
[16:56] <lool> You can install any app
[16:56] <rickspencer3> imnsho
[16:57] <lool> rickspencer3: Ah you mean like not changing icon theme?  :-)
[16:57] <slangasek> patching icons would still present its own problems, in being able to make sure the right users get the right icons
[16:57] <rickspencer3> I mean, for the desktop anyway, I feel it's too late to fix this bug, as there is no clear direction, and we need to channel resources to the Karmic end game
[16:57] <lool> I think the easiest fix is to revert the notification area icons to colours in humanity
[16:58] <lool> it's a clearly identified change and I think they have a colour version already
[16:58] <rickspencer3> the easiest thing is to change nothing and live with the way it is for Karmic
[16:58] <slangasek> wasn't really meaning to open a fresh discussion about this here, though; just trying to make sure we're on track for resolving this issue
[16:58] <slangasek> since the bug has been open for some time now with no visible progress
[16:59] <lool> This bug triggered my proposal to drop humanity in UNR which triggered the move to humanity in the desktop  :-(
[16:59] <lool> anyway, status quo is ugly but not breaking anything and design team has been pinged
[16:59] <slangasek> hmm
[16:59] <rickspencer3> slangasek, who gets to make the call in terms of it being "too late" ?
[17:00] <slangasek> rickspencer3: the artwork deadline was yesterday; it's already late
[17:01] <rickspencer3> so I propose we close the bug as "won't fix" and take it up in Lucid UDS
[17:01] <slangasek> as regards "too late", any further changes are going to have to be discussed with the release team
[17:02] <slangasek> rickspencer3: well, my understanding is that the current result looks half-cooked; I'm not keen to ship that way either
[17:02] <lool> slangasek: I'll get back to you if I hear either way from the design team
[17:02] <lool> slangasek: I can ask humanity upstream to prepare a colour revert if you like
[17:02] <lool> I mean going back to colourful icons
[17:02] <slangasek> lool: I think it makes sense to have that lined up
[17:03] <lool> Ok
[17:03] <rickspencer3> thanks lool - I presume the desktop will be expected to follow suit
[17:03] <lool> Plus humanity folks are not busy with many more changes at this point any way
[17:03] <slangasek> [ACTION] lool to ask humanity upstream to prepare a colour revert for bug #430277
[17:03] <MootBot> ACTION received:  lool to ask humanity upstream to prepare a colour revert for bug #430277
[17:03] <lool> rickspencer3: we share the theme package now, so you will automatically
[17:04] <slangasek> anything else on the mobile side?
[17:04] <pitti> we'll ping the doc team for screen shot updates when that comes
[17:04] <ogra> we're happy
[17:04] <slangasek> pitti: better to warn them in advance that it may be coming, I think, so they don't waste time on screenshots they'll have to throw away?
[17:04] <pitti> slangasek: agreed
[17:05] <slangasek> [TOPIC] Kernel Team
[17:05] <MootBot> New Topic:  Kernel Team
[17:05] <lool> slangasek, ogra: thanks
[17:05] <slangasek> pgraner: morning
[17:05] <slangasek> apw: here?
[17:06] <davidm> slangasek, pgraner is on a plane now I think
[17:06] <slangasek> ah
[17:06] <slangasek> any kernel concerns that anyone else needs to bring up?
[17:07] <mdz> pgraner is on a plane, but said he would be online
[17:07] <ogra> a bunch ... for imx51, but nothing that wasnt mentioned in mobile already
[17:07] <slangasek> bug list seems self-explanatory; including some that I talked through with the kernel team in person this week
[17:07] <mdz> slangasek, I wanted to make sure that linux-ec2 (source, binary, meta) get into main for beta
[17:08] <slangasek> [ACTION] slangasek to get linux-ec2 into main for beta
[17:08] <MootBot> ACTION received:  slangasek to get linux-ec2 into main for beta
[17:08] <slangasek> mdz: looks like the meta's the only thing not there currently
[17:08] <slangasek> but yes, I'll follow through
[17:08] <mdz> slangasek, ok
[17:08] <mdz> it should be in the new uec seed, and so show up in component mismatches
[17:08] <slangasek> ok
[17:09] <cjwatson> yes, it's in c-m
[17:09] <slangasek> [TOPIC] Server Team
[17:09] <MootBot> New Topic:  Server Team
[17:09] <slangasek> ttx: hi
[17:10] <mdz> I'm afraid ttx and I haven't synced up yet due to eucalyptus chaos, but I have a few agenda items here to add
[17:10] <slangasek> ok, please go ahead
[17:10] <mdz> first the MIRs for ec2-images
[17:10] <ttx> o/
[17:10] <mdz> it looks like several have been completed this week
[17:10] <ttx> mdz: I kinda updated https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[17:11] <cjwatson> unless I'm missing something, m2crypto is the only one left
[17:11] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[17:11] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[17:11] <mdz> cjwatson, ah, I'd missed that ec2-init was 'fix committed' (what does that mean for an MIR?)
[17:11] <cjwatson> it means approved
[17:11] <mdz> bug 434744 is the master bug for the fact that the uec images were not main-pure
[17:11] <cjwatson> but there are still unpromoted dependencies so I was holding off actually promoting it
[17:12] <cjwatson> kees requested a change in m2crypto
[17:12] <mdz> cjwatson, are there MIRs for the dependencies already?
[17:12] <kees> i'd like to see the testsuite enabled, but beyond that, I'm ok with it
[17:12] <cjwatson> although said that he was fine with it going into main on the condition that the bug remains RC
[17:12] <cjwatson> or words to that effect
[17:12]  * kees nods
[17:12] <cjwatson> hmm, actually, ec2-init doesn't dep m2crypto
[17:13] <cjwatson> I thought it did for some reason
[17:13] <mdz> I assumed it was python-boto
[17:13] <pitti> the fixed ec2-init isn't uploaded yet
[17:13] <mdz> smoser, status of ec2-init?
[17:13] <pitti> the one in bzr head is okay
[17:13] <pitti> the one in the archive really shouldn't go anywhere near main
[17:13] <slangasek> euca2ools dep: python-m2crypto
[17:13] <cjwatson> does ec2-init need a sponsor or something?
[17:13] <mdz> I don't know, need input from smoser
[17:14] <mdz> I tried to reach him a few times this week but have had trouble getting hold of him
[17:14] <pitti> I talked to smoser yesterday, but he didn't mention uploading/sponsoring
[17:14] <pitti> we just talked about the actual changes needed
[17:14] <pitti> soren: can you help here?
[17:14] <cjwatson> I've promoted m2crypto
[17:15] <pitti> in terms of review/sponsoring/testing ec2-init?
[17:15] <smoser> mdz, soren is good with my changes and is trying to incorporate and will get a new version in karmic
[17:15] <mdz> soren is away, I'll need someone else to pick that up
[17:15] <ttx> mdz: zul can do that.
[17:15] <mdz> ttx, ok, please confirm that he will do it today
[17:15] <ttx> mdz: he's been watching the MIRs to see them to completion;
[17:16] <mdz> ttx, can zul also take care of the test suite in m2crypto?
[17:16] <zul> yeah I will do it today
[17:16] <slangasek> [ACTION] zul to get new ec2-init sorted today
[17:16] <MootBot> ACTION received:  zul to get new ec2-init sorted today
[17:16] <mdz> cjwatson, odd, euca2ools was already in main
[17:16] <cjwatson> mdz: yes, I promoted it before noticing that it had an unpromoted dep
[17:16] <mdz> so with m2crypto promoted, and ec2-init getting promoted today, that should be the last of it
[17:17] <cjwatson> and decided it didn't matter so much since we knew we were going to do it anyway
[17:17] <mdz> remaining EC2 bugs are at
[17:17] <mdz> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=ec2-images
[17:17] <cjwatson> it's been whining at us in karmic_probs for a bit
[17:18] <mdz> one outstanding item I don't think we have a bug for on that list...switching vmbuilder to use seed tasks rather than the hardcoded package list for karmic
[17:18] <mdz> do we want to attempt that for beta?
[17:18] <cjwatson> I thought that was committed
[17:18] <mdz> branch?
[17:18] <cjwatson> you committed it, did you not?
[17:19] <cjwatson> that was the one I sent a patch for
[17:19] <mdz> no, I committed the seed change
[17:19] <mdz> smoser, have you tested the vmbuilder patch?
[17:20] <cjwatson> oh, you just said "thanks for the patch", I took that as meaning you'd committed it :)
[17:20] <smoser> i've not done that. i can do it. is there a bug for that explicitly ?
[17:20] <smoser> i have to verify that the uec seed has my latest adds to the package list (linux-virtual and linux-ec2)
[17:20] <mdz> smoser, it does
[17:20] <cjwatson> mdz: the seed doesn't include libc6-i686, but the bug we were trying to fix (bug 427288) says that we need both libc6-i686 and libc6-xen
[17:20] <cjwatson> is this an error?
[17:21] <mdz> smoser, please test the vmbuilder patch, compare the installed package list in the image, and if it looks OK, commit
[17:21] <slangasek> libc6-i686 is wanted on UEC; libc6-xen is wanted on EC2
[17:21] <mdz> since we're using one image for both, we need both
[17:21] <cjwatson> ok, is it harmful to have both?
[17:21] <mdz> cjwatson, I just applied your patch
[17:21] <mdz> smoser, should we add both to the seed?
[17:21] <slangasek> cjwatson: nope
[17:21] <slangasek> (now that this bug is fixed, anyway :)
[17:21] <cjwatson> mdz: yeah, I was just going from what was in vm-builder
[17:22] <cjwatson> I'll add libc6-i686 to the seed
[17:22] <mdz> cjwatson, thanks
[17:22] <cjwatson> (done)
[17:23] <slangasek> [ACTION] smoser to test vmbuilder patch to use germinate
[17:23] <MootBot> ACTION received:  smoser to test vmbuilder patch to use germinate
[17:23] <smoser> well, wait. libc6-xen can only be added on i387
[17:23] <smoser> i386
[17:23] <smoser> can that be done with a seed ?
[17:23] <cjwatson> yes
[17:23] <slangasek> yes
[17:23] <mdz> smoser, yes
[17:23] <cjwatson> I just did
[17:23] <smoser> perfect.
[17:23] <smoser> then i'll test.
[17:23] <cjwatson> note that it will be a bit over an hour before the Task field for libc6-i686 in the archive is updated, but you can test the rest of it before then
[17:24] <mdz> smoser, isn't bug 429169 fixed by installing linux-ec2?
[17:24] <smoser> yes.
[17:24] <mdz> smoser, Fix Committed then?
[17:25] <smoser> its fix-committed in vmbuilder.
[17:25] <mdz> other targeted bugs for ec2:
[17:25] <mdz> bug 431103
[17:25] <mdz> bug 423297
[17:26] <mdz> bug 414997
[17:26] <mdz> er
[17:26] <mdz> bug 423497
[17:26] <smoser> zul is working on 431103, and believes he'll have something for kernel team later today.
[17:26] <mdz> bug 431255
[17:26] <mdz> is there actually a kernel upload planned for beta?
[17:27] <mdz> smoser, are any of the above bugs not going to be fixed today?
[17:27] <pitti> hm, we just had one last night? (kernel upload)
[17:28] <smoser> zul has been working on 431103 and has something to go to kernel team later today
[17:28] <cjwatson> I'd like to know when the last kernel upload will be so that I can build d-i, certainly ...
[17:28] <mdz> smoser, is it a blocker for beta or not?
[17:28] <smoser> i actually dont know where soren is on 414997 (run-once-per-ami)
[17:28] <mdz> https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs?field.tag=ec2-images
[17:28] <smoser> sudoers (423497) is fixed in vmbuilder trunk
[17:29] <lool> (I personally would love to know whether the ARM kernels will get a merge from main kernel and an upload too)
[17:29] <lool> And I expect linux-ec2 needs one too
[17:29] <smoser> 431255 (S99 user data) is next on the todo list for today
[17:29] <mdz> smoser, 431103 is open on ec2-init, but you're saying it's actually a kernel problem? if so, please move it to the linux package
[17:29] <cjwatson> hmm, new kernels in binary new
[17:29]  * cjwatson processes
[17:29] <mdz> who can help smoser get his vmbuilder changes into the archive today?
[17:29] <smoser> mdz, 431103 is a big deal, it absolutely has to be fixed. but whether or not it blocks beta i dont know.
[17:30] <lool> happy to sponsor
[17:30] <mdz> smoser, IIRC you said most people don't even seem to know that the key is visible on the console ;-)
[17:30] <slangasek> I'm also available to help with vmbuilder sponsorship
[17:30] <cjwatson> me if nobody else, but I'll be out from 1700 UTC to c. 2100 UTC
[17:30] <lool> or perhaps someone in his TZ
[17:30] <lool> slangasek: Ok I take the first shift  :-)
[17:30] <mdz> smoser, please send me an email confirming status at the end of the day
[17:30] <mdz> anything else on EC2?
[17:30] <smoser> mdz, yes, i've said that, and its true. but the fact that no  one cares about security doesn't mean it doens't have to be secure
[17:31] <mdz> smoser, I think that means it can miss beta
[17:31] <smoser> regarding vmbuilder changes... they dont *have* to be in the archive. we're building the nighly builds with trunk vmbuilder. so they get the changes.
[17:31] <mdz> can someone follow up with the kernel team re: refreshing ARM and EC2 kernels as lool mentioned?
[17:32] <mdz> smoser, oh, then that can wait until next week I guess
[17:32] <lool> Does someone sync with pgraner later today?
[17:32] <mdz> rtg is here at plumbers
[17:32] <mdz> pgraner is on a plane and I don't know if I will speak to him today
[17:33] <lool> Perhaps someone at plumbers can talk to rtg?
[17:33] <slangasek> [ACTION] slangasek to follow up with the kernel team wrt ARM, EC2 kernel refreshes for beta
[17:33] <MootBot> ACTION received:  slangasek to follow up with the kernel team wrt ARM, EC2 kernel refreshes for beta
[17:33] <lool> thanks
[17:33] <slangasek> probably more effective to do that in person, yes
[17:33] <mdz> slangasek, just to be clear, I don't know of any urgent need to refresh the EC2 kernel for beta, only a vague worry that it might be concealing regressions
[17:34] <mdz> but I would like to know what their general strategy is wrt keeping those packages up to date, since it doesn't seem to be "update them whenever the trunk changes"
[17:34] <mdz> can we move on to eucalyptus?
[17:34] <slangasek> mdz: right, I want a consistent set of kernel packages for beta, not have half of them lagging behind the current upstream release...
[17:34] <ttx> Euclyptus tracked bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=eucalyptus
[17:35] <slangasek> [LINK] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=eucalyptus
[17:35] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=eucalyptus
[17:35] <mdz> ok, eucalyptus
[17:35] <mdz> unfortunately I don't think this list is complete
[17:35] <mdz> there are a lot of untriaged bugs on the eucalyptus source package as well
[17:35] <mdz> https://bugs.edge.launchpad.net/ubuntu/+source/eucalyptus
[17:35] <mdz> this is in very bad shape at the moment in terms of beta
[17:36] <mdz> we are going to be putting in extra hours I'm sure
[17:36] <ttx> mdz: I'll try to sync with nurmi later to see what failed in my cloud install.
[17:36] <mdz> there were several tests done overnight which identified new bugs
[17:36] <mdz> there seem to be problems with the cloud installer, with the eucalyptus packages, and with eucalyptus upstream
[17:37] <mdz> I haven't processed all of the mail on this overnight, and it is changing rapidly
[17:37] <cjwatson> I'd appreciate somebody reviewing the eucalyptus package in unapproved
[17:37] <mdz> the one I uploaded?
[17:37] <cjwatson> the one I uploaded following yours (which you apparently didn't upload to anything other than a PPA)
[17:38] <cjwatson> Dustin and I fixed four additional bugs over the two you fixed
[17:38] <mdz> cjwatson, I uploaded it to a PPA first and then to the archive later, or at least that's what I intended
[17:38] <pitti> looking
[17:38] <cjwatson> either it didn't make it to the archive, or it was rejected
[17:38] <pitti> cjwatson's version includes both
[17:38] <cjwatson> anyway, my upload includes yours, assuming you didn't have anything uncommitted to bzr
[17:38] <mdz> bah
[17:38] <kirkland> i didn't see it make the archive, but i was unsure, so i bumped the version and marked unreleased for my 3 fixes
[17:38] <mdz> cjwatson, nothing uncommitted to bzr, no
[17:39] <mdz> does cjwatson's upload include kirkland's changes?
[17:39] <cjwatson> yes
[17:39] <pitti> three changes from him, yes
[17:39] <mdz> ok, we need to get that in and building ASAP
[17:39] <mdz> and new server ISOs with it
[17:40] <cjwatson> I think that fixes all the identified beta-critical installer issues
[17:40] <mdz> great
[17:40] <mdz> which leaves the eucalyptus packaging and upstream issues
[17:40] <cjwatson> slight emphasis on think there
[17:40] <mdz> cjwatson, have you done a test install with it?
[17:40] <cjwatson> no
[17:41] <mdz> I suffered yesterday trying to hand-hack an iso to test it
[17:41] <cjwatson> I'll be back later tonight and can do a test install
[17:41] <ttx> mdz: what packaging fixes are you thinking about ?
[17:41] <slangasek> trigger set for another server ISO w/ the pending eucalyptus
[17:41] <mdz> ttx, getting auto registration working? fixing those incorrect dependencies?
[17:42] <mdz> triaging that long list of bugs on the package
[17:42] <mdz> slangasek, thanks
[17:42] <cjwatson> which incorrect dependencies?
[17:42] <cjwatson> dustin fixed the dhcp one
[17:42] <mdz> bug 435130
[17:42] <ttx> ok.
[17:43] <mdz> kirkland, any luck with bug 432154?
[17:43] <cjwatson> oh, that thing, ugh
[17:43] <pitti> eucalyptus accepted
[17:43] <mdz> he said yesterday that he had a fix for it, just needed to change the kvm invocation
[17:43] <mdz> is that by any chance in his eucalyptus changes?
[17:43] <cjwatson> no
[17:43] <mdz> ok, that's beta-critical
[17:44] <cjwatson> I have to go in 17 minutes at the latest, and ideally need to have a bit of getting-ready-to-go-out time before that
[17:44] <mdz> I don't know anything about bug 385435
[17:44] <kirkland> mdz: it works for me with driver='scsi' or driver='virtio'
[17:44] <kirkland> mdz: they're using driver='phy'
[17:44] <kirkland> mdz: waiting on nurmi to verify
[17:44] <mdz> kirkland: I don't know the implications of that. will it be fixed today?
[17:44] <kirkland> mdz: jdstrand found that if he tried to attach/detach 28 times, it would fail
[17:44] <kirkland> mdz: i don't know
[17:45] <jdstrand> fwiw, it works for me with usb too
[17:45] <mdz> I desperately need someone to triage https://bugs.edge.launchpad.net/ubuntu/+source/eucalyptus
[17:46] <mdz> kirkland, can you do that today?
[17:46] <kirkland> mdz: triage 50ish bugs ... is this higher priority than getting our cloud in the suite running?
[17:47] <jdstrand> kirkland: actually, I was using nurmi's test case almost exactly, and it was working here. I'm not sure that attach is broken anymore (other than the 28 times issue I discovered this morning)
[17:47] <mdz> kirkland, I don't think I can answer that until I get through the emails from dan and thierry
[17:47] <mdz> but it needs to be done today, otherwise we don't know where we stand
[17:47] <kirkland> jdstrand: i agree that i don't think anything is actually "broken", i think it's a matter of usage
[17:47] <kirkland> mdz: agreed
[17:47] <kirkland> mdz: okay, i'll triage those today
[17:47] <jdstrand> 'phy' with attach-device works... we need feedback from nurmi
[17:47] <mdz> thank you
[17:48] <ttx> kirkland: I'll try to spend a few evening cycles on that with you
[17:48] <mdz> anything else urgent on eucalyptus we haven't discussed here?
[17:48] <ttx> mdz: yes
[17:49] <ttx> I spent most of the day trying to make sure we had all the beta-critical bugs filed
[17:49] <ttx> basically running through the install and making it work
[17:49] <mdz> what's the URL for the list of those bugs?
[17:50] <ttx> I'm almost there, will debug what's left with nurmi tonight...
[17:50] <ttx> and file what is not due to my own stupidity or test setup
[17:50] <ttx> I didn't encounter anything new.
[17:50] <ttx> The only thing is that MANAGED-NOVLAN routing issue I need to debug first
[17:50] <ttx> and some booting errors I need to test the latest UEC image against
[17:51] <mdz> ok
[17:52] <ttx> I also will reinstall tomorrow with the daily CD
[17:52] <ttx> to confirm the fixes.
[17:53] <mdz> we'll continue testing here in portland as well
[17:53] <slangasek> does that cover us for eucalyptus, then (and for server)?
[17:54] <ttx> I need to go now anyway, to negociate evening work with wife ;)
[17:54] <mdz> slangasek, such as it is :-/
[17:54] <mdz> it's an area of great concern right now
[17:54] <mdz> and I can't be sure yet that we've covered all of the critical issues even. we'll see what comes out of that triage pass today
[17:55]  * slangasek nods
[17:55] <cjwatson> I have to go I'm afraid, slangasek has my foundations update
[17:55] <mdz> sorry to have taken up so much time with server
[17:55] <slangasek> [TOPIC] Security Team
[17:56] <MootBot> New Topic:  Security Team
[17:56] <jdstrand> o/
[17:56] <slangasek> kees: here?
[17:56] <slangasek> jdstrand: hello
[17:56] <kees> jdstrand is doing it today
[17:56] <jdstrand> slangasek: I'll lead today
[17:56] <slangasek> ok
[17:56] <kees> I'm here to fill in any details
[17:56] <slangasek> there were just two bugs that bubbled up as needing attention release-wise
[17:56] <slangasek> bug #429872, bug #131976
[17:56] <jdstrand> kees has decided to work on bug #429872
[17:56] <jdstrand> Progress is ongoing (cosmetic, not for beta)
[17:57] <jdstrand> kees added apparmor to the initramfs to avoid races where binaries with profiles could be started before apparmor (and thus run unconfined). This inadvertently reintroduced bug #131976 for karmic, which he fixed in 2.3.1+1403-0ubuntu22. This was accepted several hours ago
[17:57] <pitti> second bug is in karmic
[17:57] <pitti> ... fix
[17:57] <jdstrand> as for other stuff
[17:57] <jdstrand> noisy console output from ufw is fixed in 0.29-4ubuntu1. kees uploaded a fix for noisy apparmor console output (bug #435285), but not totally resolved. fix by kees in Vcs, cosmetic, not for beta
[17:58] <jdstrand> mdeslaur fixed important apparmor userspace bugs (bug #427966 and bug #431929). With these fixes, apparmor should be in good shape
[17:58] <jdstrand> I worked on libvirt/apparmor integration bugs and believe they should now all be fixed in 0.7.0-1ubuntu8:
[17:58] <jdstrand> bug #432581 bug #435527 bug #432810
[17:58] <jdstrand> some of my investigation into attach/detach led to progress on bug #432154. my testing of that bug shows it may no longer be a problem (as mentioned)
[17:59] <jdstrand> the above combined should completely fix bug #431090, which no longer needs (or has) a workaround. I've asked eucalyptus upstream to also fully test and get back to me if there are any problems. They agreed and are doing so (no new problems reported so far wrt apparmor integration)
[17:59] <jdstrand> kees pinged Tresys about selinux bug #434084 and they are looking into it
[17:59] <jdstrand> One regression-potential bug remains: bug #436221 (firefox-3.5 jaunty -> karmic upgrade). Fix for this and a few profiling refinements is pending. talked to asac this morning-- he will merge
[17:59] <jdstrand> In terms of features, mdeslaur got his apache2 FFe bug #430812 in before Beta. everything else is same as last week
[18:00] <mdz> I'm finding it hard to pick out which of the above bugs are open
[18:00] <jdstrand> mdz: 434084 (selinux)
[18:01] <jdstrand> 435285 (apparmor console output)
[18:01] <jdstrand> 429872 (apparmor Profile doesn't conform to protocol)
[18:01] <slangasek> jdstrand, kees: yes, in the future it would be helpful if the report could be limited to those issues that are outstanding and regarded as critical for release
[18:01] <jdstrand> 436221 (firefox-3.5 jaunty -> karmic upgrade)
[18:02] <jdstrand> slangasek: sure-- we are new to this. I've already made a note to create https://wiki.ubuntu.com/SecurityTeam/KarmicReleaseStatus
[18:02] <slangasek> ok, thanks
[18:02] <mdz> jdstrand, thanks
[18:02] <kees> slangasek: ok, noted.  afaict 434084 (selinux) is in universe, so not a beta blocker. 435285 and 429872 are cosmetic and not beta blockers.  jdstrand is 436221 considered a blocker?
[18:03] <jdstrand> kees: I think 436221 doesn't bite today, but will as soon as 3.5.3 is released, and that my happen while beta isos are available for people
[18:04] <slangasek> please target/milestone that bug accordingly
[18:04] <jdstrand> it requires a jaunty user have ff35 installed, 3.5.3 is uploaded to the archive for -security, then the user upgrades to beta
[18:04] <jdstrand> if that is an acceptable risk, the bug can be a non-blocker
[18:04] <kees> slangasek: I've adjusted 434084 435285 429872 to be non-beta.
[18:05] <slangasek> jdstrand: I would prefer we get that bug fixed
[18:05] <jdstrand> slangasek: it is committed in bzr, and a merge proposed
[18:05] <slangasek> especially as it seems the fix is already known
[18:05] <jdstrand> slangasek: talked to asac this morning and he is committing it. I'll get with him to upload it
[18:05] <slangasek> thanks
[18:05] <ace_suares> hello, edubuntu meeting here??
[18:06] <slangasek> any other concerns on security release-wise?
[18:06] <ace_suares> #startmeeting
[18:06] <MootBot> ace_suares, There is already a meeting in progress.
[18:06] <ace_suares> oh
[18:06] <jdstrand> slangasek: I don't have anything
[18:06] <slangasek> ok
[18:06] <slangasek> ace_suares: sorry, the Ubuntu release meeting is running long; we'll try to wrap up ASAP
[18:07] <slangasek> [TOPIC] Foundations Team
[18:07] <MootBot> New Topic:  Foundations Team
[18:07] <ace_suares> okay no worries edubuntu meeting will probably have low attendence. Take your time.
[18:07] <slangasek> jdstrand: thanks for the report
[18:07] <slangasek> as cjwatson had to leave, he braindumped to me beforehand
[18:07] <slangasek> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic
[18:07] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic
[18:08] <slangasek> bug status updated on https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic; a number of bugs from the agenda were already fixed
[18:08] <slangasek> who wants to be responsible for bug 412437? it's on the foundations list on the agenda, but it's in universe and tagged ct-rev, so I don't think it should be
[18:08] <slangasek> about half of the major outstanding boot bugs fixed this week; progress continues on the rest
[18:08] <slangasek> one major installation bug left, IMO (bug 431786, clock reset after partitions are created), which is fixable by beta; otherwise, current tests have been moderately reassuring for the most part
[18:08] <slangasek> lots of usb-creator work this week, especially landing PolicyKit support
[18:08] <slangasek> UbuntuSpec:software-library: now in by default, although not without naming controversy ... Michael has been working hard on bugs here
[18:08] <slangasek> UbuntuSpec:foundations-karmic-bootspeed-targets: now in bug-fixing stage
[18:08] <slangasek> UbuntuSpec:foundations-karmic-oemconfig: done as far as we're going to for karmic; some work carries over to lucid
[18:08] <slangasek> UbuntuSpec:foundations-karmic-wubi: feature work deferred; however it at least now works for me again (woohoo), although Agostino is still having some GRUB problems which appear not to be universal
[18:08] <slangasek> plus personally I've been hoiked into eucalyptus fire-fighting so am a bit behind on bugs
[18:08] <slangasek> EOF
[18:08] <slangasek> Riddelll: I noted to cjwatson that for 412437, I had suggested removing the package; he agrees in principle, but wants it cleared by Kubuntu folks first
[18:09] <slangasek> Riddelll: do you have an opinion?
[18:09] <pitti> naming controversy> now being renamed to software-center
[18:09] <slangasek> AIUI the kgrubeditor package is perpetually broken, and isn't present in Debian either
[18:09] <Riddelll> slangasek: yeah I guess that has to go
[18:10] <slangasek> Riddelll: ok - could you ack it in the bug, and I can schedule removal?
[18:10] <Riddelll> done
[18:10] <slangasek> pitti: I spoke with Keybuk yesterday, and he has a set of final ubuntu-boot fixes to land for beta which he won't be able to upload until Tuesday European time (because he's in the air on Monday)
[18:11] <slangasek> pitti: will you be available to review those in the unapproved queue and get them in that day, so they can land ASAP?
[18:11] <pitti> ok, I'll make sure to review them as quickly as possible
[18:11] <pitti> yes, absolutely
[18:11] <pitti> and trigger CD builds when they are in
[18:11] <slangasek> thanks
[18:12] <slangasek> (I haven't seen the changes in question yet, of course, so please review them to make sure they're freeze-suitable - I just know they're coming and are supposed to fix bugs we need fixed)
[18:13] <pitti> of course
[18:13] <slangasek> any questions for foundations?
[18:13] <pitti> what could possibly break.. :-P
[18:14] <slangasek> heh
[18:14]  * pitti reviews and accepts ec2-init
[18:14] <slangasek> [TOPIC] MOTU
[18:14] <MootBot> New Topic:  MOTU
[18:14]  * sistpoty|work waves
[18:15] <sistpoty|work> ftbfs is still a major concern
[18:15]  * slangasek nods
[18:15] <sistpoty|work> fixes trickle in at at too low rate imo
[18:15] <sistpoty|work> others than that FFe request seem to have come down a little bit this week
[18:15] <sistpoty|work> I guess that's it from my side
[18:16] <slangasek> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909-karmic.html
[18:16] <MootBot> LINK received:  http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909-karmic.html
[18:16] <slangasek> that's the current ftbfs report, right?
[18:16] <sistpoty|work> right
[18:16] <sistpoty|work> it now has fixed packages marked as superseeded :)
[18:16] <slangasek> ok, cool
[18:17] <sistpoty|work> thanks to wgrant!
[18:17] <slangasek> has this list been pointed to on ubuntu-devel?
[18:17] <sistpoty|work> not too sure actually, I don't think so
[18:17] <slangasek> I can include a mention in my next u-d-a "here's what we need to do" mail, but in the meantime a post to u-d is probably a good idea?
[18:18] <sistpoty|work> slangasek: excellent! :)
[18:18] <slangasek> ok
[18:18] <slangasek> anything else?
[18:19] <sistpoty|work> oh, cjwatson fixed ia64 :)
[18:19] <sistpoty|work> apart from that, nothing from my side
[18:19] <slangasek> ok
[18:19] <ogra> slangasek, given that edubuntu just rna in here and that they start to have a proper release again, they should get a spot in this meeting from lucid on imho
[18:19] <ogra> *ran
[18:20] <ogra> not sure it makes sense this round anymore ... LaserJock ?
[18:21] <slangasek> ogra: no, we don't need any more context switches in the meeting than we already have; problems affecting edubuntu should be brought up with the relevant teams, or brought up ad-hoc
[18:21]  * sistpoty|work gotta run now... cya
[18:21] <slangasek> #endmeeting
[18:21] <MootBot> Meeting finished at 12:21.
[18:21] <ogra> slangasek, ok
[18:21] <lool> slangasek: thanks
[18:21] <ace_suares> #startmeeting
[18:21] <MootBot> Meeting started at 12:21. The chair is ace_suares.
[18:21] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:21] <slangasek> anyway, let's clear the floor so that edubuntu can have their meeting :)
[18:21] <pitti> thanks all
[18:21] <slangasek> ace_suares: sorry, thanks for your patience
[18:21] <slangasek> and thanks, all
[18:21] <ace_suares> no problem
[18:21] <ace_suares> let the release rock !
[18:22] <LaserJock> ace_suares: agenda?
[18:22] <ace_suares> [Topic] Agenda
[18:22] <MootBot> New Topic:  Agenda
[18:22] <ace_suares> I think there is no agenda other then the usual weekly reports stuff. We can add:
[18:22] <ace_suares> - Release DVD; Wiki; Sabayon; Handbook;
[18:22] <ace_suares> anything else?
[18:22] <ace_suares> PRESENT
[18:23] <LaserJock> I'd like to discuss a tad bit about the EC
[18:23] <LaserJock> concerning the email I sent regarding Requests for Consideration (to borrow a Debian term)
[18:24] <ace_suares> yeah cool. One more: rmeeting rescheduling so LJ can be available, and european partners too
[18:25] <ace_suares> [Agenda]\
[18:25] <ace_suares> wo
[18:25] <ace_suares> [18:25] <ace_suares> Fri Sep 25 17:00 UTC in #ubuntu-meeting
[18:25] <ace_suares>  * Weekly Reports
[18:25] <ace_suares>  * Release DVD
[18:25] <ace_suares>  * LaserJocks Request for Comments (EC)
[18:25] <ace_suares>  * Sabayon?
[18:25] <ace_suares>  * Handbook?
[18:25] <ace_suares>  * Meeting Schedule
[18:25] <ace_suares> [TOPIC] Weekly Reports
[18:25] <MootBot> New Topic:  Weekly Reports
[18:25] <ace_suares> Any one got something to report?
[18:26] <LaserJock> not a lot in the last week from me
[18:26] <LaserJock> but the DVDs are being built daily
[18:26] <LaserJock> Beta is coming up quick
[18:26] <LaserJock> we need to get amd64 tested this time
[18:27] <LaserJock> for Alpha6 we didn't get any testing so it had to be dropped from the release
[18:27] <LaserJock> we also need to get updated testing instructions on iso.qa.ubuntu.com
[18:27] <LaserJock> as what's on there now points to Addon testing
[18:28] <ace_suares> [Topic] Release DVD
[18:28] <MootBot> New Topic:  Release DVD
[18:28] <ace_suares> LaserJock: Can you make like a schedule for when things need to be tested?
[18:28] <ace_suares> I cna then send remionders to the list.
[18:28] <ogra> beta is on thu
[18:28] <ogra> isos are being built from tue on
[18:29] <ogra> https://wiki.ubuntu.com/KarmicReleaseSchedule
[18:29] <ogra> you usually can count on freeze for an alpha/beta/rc being the tue before the respective release
[18:30] <ogra> from then on testing should start
[18:30] <ace_suares> https://wiki.edubuntu.org/EdubuntuTesting is this page up to date? If not we want to make it up to date before tue and move
[18:30] <ace_suares> oh sorry not move he eh
[18:30] <ace_suares> But it should be Edubutu/Release/9.10/Testing or something
[18:30]  * ogra wouldnt make that versioned
[18:31] <ogra> just adjust the content for a new release, so you dont create pages over and over
[18:31] <ace_suares> So what, I can work out a schedule my self looking at the release page? I can do and then will sned to devel and then you can approve or change and then i can send reminders to the list. We should alsomention zsync in 9.04 is broken and need package from 9.10 OR use rsync
[18:32] <ace_suares> Then it should be Edubuntu/Testing
[18:32] <ace_suares> ogra: it says please dont' edit this page so I am stadning off...
[18:32] <ogra> or Edubutu/Release/Testing ... as you like :)
[18:32] <ace_suares> yeah okay better.
[18:32] <ogra> its bound to the isotracker
[18:32] <ogra> thats why it has that note
[18:32] <ace_suares> what is an isotracker?
[18:33] <ogra> the thing LaserJock mentioned above :)
[18:33] <ogra> http://iso.qa.ubuntu.com
[18:33] <MootBot> LINK received:  http://iso.qa.ubuntu.com
[18:34] <ace_suares> actually http://iso.qa.ubuntu.com/qatracker/build/edubuntu/all
[18:34] <ace_suares> hm it's still listed as an add-on ?
[18:34] <ogra> thats what LaserJock said ...
[18:35] <ogra> you should start using action items in your meeting ;)
[18:35] <ace_suares> sorry i am missing things obiviouyslly, must be visually challenged
[18:35] <ace_suares> so, who is going to simplify the test schedule so we can all try and motivate more poeple to test?
[18:36]  * LaserJock returns from checking on experiment
[18:36] <LaserJock> I can put together a list and send it to -devel
[18:37] <LaserJock> stgraber can probably make changes in the tracker
[18:37] <ace_suares> [Action] LaserJock puts together a list of dates when we need testing and posts it to -devel
[18:37] <MootBot> ACTION received:  LaserJock puts together a list of dates when we need testing and posts it to -devel
[18:37] <ace_suares> [Action] Ace volunteers to write up a Testing page that outlines the simple procedure to test, links to all relevant procedures etc
[18:37] <MootBot> ACTION received:  Ace volunteers to write up a Testing page that outlines the simple procedure to test, links to all relevant procedures etc
[18:37] <ace_suares> stgraber: are you here?
[18:38] <LaserJock> I'm not sure if we need that page anymore though
[18:38] <LaserJock> the QA team has their own wiki for test cases
[18:38] <ace_suares> I think we need a page that outlines what we expect from our community and then link tru to the various pages that are relevant
[18:39] <ace_suares> Like a starting point that is edubuntu specific
[18:39] <ace_suares> but of course I will immediately agree with LaserJock if that means I can keep on doing nothing :-)
[18:39] <LaserJock> well
[18:39] <LaserJock> we should have a Testing page that sends people to the tracker, etc.
[18:39] <ogra> it would need a set of cases on http://testcases.qa.ubuntu.com/Testing/Cases/ i guess
[18:39] <LaserJock> but the actual "this is what you test" wiki page is on the QA wiki
[18:40] <ogra> unless you can add individual links to the tracker
[18:40] <LaserJock> I think the tracker links to a particular page on testcases.qa.u.c already
[18:40] <LaserJock> if we have permission to edit that one we should just do that
[18:40] <ogra> yep http://testcases.qa.ubuntu.com/Testing/Cases/EdubuntuDesktop
[18:41] <ogra> and http://testcases.qa.ubuntu.com/Testing/Cases/EdubuntuAddOnCD
[18:41] <LaserJock> hmm, http://testcases.qa.ubuntu.com/Install/EdubuntuAddonCd is the one it links to, which is not optimal :-)
[18:41] <ogra> as well as http://testcases.qa.ubuntu.com/Testing/Cases/LTSPServer if you want to include that ( alkisg seemed to have interest here )
[18:42] <ace_suares> [Action] Ace is not volunteering to set up a testing page anymore due to unexpected complexities
[18:42] <MootBot> ACTION received:  Ace is not volunteering to set up a testing page anymore due to unexpected complexities
[18:42]  * alkisg volunteers to test the ltsp installation
[18:42] <LaserJock> ok, well somebody should get the testing thing all figured out
[18:43] <ace_suares> Sorry guys, my time is almost up here
[18:43] <ogra> ace_suares, s/complexities/challenges/
[18:43] <ogra> ;)
[18:44] <LaserJock> ok, well
[18:44] <ace_suares> ogra: yeah. right :-)
[18:44] <LaserJock> is there anything that's quick that IRC is good for?
[18:44] <LaserJock> else we can shove things onto edubuntu-devel for discussion
[18:44] <ace_suares> LaserJock: I don't know.
[18:45] <LaserJock> I had a good discussion with highvoltage the other day concerning the Edubuntu Council and providing more leadership/direction for contributors
[18:45] <LaserJock> one of the results is that email I sent
[18:45] <ace_suares> LaserJock: Normally, i'd put up a page and in doing so figuring out all things that are related, asking around and such, but if it's already doubtful if we need such page then I'm not even starting. Once bitton, twice shy.
[18:46] <ace_suares> [Topic] EC and Request for... Confirmation?
[18:46] <MootBot> New Topic:  EC and Request for... Confirmation?
[18:46] <ogra> first of all you should get a quorum again
[18:46] <LaserJock> yes
[18:46] <ace_suares> how much is the quorum ?
[18:46] <LaserJock> I believe we are working with the CC on that
[18:47] <ogra> three at least i think
[18:47] <LaserJock> we have 3
[18:47] <ace_suares> there is three is nt there?
[18:47] <ogra> but CC needs to approve
[18:47] <LaserJock> we'd like to get 2 more
[18:47] <ogra> who is EC atm ?
[18:47] <LaserJock> stgraber, highvoltage, and myself
[18:47] <ace_suares> https://wiki.ubuntu.com/Edubuntu/WikiSite/Teams/EdubuntuCouncil
[18:48]  * ogra is definately ready to retire, i think i'm still in the LP team
[18:48] <LaserJock> unfortunately all busy people :(
[18:48] <LaserJock> ogra: I think you got removed
[18:48] <ogra> ah, good
[18:48] <LaserJock> I did some cleanup and got the CC mad at me ;-)
[18:48] <ogra> heh
[18:48] <ace_suares> happens to the best then :-)
[18:48] <LaserJock> ace_suares: if you're not getting yelled at you're not doing enough!
[18:49] <ogra> ++
[18:49] <ace_suares> LOL
[18:50] <LaserJock> I'm working on getting a task list to finish of Karmic
[18:50] <ace_suares> Well, the problem is after being yelled at I'd tend to try to respect the points of the yeller and postpone working till a resolve is there, but that's maybe the wrong thing to do. I don't know.
[18:50] <ace_suares> Noting really moves forward.
[18:50] <LaserJock> ace_suares: they key I think is getting resolution quickly and moving on
[18:50] <LaserJock> we're stalling a lot
[18:50] <ace_suares> Now Waiting for the EC
[18:50] <ace_suares> And then it turns out that the EC has no quorom unless the CC approves
[18:50] <LaserJock> no, we have a quorom
[18:51] <LaserJock> barely
[18:51] <LaserJock> but I believe we have it
[18:51] <ogra> right, three is enough
[18:51] <ace_suares> My enthusiasm meter is going 51%... 49%... 50.9%... 49%... 50.5%...
[18:51] <LaserJock> in any case, I'm not sure that we need to have such rigidity there
[18:51] <LaserJock> I think people are just wanting a bit more guidance and a bit more "leadership" for lack of a better term
[18:52] <ace_suares> Even my first proposal of today got shot down.
[18:52] <LaserJock> ace_suares: which one was that?
[18:52] <LaserJock> oh, we should discuss meeting schedule before leaving
[18:53] <ace_suares> Oh, never mind. My wife is calling me for dinner. I gotta go. Can someone else do endmeeting or do in need to close? Trying to follow the mootbot.
[18:53]  * stgraber waves
[18:53] <ace_suares> [Topic] meeting schedule
[18:53] <MootBot> New Topic:  meeting schedule
[18:53] <LaserJock> ace_suares: you need to end it
[18:53] <ace_suares> Last meeting it was decided that Highvoltage should reschedule the meetings so LJ can be included, but nothing happened.
[18:53] <ace_suares> #endmeeting
[18:53] <MootBot> Meeting finished at 12:53.
[18:53] <LaserJock> ace_suares: he contacted me
[18:54] <LaserJock> ace_suares: so we should be moving forward a bit on that one
[18:54] <LaserJock> stgraber: we need to get the Edubuntu info on iso.qa.ubuntu.com updated
[18:54] <LaserJock> stgraber: can you help with that?
[18:54] <ace_suares> Splendid! So by lack of a proposal at the table the next meeting is next friday same time? or?
[18:54] <stgraber> LaserJock: sure
[18:55] <LaserJock> ace_suares: maybe we should do that and if we get a new schedule figured out in the mean time we can change it
[18:55] <ace_suares> Yeah, that would be the normal thing to do.
[18:55] <LaserJock> stgraber: do you have time now or should I send an email?
[18:56] <ace_suares> Okay I'm off have a good time all. Enjoy your everyday of your life and don't fill it with worthless tasks.
[18:56] <ace_suares> Bye!
[18:56] <alkisg> bye ace_suares :)
[18:56] <Lns> bye ace_suares
[18:56] <stgraber> LaserJock: I'm connected to quandong right now, so I can do a quick DB change quite easily
[18:56] <LaserJock> stgraber: awesome, let's move to #edubuntu to free up the room
[18:57] <stgraber> ok