[14:00] <lool> Hi there
[14:00] <lool> Where's NCommander?
[14:00] <paulliu> hi
[14:01] <JamieBennett> hey
[14:01] <lool> ogra, GrueMaster, plars, davidm, JamieBennett, dyfet: meeting?
[14:01] <dyfet> hi
[14:01] <GrueMaster> if I must.
[14:01] <plars> yarg
[14:01] <JamieBennett> yup
[14:01] <ogra> oooh
[14:01]  * ogra totally forgot 
[14:01] <ogra> i'm so ddep into filing bugs atm
[14:01] <ogra> *deep
[14:02] <davidm> hello
[14:02]  * GrueMaster stragles out to get a fresh cup of caffeine.
[14:02] <lool> I guess we'll do without NC
[14:02] <lool> NCommander
[14:02] <lool> #startmeeting
[14:02] <MootBot> Meeting started at 08:02. The chair is lool.
[14:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:02]  * lool sighs on the lack of a meeting page
[14:03] <lool> Nor for last week, impressive
[14:03] <lool> [link] https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:03] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:04] <lool> First action on completing dove z0 d-i support was on ncommander
[14:05] <lool> But I don't think he worked further on it; I agree we should first confirm whether that's still a target since bjf was saying it might not be supported anymore
[14:05] <lool> move lubuntu seed to proper location and enable the meta on amd64 (dyfet)
[14:05] <lool> dyfet: ?
[14:06] <dyfet> oh...we want amd64 active for that?  Then I will change architecture to any
[14:06] <dyfet> That I think would be simplest...
[14:06] <lool> I don't see why lubuntu should be architecture specific
[14:06] <dyfet> I do not recall why this was done either originally
[14:06] <lool> This decision is usually defered to image building time because these cost QA and space
[14:07] <lool> dyfet: So what about the other bits?
[14:07] <lool> dyfet: Moving to proper location (/ubuntu-seeds)
[14:07] <dyfet> Agreed...and a quick tiny change :).  I had been trying to sync up with the other people using the branch to move the seed.  But it is a team maintained seed
[14:08] <davidm> NCommander, is here now
[14:08] <NCommander> #startmeeting
[14:08] <MootBot> NCommander, There is already a meeting in progress.
[14:08] <NCommander> ah
[14:08] <lool> dyfet: so carry on I guess
[14:08] <dyfet> okay
[14:08] <lool> [action] move lubuntu seed to proper location and enable the meta on amd64 (dyfet, c/o)
[14:08] <MootBot> ACTION received:  move lubuntu seed to proper location and enable the meta on amd64 (dyfet, c/o)
[14:09] <lool> setup meeting with ubuntu-moblin and report back here (lool, c/o)
[14:09] <lool> Had a meeting on Monday where we planned our various efforts
[14:09] <lool> A short summary is that there are some 4 parallel efforts going on or so
[14:09] <lool> We're trying to merge bug fixes from private jaunty ppa to public moblin ppa
[14:09] <lool> we're trying to merge karmic public ppa to karmic proper
[14:09] <lool> we're trying to fix more bugs
[14:10] <lool> we're trying to merge moblin 2.1
[14:10] <lool> (and we're also trying to make the jaunty bits public in some way)
[14:10] <lool> chrischeney will be tasked with the jaunty -> any merges
[14:10] <lool> paulliu keeps working on moblin 2.1
[14:10] <lool> rest of OEM folks work on bug fixes and moblin 2.1
[14:10] <paulliu> lool: yes.
[14:11] <lool> We touched based on a plan for some partial moblin compliance too
[14:11] <lool> That's it
[14:11] <lool> Image is quite broken right now due to move to 2.1
[14:11] <lool> but that's life and we want moblin 2.1 more than a 100% karmic based image which doesn't seem atteinable anymore
[14:11] <paulliu> lool: Update mutter-moblin should brings everything back.
[14:11] <lool> file question against soyuz on PPA size (paulliu, c/o)
[14:12] <lool> paulliu: ^ did you file that?
[14:12] <GrueMaster> lool: how come I wasn't invited to the meeting?
[14:12] <paulliu> lool: Ah. Not yet. (c/o)
[14:12] <GrueMaster> Seeing as how I'm doing the compliance testing.
[14:12] <paulliu> lool: But we haven't have a new PPA.
[14:12] <lool> GrueMaster: We only discussed how to organize package uploads and this was appended to the meeting, not really part of the agenda to start with
[14:13] <paulliu> lool: The current PPA size is large enough. If we want a new PPA we need to have the same size.
[14:13] <lool> GrueMaster: The only thing we discussed on this topic was basically that we want to keep this in a separate compliance ppa and perhaps base on jaunty
[14:13] <lool> paulliu: Do we want one?  Not sure we actually need one anymore
[14:13] <lool> paulliu: I guess not
[14:13] <paulliu> lool: yes. So let's delete that action.
[14:14] <lool> plars to update the bug workflow
[14:14] <lool> plars: ^
[14:14] <plars> that has been mostly completed, the only thing I hadn't done yet was add a section for moblin
[14:14] <lool> Ok thanks
[14:14] <plars> which I was kind of on the fence about one part, and that would be for the 'moblin' tag
[14:15] <plars> I was thinking it may not be necessary, since all moblin bugs are supposed to go into ubuntu-moblin
[14:15] <plars> however, after thinking about it some more, I could see how someone might file a bug against a non-moblin specific package, and it end up being in ubuntu with possibly nothing indicating that it happened on a moblin system
[14:15] <lool> plars: indeed not necessary for now but doesn't hurt much to plan for next cycle and start adding that perhaps?
[14:15] <lool> ack
[14:15] <plars> so I'm thinking it would still be useful to have
[14:15] <lool> plars: makes sense to have it IMO
[14:16] <plars> so I'm going to go ahead with that, and see about putting the hook in for it too
[14:16] <plars> we want the tag to just be 'moblin' right?
[14:16] <lool> GrueMaster to continue driving moblin compliance issues with the LinuxFoundation.
[14:16] <lool> plars: yeah
[14:16] <plars> or is something like 'ubuntu-umr' or 'ubuntu-moblin' more paletable?
[14:16] <plars> ok
[14:17] <GrueMaster> I talked with Ted Tso and a couple of test developers, found out what needs to be installed for testing compliance.
[14:18] <GrueMaster> There were a lot of missing bits, like locale info and a few other missing packages that the tests depend on.
[14:18] <GrueMaster> I'll add those in to the next test round.
[14:18] <GrueMaster> The list I have is non-distro specific, so once I know what ubuntu packages are needed, I'll request a meta package wrapper to be made.
[14:19] <lool> lool to add uboot-mkimage to the desktop ship seed to make dove images non-dependent on internet access
[14:19] <lool> done
[14:19] <lool> pushed today; need to see if that works as expected
[14:19] <GrueMaster> As to actual compliance, the final specification for 2.0 won't be released until after karmic.
[14:20]  * GrueMaster is done.
[14:20] <lool> [topic] UNR status
[14:20] <MootBot> New Topic:  UNR status
[14:20] <lool> njpatel: You around?
[14:20] <lool> njpatel: Any particular comments?
[14:21] <lool> AFAIK we're up to date on releases
[14:21] <lool> Except for a tentative humanity upload which I nacked
[14:22] <lool> Nothing particularly interesting to report
[14:22] <lool> [link] UNR Status
[14:22] <MootBot> LINK received:  UNR Status
[14:22] <lool> Ups
[14:22] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:22] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:22] <lool> No interesting bugs there
[14:22] <lool> Biggest issue with icon theme has been resolved by saying we keep what we have
[14:23] <GrueMaster> Apparently there was a new bug filed recently against maximus that isn't listed here.
[14:23] <lool> #?
[14:23] <GrueMaster> bug #421019
[14:23] <lool> If someone has some free cycles, there's an easy bug with translations of window-picker-applet where I outlined the necessary changes and they need implementation
[14:24] <GrueMaster> Ah, someone has already looked at it.
[14:25] <joaopinto> does it make sense to report such an obvious bug like flash failing to install from firefox plugin finder service ? Does anyone know a bug report about it ?
[14:25] <lool> Can't personally load it
[14:25] <lool> I mean it takes forever
[14:25] <joaopinto> ops, wrong channel, sorry :|
[14:25] <lool> GrueMaster: Is it properly milestoned etc.?
[14:25] <plars> my current concern with unr is that desktop-switcher seems unusable without reeking havoc
[14:25] <lool> plars: Indeed
[14:26] <GrueMaster> plars triaged this one.
[14:26] <lool> plars: So we tried clamping the worst issues last week but I still see it as a sore poin
[14:26] <plars> I wanted to talk to neil about it first before suggesting anything rash
[14:26] <lool> point
[14:26] <lool> plars: last times I looked into d-s issues, I gazed and thought we need to rewrite everything
[14:26] <lool> Problem is that we can't do that for karmic
[14:27] <lool> It should of course be a lucid spec to use a different mechanism for it
[14:27] <plars> lool: jason had suggested that it should just be a session option at login, which seems reasonable
[14:27] <plars> the on-the-fly switching is a neat trick, but doesn't seem to work well in practice
[14:27]  * StevenK shores
[14:27] <lool> plars: Yes; I suggested that too, months ago, but nobody had time to look into it
[14:27] <lool> StevenK: Hey; we're in UNR status
[14:27] <lool> topic is d-s
[14:27] <plars> it's the only really good option I've heard so far
[14:28] <StevenK> d-s is broken?
[14:28] <lool> plars: Cant do that in karmic though; I had in mind we should do our best to fix the biggest issues in karmic's
[14:28] <plars> StevenK: it never actually worked
[14:28] <StevenK> Sure it has, it's just ... fragile
[14:28] <lool> plars: Could you come up with the highest prio bugs in your eyes which we should fix for release?
[14:28] <plars> lool: right, but if d-s can't be stabilized enough, I think it needs to not be there.  It's breaking systems
[14:28] <plars> will do
[14:28] <lool> plars: It's an option
[14:29] <lool> plars: I think I'd need a summary of breakage from you if you could produce that
[14:29] <GrueMaster> hey, that would also reduce the image size.  Win.
[14:29] <lool> plars: That'd help convincing release team + design team that we want it out
[14:29] <lool> GrueMaster: Speaking of which
[14:29] <lool> GrueMaster: How did that effort go recently?
[14:29] <GrueMaster> I haven't had time to look into it.  I was busy withthe conference last week.
[14:30] <GrueMaster> I'm looking into it today.
[14:30] <StevenK> We need to wait until after beta for large-ish things anyway
[14:30] <lool> StevenK: anything WRT UNR?
[14:31] <StevenK> Yes, we're oversized.
[14:31] <lool> Right now?
[14:31] <lool> We seem to be at 686M
[14:31]  * StevenK checks again
[14:32] <StevenK> Okay, we were ... :-)
[14:32] <StevenK> We hit 714M this morning
[14:32] <lool> wow
[14:32] <lool> how come?
[14:33] <StevenK> I wasn't able to figure that out, sadly
[14:33] <lool> Ok; probably temporary bogosity
[14:33] <StevenK> But it looks like we dropped like a stone after that if we're at 686
[14:33] <lool> StevenK: any other bugs / highlights?
[14:33] <StevenK> I'll re-instate de after beta
[14:33] <lool> StevenK: are we in sync WRT seeds and upstream releases?
[14:34] <lool> StevenK: Well I remember pidgin crept in over the week end and I fixed it but it probably was accepted on monday only
[14:34] <lool> that might explain the big image
[14:34] <StevenK> I've not checked those, but we are probably too late to change either
[14:34] <lool> StevenK: Can you make sure you double check we're not out of date?
[14:34] <lool> StevenK: I'd hate if we would be missing any change, even the most trivial ones
[14:35] <StevenK> lool: I certainly will, when I'm working again
[14:35] <lool> Thanks
[14:35] <lool> [topic] moblin remix status
[14:35] <MootBot> New Topic:  moblin remix status
[14:35] <lool> StevenK: hey again!
[14:35]  * StevenK chuckles
[14:35] <lool> paulliu, StevenK: So it's quite borken right now
[14:35] <lool> paulliu: You say it's about to be mostly fixed?
[14:36] <paulliu> lool: yes. If you boot with a while screen. You just need to upgrade mutter-moblin.
[14:36] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-moblin
[14:36] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-moblin
[14:36] <paulliu> lool: I think it might not included in the built today.
[14:36] <lool> paulliu: Is it still booting into gnome?
[14:37] <StevenK> paulliu: So the current livefs needs a fixed mutter-moblin?
[14:37] <lool> I'll take care of the sources.list and apt preferences files in livecd-rootfs, but after beta
[14:37] <paulliu> StevenK: yes.
[14:37] <lool> paulliu: When was it uploaded?
[14:37] <lool> paulliu: We had a build an hour ago or so
[14:37] <paulliu> lool: one hour ago.
[14:37] <ogra> note that dues to a casper breakage we dont have ttys on live images
[14:37] <lool> mutter-moblin 0.40.0-0ubuntu0moblin6
[14:38] <lool> that's what we have
[14:38] <StevenK> Okay, we can organise a rebuild
[14:38] <ogra> so if you have a white screen there is no way to install anything on tty
[14:38] <paulliu> lool: ok. It's ok.
[14:38] <lool> ogra: Is that one fixed?
[14:38] <lool> paulliu: Cool
[14:38] <ogra> lool, slangasek said post beta
[14:38] <lool> paulliu: no rebuild needed then?
[14:38] <lool> ogra: Ok
[14:38] <paulliu> lool: no rebuild needed.
[14:38] <lool> Anything else on moblin for beta?
[14:38] <ogra> Bug 438678 filed ...
[14:38] <lool> plars, GrueMaster: ^?
[14:39] <GrueMaster> That tty issue may be related to a kernel bug I filed yesterday.
[14:39] <ogra> GrueMaster, it isnt
[14:39] <GrueMaster> ok
[14:39] <plars> lool: I've not had time to focus on moblin this week, couldn't say
[14:39] <paulliu> Is it only breaks Moblin??
[14:39] <ogra> nope
[14:39] <ogra> all live images
[14:39] <StevenK> No, it would affect everything
[14:40] <lool> Hmm if it's in the installed system too it certainly should be > medium
[14:40] <paulliu> ogra: OK. thanks. That should be the bug mentioned by Kevin Huang today afternoon.
[14:40] <StevenK> It's more casper and upstart fallout
[14:40] <ogra> but if moblin leaves you with unusable X it is hard :)
[14:40] <paulliu> ogra: He complains that moblin installation is totally broken.
[14:40] <GrueMaster> lool, my focus last week was on moblin compliance, based on Alpha 6.
[14:40] <GrueMaster> I didn't get into any testing yet.
[14:40] <lool> GrueMaster: Do we have public results?
[14:40] <StevenK> paulliu: Could you ask him to file bugs?
[14:41] <lool> GrueMaster: Are you automating this stuff?
[14:41] <GrueMaster> public results for moblin compliance testing?  not yet.
[14:41] <StevenK> paulliu: Or at least document what is broken, and how it breaks
[14:41]  * StevenK prods LP with a sharp stick
[14:41] <paulliu> StevenK: Hmm. Not good because it's a secret project I think. A hardware runs nvidia driver. Not Intel.
[14:42] <GrueMaster> The testing is automated.  Last week i was in a full week long conference, where I managed to corner some members of the linux foundation that work on the compliance test suite.
[14:42] <lool> GrueMaster: So this runs from cron on your side?
[14:42] <StevenK> GrueMaster: Were you armed or unarmed?
[14:42] <lool> GrueMaster: What I'd like to see are daily builds of the testsuite against the daily image so that we can see progress on compliance fixing
[14:43] <GrueMaster> No.  It is manually started.  I really don't have time to give a full education on how the test system works.
[14:43] <GrueMaster> Not possible.
[14:43] <lool> I don't like reading not possible
[14:43] <GrueMaster> Test suite takes 26 hours to run it's course, not including manual tests.
[14:43] <GrueMaster> You want it done faster, buy me more hardware.
[14:43] <lool> I don't want to have to rely on you to push the button
[14:44] <lool> GrueMaster: Well actually I did wonder a couple of times why it's running in your basement instead of in our shiny DCs
[14:44] <GrueMaster> It's my job, it's what I do.
[14:44] <GrueMaster> DC's?
[14:44] <lool> data ceners
[14:44] <StevenK> Datacentre
[14:44] <lool> *centers
[14:45] <GrueMaster> Some of the tests require hardware that you don't see when running in a VM.
[14:45] <GrueMaster> Like the GL tests.
[14:45] <lool> We don't need to run them in a vm in the DC
[14:45] <lool> We have our hw cert labs and our regular DCs which could host a new machine
[14:45] <lool> But ideally this would run on hw cert machines
[14:46] <GrueMaster> And who would run the manual tests?
[14:46] <lool> GrueMaster: Could you look at documenting what you run and how you setup a machine to rnu the testsuite?
[14:46] <StevenK> And what access it needs to the machine
[14:46] <lool> GrueMaster: I don't know what the manual tests are
[14:46] <GrueMaster> It is already documented on the moblin.org site, along with some new hints for missing packages I just got last week.
[14:47] <GrueMaster> let's take this offline.
[14:47] <StevenK> Does it need root, will it spew 80G of garbage to a disk ...
[14:47] <lool> Ok; I agree it takes too long to discuss here
[14:47] <lool> GrueMaster: But I would like to see more transparency on the setup and less dependencies on you pressing abutton
[14:47] <GrueMaster> Do we really want to spend the next 15 minutes with a tutorial on how to run the test suite?
[14:48] <StevenK> ... not here
[14:48]  * StevenK has a bed to visit
[14:48] <lool> Anything else moblin related?
[14:48] <plars> GrueMaster: we should talk about seeing if we can make it run in checkbox
[14:48] <StevenK> plars, GrueMaster: That sounds like a good UDS topic
[14:48] <GrueMaster> lool: you seem to have some sort of misconception about how the test suite works.  Please either read the documentation or try the test out yourself for once.
[14:48] <lool> +1
[14:48] <GrueMaster> -1.
[14:49] <GrueMaster> Good luck.
[14:49] <GrueMaster> The test suite is updated too often.
[14:49] <lool> GrueMaster: I have the impression that thousands of tests must be automated in some way and that having a person kick them manually is not the best way to use our time
[14:49] <plars> GrueMaster: I'm not saying it's simple, just worth taking a look at
[14:49] <GrueMaster> It is automated. To a point.
[14:49] <plars> GrueMaster: we already have testsuites in checkbox that are updated several times a day!
[14:49] <GrueMaster> IT TAKES LITTLE TIME TO RUN!!!!!
[14:50]  * ogra shades his ears
[14:50] <lool> But you might be at a conference or hit by a bus
[14:50]  * GrueMaster wants desparately to drop this subject.
[14:50] <plars> ok, in any case, we have 10 minutes left, we can talk about it offline
[14:50] <GrueMaster> Then someone else will need to spend 15 minutes learning how to run them.
[14:50] <lool> [topic] armel
[14:50]  * plars suggests [action] gruemaster to avoid busses for a while
[14:50] <MootBot> New Topic:  armel
[14:50] <GrueMaster> And another 10 minutes posting the data.
[14:50] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel
[14:50] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel
[14:50]  * ogra would like to see someone from the team to test Bug 427289
[14:51] <GrueMaster> Plus an hour a week justifying the ten minutes spent.
[14:51] <lool> amitk would like us to test his pselect patches
[14:51] <ogra> the kernel in todays image should support the charging
[14:51] <ogra> but my battery seems to be bad
[14:51] <lool> ogra: Ok
[14:51] <lool> will dist upgrade and test
[14:51] <ogra> you need to change for 8-12h, according to amit the clock should keep the time then
[14:51] <lool> [action] test fix for RTC battery charging (lool)
[14:51] <MootBot> ACTION received:  test fix for RTC battery charging (lool)
[14:51] <ogra> a voltmeter would also be nice :)
[14:52] <ogra> and reporting some values
[14:52] <ogra> but not mandatory
[14:52] <lool> CRAP
[14:52] <lool> https://launchpad.net/ubuntu/+source/openoffice.org/1:3.1.1-2ubuntu3/+build/1264928
[14:52] <ogra> imx51 FEC driver has issues with NM and in d-i
[14:52] <lool> doko_: ^
[14:52] <lool> ogra: Bug?
[14:53] <ogra> oo.o didnt build and we will likely ship with a broken one this round
[14:53] <lool> make[2]: *** [bfd.info] Error 1
[14:53] <lool> make[2]: Leaving directory `/build/buildd/openoffice.org-3.1.1/binutils-build/bfd/doc'
[14:53] <ogra> Bug 438687
[14:53] <lool> doko_: missing bdep?
[14:53] <ogra> lool, he knows the fixy
[14:53] <lool> ogra: Is this being pushed?
[14:53] <ogra> but we wont make it in time
[14:53] <lool> Unless we respin thursday morning
[14:53] <ogra> doko is on it afaik
[14:54] <ogra> in any case i propose to not rip out oo.o this time
[14:54] <doko_> lool: it's missing a b-d for binutils, yes. if it helps anything, I'll have packages ready in about 2h/3h on jocote, built from the same source
[14:54] <lool> ogra: 438687 > looks good
[14:54] <ogra> it took four people and several hours to get that right last time
[14:54] <ogra> if oo.o doesnt build, lets just release note it but leave it in the image
[14:54] <lool> ogra: It wasn't installable I think
[14:54] <ogra> you have to make changes in to many places
[14:54] <lool> Ok anything else on armel?
[14:55] <ogra> lool, ouch, indeed
[14:55] <ogra> and it wont be this time either
[14:55] <GrueMaster> sata still doesn't work when running gdm.
[14:55] <ogra> arch all discrepancy
[14:55] <lool> I have to review the f-k changes from NCommander  but will be post beta now
[14:55] <ogra> lool, so it seems we have to rip it out or not respin
[14:55] <ogra> current .1 image looks quite good
[14:56] <ogra> a respin will screw up the livefs build
[14:56] <GrueMaster> Also, the two failing nics of mine have been given to amitk for debugging.
[14:56] <lool> [topic] specs review
[14:56] <MootBot> New Topic:  specs review
[14:56] <ogra> GrueMaster, well, the builtin NIC works now
[14:56] <GrueMaster> I have spres here.
[14:56] <lool> ogra: is cron disabled?
[14:56] <GrueMaster> ogra, I noticed.
[14:57] <ogra> lool, for images ? i think so
[14:57] <ogra> pitti could tell
[14:57] <lool> ogra: Ok they are
[14:57] <lool> ogra: then we just need to pass the word not to respin desktop on arnel
[14:57] <lool> armel
[14:57] <ogra> yeah
[14:57] <lool> GrueMaster: LSB results for A6 > didn't see them
[14:57] <GrueMaster> I think there is still some stability issues in the USB driver stack. on imx51.
[14:57] <lool> GrueMaster: So I dropped it from the spec
[14:58] <GrueMaster> sigh.
[14:58] <plars> 2 min
[14:58] <lool> I POSTPONED a bunch of items on paulliu's specs
[14:58] <GrueMaster> I just posted them.
[14:58] <lool> GrueMaster: I updated the spec again
[14:58] <StevenK> I'm still waiting to hear when Wubi is fixed ...
[14:58] <lool> GrueMaster: Just update the spec next time
[14:58] <lool> StevenK: :-(
[14:58] <GrueMaster> I had waited to go over them with the linux foundation folks so I could understand some major failures.
[14:59] <lool> StevenK: it affects desktop too, so quite bad
[14:59] <StevenK> lool: Absolutely
[14:59] <lool> GrueMaster: I dont see how that blocks posting them?!
[14:59] <GrueMaster> lool: let ME update my spec, please.
[14:59] <StevenK> lool: I think Agostino needs to be nailed down, I'll try and catch him this week
[14:59] <lool> [link] http://piware.de/workitems/mobile/karmic/report.html
[14:59] <MootBot> LINK received:  http://piware.de/workitems/mobile/karmic/report.html
[14:59] <GrueMaster> I needed to see if I was doing anything wrong.  there was a major test suite that hung.
[15:00] <GrueMaster> turned out to be a kernel bug.
[15:00] <lool> GrueMaster: Sorry but you're not the only one to be in charge of the spec
[15:00] <lool> GrueMaster: I happen to have to report on it
[15:00] <lool> with the help of ogra BTW
[15:00] <GrueMaster> can you at least ask me what's up before blindly making changes?
[15:01]  * ogra looks up 
[15:01] <lool> GrueMaster: I checked the wiki, the results were not posted, I updated the spec to match
[15:01] <lool> GrueMaster: I thought that you could still fix it if that was incorrect -- like I just did
[15:01]  * GrueMaster gives up.
[15:01] <StevenK> ogra: Back in your cage!
[15:01] <lool> GrueMaster: I'm not going to organize to block on you
[15:01]  * ogra roars 
[15:01] <ogra> :)
[15:02] <lool> plars: I marked the unr checkbox stuff as implemented since the last action was to merge the test in the main branch
[15:02] <GrueMaster> hey, it's 3 minutes past.  meeting over, right?
[15:03] <lool> Ok ; I don't have any other questions on specs; does anybody want to raise anything?
[15:03] <lool> GrueMaster: We can run a bit over this week; especially since it's beta
[15:03] <lool> and there's no TB meeting after us
[15:03] <lool> ian_brasil: Around?
[15:03] <lool> [topic] AOB
[15:03] <MootBot> New Topic:  AOB
[15:03] <ian_brasil> yep
[15:04] <lool> ian_brasil: Did you want to raise MID stuff?
[15:04] <ian_brasil> just an update
[15:04] <ian_brasil> we created the community project..worked on seeds and i have packages upstream libhildon and hildon-desktop..both fail to build ha ha but i will sort that later
[15:04] <lool> ian_brasil: Did you settle on a set of goals and a codename?
[15:05] <ian_brasil> not the goals yet but we have a codename
[15:05] <lool> Eh ok
[15:05] <ian_brasil> Liquid remix
[15:05] <plars> lool: I saw, thanks.  They are both marked implemented now
[15:05] <lool> ian_brasil: I think at this point it's not reasonnable to do anything in karmic, but you guys could prepare stuff in a PPA for lucid
[15:06] <ian_brasil> that is what we thought
[15:06] <lool> Ok; any other business?
[15:06] <lool> NCommander: Still with us?  :-)
[15:07] <lool> #endmeeting
[15:07] <MootBot> Meeting finished at 09:07.
[15:07] <lool> Thanks all
[15:07] <ogra> thanks
[15:56] <zul> morning
[15:56] <sommer> yo :)
[16:01] <ttx> o/
[16:01] <alexm> o/
[16:02] <nijaba> \o
[16:02] <zul> gday
[16:02] <Daviey> o/
[16:02] <nurmi> o/
[16:02] <ttx> Welcome to the server team meeting...
[16:03] <kirkland> o/ ttx
[16:03] <jmdault> o/
[16:03] <nurmi> hi all, I need a few minutes before I can join, apologies; i'll o/ when i am back
[16:03] <smoser> o/
[16:03] <ttx> #startmeeting
[16:03] <MootBot> Meeting started at 10:03. The chair is ttx.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <zul> its like people are doing aerobics
[16:04] <ttx> Agenda is at https://wiki.ubuntu.com/ServerTeam/Meeting
[16:04] <ttx> [TOPIC] Review ACTION points from previous meeting
[16:04] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:04] <ttx> ACTION: Daviey to get his Asterisk 1.6RC2 update sponsored
[16:05] <ttx> no Daviey
[16:05] <Daviey> ttx: that was same day as the meeting :)
[16:05] <ttx> ok cool
[16:05] <ttx> ACTION: soren to clear out status for ec2-version-query publication
[16:05] <ttx> ACTION: soren to automate updating of ec2-version-query" (once publication is resolved)
[16:06] <ttx> soren is away, anyone knows the status of this ?
[16:06] <ttx> slangasek, maybe ^
[16:06] <ttx> ACTION: kirkland to open discussion on how to best solve the remaining configuration options on Moodle appliance
[16:06] <kirkland> ttx: is that from last week?
[16:06] <ttx> heh, yes
[16:06] <ttx> well, carried on from the week before
[16:07] <kirkland> ttx: for the prototype, i moved away from a moodle appliance for now, to a gobby server
[16:07] <ttx> ok.
[16:07] <kirkland> ttx: generically, we need to figure out how to make appliances out of packages that have critical debconf questions
[16:07] <ttx> I might have some time tomorrow to do appliance testing, if the eucalyptus front calms down
[16:07] <kirkland> ttx: that's a generic problem, which requires admin input on package installation
[16:07] <ttx> ACTION: kirkland to get help from soren and smoser on proper UEC-compatible image generation
[16:08] <ttx> ACTION: kirkland to discuss with niemeyer and nurmi about image store integration testing
[16:08] <kirkland> ttx: for the appliance to be useful, all configuration should be web driven, after instantiation, according to mdz
[16:08] <Daviey> kirkland: I'm happy to help aswell if that is wanted.
[16:08] <kirkland> Daviey: thanks
[16:08] <kirkland> cjwatson: is there a web frontend for debconf?
[16:08] <kirkland> cjwatson: i seem to recall you saying at some point that various frontends can be bolted onto debconf....
[16:08] <zul> yes there is i think we discussed it at the sprint in aalborg
[16:08] <ttx> kirkland: soren mentionned a web frontend, yes
[16:09] <cjwatson> there is, though it's not very good
[16:09] <kirkland> ttx: all of those actions have been pre-empted by getting UEC to work in Karmic Beta
[16:09] <cjwatson> I think it is minimally functional
[16:09] <kirkland> cjwatson: could you just send me a pointer to it, when you get a chance?
[16:09] <ttx> kirkland: ok.
[16:09] <cjwatson> kirkland: it's in the debconf package itself
[16:09] <ttx> ACTION: soren to update to latest euca2ools
[16:09] <mathiaz> kirkland: we should work on the appliance stuff next week
[16:09] <kirkland> cjwatson: ah, okay, thanks.
[16:09] <kirkland> mathiaz: agreed
[16:09] <ttx> I replaced soren on that one.
[16:10] <kirkland> ttx: we need a running cloud before we can test images ;-)
[16:10] <ttx> ACTION: soren to add image-generation-toolchain version numbers to manifests
[16:10] <ttx> kirkland: working on it :)
[16:10] <ttx> I don't think this was done...
[16:10] <kirkland> ttx: yup, me too :-)
[16:10] <ttx> Two actions on missing MIRs:
[16:10] <ttx> ACTION: zul to follow up on the UEC/EC2 packages MIR status
[16:10] <ttx> ACTION: smoser to file one bug for the fact that the images include unsupported packages
[16:10] <zul> done
[16:11] <zul> ec2-init is in main
[16:11] <smoser> that was done. bug 434744.
[16:11] <ttx> ok
[16:11] <ttx> ACTION: ttx to file bug about providing ec2-* command names which call euca2ools
[16:11] <ttx> bug 435140
[16:11] <ttx> ACTION: mdz to sync with kirkland on Virtual appliance status
[16:11] <ttx> That was done, he communicated basic requirements, methink
[16:12] <kirkland> ttx: i think we're in sync
[16:12] <ttx> ACTION: ttx to poke QA team about omitting untargeted wishlist bugs from the buglist and add something to those pages which tell you who to contact about them
[16:12] <kirkland> ttx: you can action mathiaz and I to work on appliance creation/generation next week in Austin
[16:12] <ttx> I did poke Brian Murray by email, without much result at that point.
[16:12] <ttx> kirkland: we'll do that when we'll see appliance status in roadmap
[16:12] <kirkland> k
[16:12] <ttx> ACTION: mathiaz to involve sbeattie in the Weekly SRU review process
[16:13] <mathiaz> ttx: talked to him last week in Portland
[16:13] <Daviey> ttx: hmm, i thought the previous meeting it was decided that ec2-* shouldn't be symlinked or similar to euca2ools as it wasn't quite compatiable at this stage?
[16:13] <mathiaz> ttx: he is interested in being part of the process
[16:13] <ttx> Daviey: the bug is the place to discuss that.
[16:13] <mathiaz> ttx: I'll talk about that more during the SRU weekly review
[16:13] <Daviey> oh, ok :)
[16:13] <ttx> [TOPIC] Beta release: Remaining beta-targeted bugs
[16:13] <MootBot> New Topic:  Beta release: Remaining beta-targeted bugs
[16:14] <ttx> is nurmi back ?
[16:14] <ttx> I prefer to have him around for that one. Lets do the next one first
[16:14] <ttx> [TOPIC] Beta release: Release process remaining actions
[16:14] <MootBot> New Topic:  Beta release: Release process remaining actions
[16:14] <ttx> * vmbuilder: using seeds, publishing toolchain version in manifests
[16:15] <ttx> I think nobody had time to work on that...
[16:15] <nijaba> ttx: did not see any cmmit to do this in vmbuillder
[16:15] <ttx> we might push that back to RC.
[16:15] <zul> ttx: what is involved?
[16:16] <ttx> zul: making vmbuilder use seeds (or germinate results) to build its package list... and generate manifests that include the vmbuidler version used, among other things
[16:17] <ttx> I think its a little late for beta anyway.
[16:17] <ttx> MIR all non-main packages used in images (smoser)
[16:17] <zul> ttx: i might take a a crack at it
[16:17] <ttx> zul: I know the seeds were pushed.
[16:17] <ttx> * MIR all non-main packages used in images (smoser)
[16:17] <ttx> that was done...
[16:17] <smoser> vmbuilder does use seed uec-images
[16:18] <smoser> err.. whatever that seed was called.
[16:18] <ttx> ah.
[16:18] <smoser> mdz had asked that vmbuilder's version be included in the manifest
[16:18] <ttx> smoser: that's not done yet, right
[16:18] <smoser> that is less straighttforward, as we're currently building with vmbuilder trunk.
[16:19] <ttx> ok, that might slip to RC.
[16:19] <ttx> * Publish ec2-version-query in a appropriate place (soren)
[16:19] <smoser> that has yet to happen
[16:19] <smoser> afaik
[16:21] <ttx> * Automate image publishing and ec2-version-query refresh (smoser)
[16:22] <smoser> not done.
[16:22] <nurmi> o/
[16:23] <ttx> smoser: is image publishing automated in /some/ways ?
[16:24] <smoser> https://wiki.ubuntu.com/UEC/Images/Publishing
[16:24] <smoser> "some"
[16:24] <ttx> ok, we'll need to review that.
[16:24] <smoser> i spent yesterday working on some publish scripts. http://smoser.brickies.net/git/?p=misc-starter-tools.git
[16:25] <smoser> with the goal of moving towards being ready to work right away as soon as we get some access to amazon from data center
[16:25] <ttx> ok.
[16:25] <ttx> Anything that needs to be done on the release management side for beta release ?
[16:26] <ttx> [TOPIC] Beta release: Remaining beta-targeted bugs
[16:26] <MootBot> New Topic:  Beta release: Remaining beta-targeted bugs
[16:27] <ttx> https://bugs.launchpad.net/bugs/432154
[16:27] <ttx> kirkland: I think this one should be untargeted now
[16:27] <kirkland> ttx: i agree
[16:27] <ttx> please retarget to next
[16:27] <kirkland> ttx: done
[16:27] <ttx> https://bugs.launchpad.net/bugs/429106 (smoser)
[16:28] <ttx> smoser: it's disputed if it's really a good idea right now, right ?
[16:28] <smoser> that is fix-commited, and images are available, although not ideally named for client pulling (or documentation)
[16:29] <smoser> i dont think its disputed. slangesek just impllied that we need to make sure we can fulfill gpl source requirements on the stuff
[16:29] <ttx> smoser: is there a bug open to track that ?
[16:29] <smoser> is marked committed and not released because its not in vmbuilder that is in karmic
[16:29] <smoser> i guess i should open 2 bugs.
[16:29] <ttx> (the gpl reqs)
[16:29] <smoser> 1 for gpl reqs
[16:29] <smoser> 1 for renaming output or re-ordering
[16:30] <ttx> [ACTION] smoser to open bugs to cover kernel/ramdisk GPL reqs and renaming
[16:30] <MootBot> ACTION received:  smoser to open bugs to cover kernel/ramdisk GPL reqs and renaming
[16:30] <ttx> https://bugs.launchpad.net/bugs/438747
[16:30] <ttx> That one is the latest eyucalyptus issue uncovered in my testing
[16:30] <ttx> its quite easy to fix and is needed for beta
[16:31] <ttx> though I might need someone to push the fix, upload get the exception and the respin
[16:31] <ttx> since I intend to have some evening left
[16:31] <ttx> https://bugs.launchpad.net/bugs/438602
[16:31] <ttx> This one is more tricky
[16:31] <ttx> We want autoregistration to work for beta
[16:32] <ttx> but... whatever we do it seems that eucalyptus randomly fails to accept it
[16:32] <mathiaz> ttx: yeah - I ran into the same issue
[16:32] <mathiaz> ttx: none of my test installs actually worked correclty
[16:32] <ttx> nurmi: any clue ?
[16:32] <ttx> We run registration after getting some response from port 8443
[16:32] <mathiaz> ttx: I suspect an issue with the upstart job
[16:33] <nurmi> ttx: the last UEC iso I tried last night was kind of hard to figure out
[16:33] <ttx> nurmi: yes, try the 20090929.2
[16:33] <mathiaz> ttx: ex: the walrus-registration would start and failed but the cc-registration job would not even start
[16:33] <nurmi> ttx: okay, i'll try that
[16:34] <ttx> nurmi: if I run "sudo eucalyptus stop / sudo eucalyptus start" 10 times in a row, it would succeed to autoregister the 8th time
[16:34] <kirkland> mathiaz: ttx: fwiw, i just installed fresh; walrus successfully auto registered; cluster did not
[16:34] <ttx> kirkland: yes, that's what I got with 20090929.2
[16:35] <ttx> cluster and sc fail
[16:35] <nurmi> ttx: i think i need the latest iso, my 'start eucalyptus-cloud' commands were hanging forever yesterday
[16:35] <kirkland> ttx: confirmed
[16:35] <ttx> kirkland: could you debug that with nurmi and push the fix if you find any ?
[16:35] <mathiaz> kirkland: is there a log file in /var/log/eucalyptus/cc-registration?
[16:35] <ttx> at that point I'd say if we don't manage to fix it today, it should be a beta known issue
[16:35] <nurmi> interesting, the only difference between walrus and cc/sc is that the cc/sc registration commands require a 'cluster name'
[16:36] <mathiaz> kirkland: I would first make sure that the upstart job is started correclty
[16:36] <nurmi> i.e. euca_conf --register-cluster <cluster-name> <ip>
[16:36] <kirkland> mathiaz: that log does not exist
[16:36] <ttx> nurmi: it also uses localhost instead of the IP
[16:36] <mathiaz> kirkland: right - I suspect that the upstart job is not even started
[16:36] <mathiaz> kirkland: I'd add a pre-script to check whether the job is actually started
[16:36] <ttx> which might be the reason, actually.
[16:37] <mathiaz> kirkland: and bug Keybuck about debugging upstart
[16:37] <ttx> let's not debug that during the meeting
[16:37]  * mathiaz agrees
[16:37] <nurmi> ttx: ah, well, that is most likely the issue; in upstream, you cannot register 'localhost', as we discussed a few days ago; mdz said that ubuntu had patched the system to allow localhost registration
[16:37] <kirkland> ttx: okay, so i'll debug the cc auto registration
[16:37] <mathiaz> kirkland: we can debug this later
[16:37] <kirkland> ttx: and sync with mathiaz and nurmi
[16:37] <ttx> kirkland: might make sense to try to use the walrus IP inside cc and sc-registration.conf
[16:37]  * nurmi agrees
[16:37] <ttx> lets talk about that later
[16:38] <ttx> Anything else that should be targeted for beta ?
[16:38] <ttx> Hopefully, nothing...
[16:38] <ttx> [TOPIC] Roadmap review / Eucalyptus
[16:38] <MootBot> New Topic:  Roadmap review / Eucalyptus
[16:38] <ttx> https://bugs.launchpad.net/ubuntu/+source/eucalyptus
[16:39] <ttx> thanks to a huge triage effort by kirkland, the buglist is actually usable now.
[16:39] <ttx> we dalready discussed what could be brought after beta for the release
[16:40] <ttx> I'm more scared by the bugs we don't know (the ones we find in testing)
[16:40] <ttx> [TOPIC] Roadmap review / UEC - EC2 bugs
[16:40] <MootBot> New Topic:  Roadmap review / UEC - EC2 bugs
[16:40] <ttx> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=uec-images
[16:40] <ttx> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=ec2-images
[16:40] <ttx> smoser: comments ?
[16:41] <smoser> http://tinyurl.com/yazgzzf link is "all bugs targetted to beta with ec2-images or uec-images in a tag"
[16:41] <MootBot> LINK received:  http://tinyurl.com/yazgzzf link is "all bugs targetted to beta with ec2-images or uec-images in a tag"
[16:42] <smoser> all of those are fixed as far as i know
[16:43] <zul> i just like to bring up that amazon has released a new version of ec2-api-tools which add better ebs and also adds vpn support I was going to ask for a FFE but I dont know how well it works with eucalyptus
[16:43] <ttx> smoser: sounds good. I did not have time to carefully review them
[16:43] <smoser> the most difficult bug of anything still open is bug 428692
[16:44] <ttx> zul: I think that's not for beta anyway... and maybe not for release
[16:44] <zul> ttx: I can just throw it in a ppa and upload it for lucid
[16:44] <smoser> the only karmic related bug there with medium or > priority that isn't on track for being fixed in karmic is bug 407949
[16:44] <ttx> zul: that won't hurt.
[16:45] <zul> ttx: okie dokie
[16:45] <ttx> smoser: I tested images on my karmic UEC today, worked. I still have to test the kernel/ramdisk you produce though
[16:46] <ttx> smoser: thanks for the update.
[16:46] <ttx> [TOPIC] Roadmap review: Virtual appliance
[16:46] <MootBot> New Topic:  Roadmap review: Virtual appliance
[16:46] <ttx> kirkland, niemeyer: what's the plan ?
[16:46] <smoser> i think we're actually looking pretty good now (although i fear i've said that bfore)
[16:47] <kirkland> ttx: i'm confident gobby will work well
[16:47] <kirkland> ttx: as it has a very hands off, unattended installation
[16:47] <niemeyer> ttx: The proxy should be in pretty good state now..
[16:47] <kirkland> ttx: mdz raised a question about persistent storage configuration, which i have not yet solved
[16:47] <kirkland> ttx: but that's the case for most any appliance
[16:47] <ttx> kirkland/niemeyer: at one point you need to sync on how to intgerate one with the other
[16:47] <mathiaz> niemeyer: did you get a chance to look at bug 436896?
[16:47] <ttx> integrate, even
[16:47] <niemeyer> ttx: I just have to work a bit on the server side.. waiting for the server infrastructure for this
[16:48] <kirkland> ttx: as for moodle, wordpress, others, we need to establish the process by which we handle debconf
[16:48] <ttx> niemeyer: any ETA on infra ?
[16:48] <niemeyer> mathiaz: Oh yeah, thanks for reporting this.. I'll provide you with a fix in the next couple of days
[16:48] <kirkland> ttx: i'm going to have a look at the web frontend for debconf that colin mentioned
[16:48] <niemeyer> ttx: Not really.. should already have been made available by now, so at any time
[16:48] <ttx> kirkland: ok. You mentioned a sprint ?
[16:48] <mathiaz> niemeyer: the key is to test without a ~/.gnupg/ directory
[16:48] <niemeyer> mathiaz: Cool, I'll make sure to check this out
[16:48] <mathiaz> niemeyer: and making sure that it's not created afterwards
[16:49] <niemeyer> mathiaz: Any other issues about 1.0, or is it all good?
[16:50] <mathiaz> niemeyer: well - I haven't been able to complete a full test
[16:50] <mathiaz> niemeyer: as there isn't a server side yet
[16:50] <mathiaz> niemeyer: is the fakeproxy actually able to push images?
[16:50] <niemeyer> mathiaz: Cool, please note that you can fake the server side
[16:50] <niemeyer> mathiaz: The fakestoreapi.py can fake the server side entirely
[16:51] <kirkland> ttx: potentially a mini sprint
[16:51] <niemeyer> mathiaz: I'll send you and nurmi a mail later with details on how to test this
[16:51]  * ttx adds a few missing actions...
[16:51] <kirkland> ttx: mathiaz will be in Austin anyway
[16:51] <mathiaz> niemeyer: ok - thanks.
[16:51] <kirkland> ttx: i'm trying to convince nurmi to come down too :-)
[16:51] <nurmi> niemeyer: nod, thanks
[16:51] <kirkland> ttx: i reckon the 3 of us could kick some post-beta butt
[16:51] <niemeyer> nurmi: I've seen your mail, btw, was just catching up after holidays to send you these details
[16:51] <ttx> [ACTION] kirkland to fix bug 438747, maybe bug 438602, package and push a respin with that package in
[16:51] <MootBot> ACTION received:  kirkland to fix bug 438747, maybe bug 438602, package and push a respin with that package in
[16:51] <nurmi> kirkland: actively working on it :)
[16:52] <kirkland> nurmi: ack ;-)
[16:52] <niemeyer> nurmi: I have a new assignment to do a few tweaks in the UI.. we should catch up about this at some point
[16:52] <ttx> [ACTION] ttx to test UEC images + UEC kernel/ramdisk on karmic UEC
[16:52] <MootBot> ACTION received:  ttx to test UEC images + UEC kernel/ramdisk on karmic UEC
[16:52] <nurmi> niemeyer: thank you, I can't wait to check it out
[16:52] <ttx> [TOPIC] Other specs from the Roadmap
[16:52] <MootBot> New Topic:  Other specs from the Roadmap
[16:52] <niemeyer> nurmi: I hope to have a patch by the end of the week for appreciation
[16:53] <ttx> I think at that point only the late specs (that we covered) are to be considered
[16:53] <ttx> especially with asterisk done, iiuc
[16:53] <nurmi> niemeyer: sounds good, please send me email if you're blocking or could use testing/integration
[16:54] <ttx> [TOPIC] Assigned and to-be-assigned bugs
[16:54] <MootBot> New Topic:  Assigned and to-be-assigned bugs
[16:54] <ttx> http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html
[16:54] <MootBot> LINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html
[16:54] <niemeyer> nurmi: Awesome, thanks a lot
[16:55] <ttx> I'll have a look at the bugs assigned to soren to see if something needs to be reassigned before he comes back
[16:55] <ttx> [ACTION] ttx to see if some bugs assigned to soren need urgent reassignment
[16:55] <MootBot> ACTION received:  ttx to see if some bugs assigned to soren need urgent reassignment
[16:56] <ttx> any other comments on that list ?
[16:56] <ttx> [TOPIC] Weekly SRU review (mathiaz)
[16:56] <MootBot> New Topic:  Weekly SRU review (mathiaz)
[16:57]  * ttx lies back and enjoys mathiaz taking over
[16:57] <ttx> (please :)
[16:57] <mathiaz> right - so let's go through the list of bugs
[16:57] <mathiaz> http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[16:57] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[16:57] <zul> the nut init script bug is probably a good candidate for jaunty i have to check though
[16:58] <mathiaz> any bugs worth SRU in the list?
[16:58] <mathiaz> zul: bug number?
[16:58] <mathiaz> bug 416182
[16:58] <zul> #416182	
[16:58] <Daviey> Wow eucalyptus is a large part.
[16:58] <mathiaz> Daviey: yeah - that's kirkland's work
[16:58] <mathiaz> Daviey: we can probaly ignore most of them
[16:58] <ttx> yes we can
[16:59] <zul> mathiaz: none of the php5 ones
[16:59] <mathiaz> there is bug 404394
[16:59] <mathiaz> kirkland: ^^ which I've hit on my server
[16:59] <mathiaz> kirkland: (hardy - with the kvm 84 backport)
[16:59] <mathiaz> kirkland: I can't use karmic guest + qcow2 + virtio
[17:00] <mathiaz> zul: bug 424719?
[17:00] <kirkland> arg
[17:00] <kirkland> mathiaz: i haven't had much time to look at that
[17:01] <kirkland> s/much/any/
[17:01] <mathiaz> kirkland: understood
[17:01] <zul> mathiaz: yeah its a bit hard to reproduce though for SRU testing
[17:01] <mathiaz> allright - any bugs apart the nut init script SRU worthy from the list above?
[17:01] <Daviey> Does that one need to be private?
[17:01] <zul> just a sec
[17:02] <zul> Daviey: it isnt now
[17:02] <mathiaz> zul: bug 416182 would be worth accepting for which release?
[17:02] <mathiaz> zul: hardy?
[17:02] <zul> jaunty i think
[17:02] <mathiaz> zul: and what's the importance?
[17:02] <zul> low
[17:02] <Daviey> thanks zul
[17:03] <mathiaz> zul: ok - jaunty+low -> we can live with it
[17:03] <mathiaz> anything else?
[17:03] <zul> nope
[17:03] <zul> not from me
[17:03] <mathiaz> ok - let's move on to the next list
[17:04] <mathiaz> http://us-hardynominated.notlong.com/
[17:04] <MootBot> LINK received:  http://us-hardynominated.notlong.com/
[17:04] <mathiaz> nothing
[17:04] <mathiaz> http://us-dappernominated.notlong.com/
[17:04] <MootBot> LINK received:  http://us-dappernominated.notlong.com/
[17:04] <mathiaz> nothing
[17:04] <mathiaz> http://us-intrepidnominated.notlong.com/
[17:04] <MootBot> LINK received:  http://us-intrepidnominated.notlong.com/
[17:04] <mathiaz> nothing
[17:04] <mathiaz> http://us-jauntynominated.notlong.com/
[17:04] <MootBot> LINK received:  http://us-jauntynominated.notlong.com/
[17:05] <Daviey> wouldn't seem SRU worthy to me?
[17:05] <mathiaz> bug 356905
[17:06] <zul> uh...its fixed in jaunty
[17:07] <mathiaz> zul: right - declining
[17:07] <mathiaz> that's all for the nominated bugs
[17:07] <mathiaz> let's move on to the next list
[17:07] <mathiaz> http://qa.ubuntu.com/reports/ubuntu-server-team/acceptedbugs.ubuntu-server.latest.html
[17:07] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/acceptedbugs.ubuntu-server.latest.html
[17:07] <mathiaz> this is the list of accepted bugs that have an assignee
[17:08] <mathiaz> ie someone working *actively* on preparing an sRU
[17:08] <mathiaz> zul: what's the state of all your bugs?
[17:08] <zul> most of those are in -proposed and need testers
[17:08] <mathiaz> kirkland: bug 332156
[17:08] <mathiaz> kirkland: still working on an SRU for it?
[17:08] <kirkland> mathiaz: no, not really
[17:09] <kirkland> mathiaz: should be fixed in the backport
[17:09] <kirkland> mathiaz: i'll note it
[17:09] <mathiaz> kirkland: ok - and unassign yourself from the bug if necessary
[17:09] <Daviey> hmm, are we allowed to fix release via backport?
[17:10] <kirkland> Daviey: not usually
[17:10] <kirkland> Daviey: but for kvm, i've been doing so, as these bugs are not fixable otherwise
[17:10] <mathiaz> zul: bug 382136?
[17:10] <zul> i need to look at that again
[17:12] <mathiaz> ok - that's all for this list
[17:12] <mathiaz> on to the next
[17:12] <mathiaz> https://code.launchpad.net/~ubuntu-server/+requestedreviews
[17:12] <ttx> ew
[17:12] <Daviey> 404?
[17:12] <mathiaz> https://code.launchpad.net/~ubuntu-server/+activereviews
[17:13] <mathiaz> so no one is using pkg branches for reviews
[17:13] <ttx> mathiaz: no more lists ?
[17:13] <mathiaz> ttx: nope - I ran out
[17:13] <mathiaz> https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20resources
[17:13] <ttx> [TOPIC] 2009 Server survey status and call for action. (nijaba)
[17:13] <MootBot> New Topic:  2009 Server survey status and call for action. (nijaba)
[17:13] <mathiaz> ttx: ah - no
[17:13] <mathiaz> ttx: I just wanted to reiterate
[17:14] <nijaba> ttx: so I have prepared a new version of the survey
[17:14] <mathiaz> ttx: that we're trying to use package branches for SRU
[17:14] <nijaba> ttx: and it is now time for review
[17:14] <nijaba> background: https://wiki.ubuntu.com/ServerTeam/Survey
[17:14] <ttx> nijaba: who should review ?
[17:15] <nijaba> aynone interested in the community
[17:15] <nijaba> I have put a test server in place: http://admin.barcet.com:8084/limesurvey
[17:15] <ttx> yay, let's slashdot that
[17:15] <nijaba> bugs should be reported on https://bugs.launchpad.net/server-survey/+filebug
[17:15] <Daviey> nijaba: suggestions to https://bugs.launchpad.net/server-survey/+filebug ?
[17:16] <ttx> Daviey: you read minds
[17:16] <nijaba> Daviey: yes please
[17:16] <ttx> nijaba: anything else ?
[17:16] <nijaba> nope
[17:16] <ttx> [TOPIC] Open Discussion
[17:16] <MootBot> New Topic:  Open Discussion
[17:16] <ttx> I've one thing I forgot to mention in the agenda
[17:17] <ttx> About https://help.ubuntu.com/community/Eucalyptus
[17:17] <ttx> its quite outdated especially now that we push usage of the UEC installer from the CD
[17:17] <ttx> if someone has some time to refresh it...
[17:17] <ttx> see http://testcases.qa.ubuntu.com/Install/ServerECluster
[17:18] <ttx> http://testcases.qa.ubuntu.com/Install/ServerENode
[17:18] <MootBot> LINK received:  http://testcases.qa.ubuntu.com/Install/ServerENode
[17:18] <ttx> and http://testcases.qa.ubuntu.com/Install/ServerEConfig
[17:18] <Daviey> ttx: https://help.ubuntu.com/community/Eucalyptus is still valid for Jaunty, so perhaps the pages need to be forked.. for a karmic and jaunty one?
[17:18] <ttx> the last part shoudl probably be rewritten from the perspective of running imaghes from a client rather than from the cluster itself
[17:18] <ttx> Daviey: "Note: Please see Eucalyptus-Jaunty for documentation covering Eucalyptus on Ubuntu 9.04. "
[17:19] <ttx> at the top of the page
[17:19] <Daviey> "whoops"
[17:19] <ttx> those testcases should help in getting started
[17:19] <ttx> we refresh those instructions to correspond to the moving status in eucalyptus
[17:20] <ttx> anyone up to the challenge ?
[17:20]  * ttx ponders writing a blog post after beta
[17:20] <ttx> Any other subject for Open Discussion ?
[17:20] <Daviey> Yes!
[17:20]  * alexm offers himself as doc tester
[17:21] <alexm> i'm interested in eucalyptus but i don't know where to start :(
[17:21] <ttx> alexm: the test cases should get you there. Minus the critical bugs we still have to fix :)
[17:21] <Daviey> I'll try and contribute to the wiki page, but i can't commit to doing the whole thing.
[17:22] <alexm> s/doc tester/doc reviewer/
[17:22] <ttx> Daviey: ok, we'll do it wikistyle
[17:22] <ttx> [TOPIC] Agree on next meeting date and time
[17:22] <MootBot> New Topic:  Agree on next meeting date and time
[17:22] <Daviey> Currently we are installing -pae on 32bit and -server on amd64.. However, we don't install the linux-headers for the kernel installed/
[17:22] <Daviey> ttx: wait 1
[17:22] <ttx> done
[17:22] <alexm> ttx: we're talking about test cases running on karmic, i guess
[17:22] <Daviey> dkms isn't installed by default.. and when dkms IS installed on a server it installs the -generic kernel
[17:22] <Daviey> this is bad.
[17:23] <ttx> alexm: karmic on karmic on karmic, yes
[17:23] <alexm> ok, thanks :)
[17:23] <Daviey> bug 433712 is related
[17:23] <Daviey> damn you kirkland
[17:24] <ttx> Daviey: is there a bug filed on that specific issue ?
[17:24] <Daviey> ttx: no, only came to light this morning and wasn't sure how to proceed.
[17:24] <kirkland> Daviey: huh?
[17:24] <Daviey> kirkland: sorry, i thought you fixed the issue just now.. as the status has changed to Fixed Released
[17:25] <kirkland> Daviey: no i just marked it fix released, since dkms is already on the server cd
[17:25] <kirkland> Daviey: which is what superm1 was askign for
[17:25] <Daviey> kirkland: sure.
[17:26] <Daviey> but installing dkms doesn't pull in the correct kernel for what the server iso installs.
[17:26] <ttx> Daviey: if there is a persisting bug, just file one, please
[17:26] <mathiaz> Daviey: right - kirkland run into the same issue with the kvm backport in hardy
[17:26] <Daviey> ttx: will do.
[17:26] <ttx> [TOPIC] Agree on next meeting date and time
[17:26] <MootBot> New Topic:  Agree on next meeting date and time
[17:26] <kirkland> yeah
[17:26] <mathiaz> Daviey: AFICT there isn't a way to fix it in apt
[17:26] <ttx> soren started a discussion about moving the time of the meeting.
[17:27] <ttx> I'd like all the usual suspects to submit their preferences, otherwise we might pick up a time that will not please you
[17:27] <Daviey> could http://www.doodle.com/ help with this?
[17:27] <ttx> Daviey: certainly.
[17:28]  * ttx frowns at entering his email in one more place
[17:28]  * alexm hasn't replied because thinks that key team members should speak first
[17:29] <ttx> now that the discussion started on the list, its probably good to continue on the list
[17:29] <alexm> ttx: there's no need to register for using doodle
[17:30]  * mathiaz agrees
[17:30] <ttx> If Doodle is ok with everyone... Daviey could you reply to the thread and set it up ?
[17:30] <Daviey> wilco
[17:30] <ttx> mathiaz: with what ?
[17:30] <mathiaz> Daviey: I'm not sure how doodle will help
[17:30] <mathiaz> Daviey: you'd have to enter 24 different options
[17:30] <mathiaz> Daviey: and we'd have to vote for each of them
[17:30] <ttx> that's 2 * -1 against Doodle, lets do it UTC + ML style
[17:30] <Daviey> mathiaz: you put in the time that is suitable(s)
[17:31] <mathiaz> Daviey: http://www.doodle.com/BSP6n4bmdzyg5c3g
[17:31] <mathiaz> Daviey: that seems like the creator of the poll creating the different options
[17:32] <mathiaz> I'll reply to the ML thread.
[17:32] <mathiaz> and then someone can sort it out
[17:32] <Daviey> ok
[17:33] <ttx> ok then
[17:33] <ttx> #endmeeting
[17:33] <MootBot> Meeting finished at 11:33.
[17:33] <ttx> mathiaz: i was wondering if we could cycle in writig the minutes
[17:34] <mathiaz> ttx: ok
[17:34] <ttx> mathiaz: much appreciated, thx
[17:36] <Daviey> thanks
[17:58] <bjf> Roll Call
[17:58] <amitk_> \o
[17:58]  * ogasawara waves
[17:58] <lieb> hi
[17:58]  * rtg waves
[17:58]  * jjohansen waves
[17:58]  * sconklin is here
[17:59] <bjf> no apw, nor pgraner this week
[17:59]  * cking_ here
[17:59]  * csurbhi1 waves
[17:59] <smb> \o
[17:59]  * manjo waves
[17:59] <bjf> #startmeeting
[17:59] <MootBot> Meeting started at 11:59. The chair is bjf.
[17:59] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:00] <bjf> [TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targe
[18:00] <MootBot> New Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targe
[18:00] <ogasawara>  * Release Meeting Bugs (8 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:00] <ogasawara>  * RC Milestoned Bugs Beta (17 kernel bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs?field.milestone%3Alist=12715
[18:00] <ogasawara>  * Release Targeted Bugs (15 bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:01] <bjf> [TOPIC] Karmic Release Status: Milestoned Features
[18:01] <MootBot> New Topic:  Karmic Release Status: Milestoned Features
[18:01] <ogasawara> Milestoned Features - https://edge.launchpad.net/ubuntu/+milestone/ubuntu-9.10-beta
[18:01] <bjf> [TOPIC] Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:01] <MootBot> New Topic:  Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:01] <ogasawara> bjf: Nothing new to report
[18:02] <bjf> [TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:02] <MootBot> New Topic:  Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:02] <rtg> I talked to marjo about getting some testing done. I'm gonna upload it this week.
[18:02] <bjf> [TOPIC] Blueprints: kernel-karmic-kms (anyone since apw is out)
[18:02] <MootBot> New Topic:  Blueprints: kernel-karmic-kms (anyone since apw is out)
[18:02] <rtg> there are some AA components that need fixing, but will get kees or jjohansen to work on that
[18:03] <bjf> sorry, little quick there
[18:03] <rtg> all done
[18:03] <bjf> any kms status?
[18:03] <rtg> KMS is getting some love with the next upload (for Intel that is)
[18:03] <rtg> as soon as slangasek approves the kernel package
[18:03] <bjf> [TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:03] <MootBot> New Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:04] <smb> I would say that one is done. But I have to do the final edits in the spec. Hopefully tomorrow.
[18:04] <bjf> smb, you want me to remove it from the agenda?
[18:04] <smb> leave it there to remind me in case I do not get t edit the spec
[18:04] <bjf> smb, ack
[18:04] <bjf> [TOPIC] Blueprints: kernel-karmic-suspend-resume (manjo)
[18:04] <MootBot> New Topic:  Blueprints: kernel-karmic-suspend-resume (manjo)
[18:05] <manjo> nothing to update
[18:05] <bjf> [TOPIC] Other Release Tasks: AppArmor (jjohansen)
[18:05] <MootBot> New Topic:  Other Release Tasks: AppArmor (jjohansen)
[18:05] <jjohansen> well I have a couple known bugs to fix
[18:05] <jjohansen> bug 427948
[18:06] <jjohansen> I need to test and push the patch for
[18:06] <bjf> jjohansen, how is your progress on upstreaming?
[18:06] <jjohansen> I posted to LSM, and overall it has gone well, but I am waiting on more comments as people clear mail queue from plumbers
[18:07] <jjohansen> I have a couple questions I need to answer
[18:07] <jjohansen> and have pulled in some changes.
[18:07] <jjohansen> 1, fix that I need to push into karmic
[18:07] <bjf> jjohansen, is that it?
[18:07] <jjohansen> I need to look at capability setting more, and come up with a solution that allows dropping caps
[18:08] <jjohansen> apparmor got pushed into initramfs this last week
[18:08] <jjohansen> that caused some breakage, but kees did the patches
[18:09] <kees> afak, all the bugs from that are fixed
[18:09] <jjohansen> AA was pushed into initramfs so that policy could be loaded before parallel boot
[18:09] <jjohansen> yep
[18:09] <jjohansen> we will need to change the solution in the future, but that waits on full upstartification
[18:10] <jjohansen> I think that is it
[18:10] <bjf> [TOPIC] Other Release Tasks: ARM-Freescale/Marvell (amitk, bjf)
[18:10] <MootBot> New Topic:  Other Release Tasks: ARM-Freescale/Marvell (amitk, bjf)
[18:10] <amitk_> * bug 438687 - need to fix fec ethernet to set the DRIVER property of N-M to work
[18:10] <bjf> Marvell is pretty stable, some new changes, some rebasing... got a Y1 reference board
[18:10] <amitk_> * bug 418238 - (fixed) fec ethernet driver
[18:10] <amitk_> * bug 427289 - investigating RTC problems with imx51
[18:10] <amitk_> * bug 319729 - debugging pselect/ppoll with jk at the sprint, continuing study of glibc wrappers
[18:11] <amitk_> those bugs are taking up my time ATM
[18:11] <bjf> [TOPIC] Other Release Tasks: EC2 Karmic Kernel Status
[18:11] <MootBot> New Topic:  Other Release Tasks: EC2 Karmic Kernel Status
[18:12] <jjohansen> I need to finish bisecting the virtual style config problems
[18:12] <rtg> I rebased ec2 against 2.6.31-11.36 and uploaded last night
[18:12] <jjohansen> rtg: thanks, smoser was real happy to get that
[18:12] <rtg> the primary reason was for an LSB test failure
[18:13] <rtg> jjohansen, I think its still in the waiting-to-be-approved queue
[18:13] <bjf> [TOPIC] Status: Karmic (rtg, apw)
[18:13] <MootBot> New Topic:  Status: Karmic (rtg, apw)
[18:13] <rtg> I've been messing with scheduler settings.
[18:14] <rtg> the I/O CFQ was kind of broken, but an upstream cherry-pick has helped it out a lot
[18:14] <rtg> It'll make the next upload.
[18:14] <rtg> other then that, some i915 enablement and performance fixes.
[18:14] <rtg> 2.6.31.1 stable updates
[18:14] <rtg> thats about it.
[18:14] <amitk_> rtg: are you reverting back to CFQ then?
[18:15] <rtg> amitk_, I don't think so, perhaps we can swizzle it from userspace.
[18:15] <rtg> the sysv-init package has been suggested as theright place
[18:16] <bjf> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:16] <MootBot> New Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:16] <smb> * Dapper:   2.6.15-54.79 (security)
[18:16] <smb> * Hardy:    2.6.24-24.60 (updates)
[18:16] <smb>             2.6.24-24.61 (proposed)[0] (0/2 verifications)
[18:16] <smb>             (accepted 11 days ago but stuck in binary new until today)
[18:16] <smb>             LUM-2.6.24-24.41 (updates)
[18:16] <smb> * Intrepid: 2.6.27-14.41 (updates)
[18:16] <smb> * Jaunty    2.6.28-15.52 (updates)
[18:16] <smb> So beside of Hardy, proposed is surprisingly empty. Which should make the
[18:16] <smb> upcoming security work a bit simpler.
[18:16] <bjf> i've rebased the fsl-imx51 topic branch (Jaunty) and will issue a pull request soon
[18:17]  * smb takes that of his todo list.
[18:17] <bjf> [TOPIC] Incoming Bugs: Regressions (ogasawara)
[18:17] <rtg> bjf, I'm working on the Karmic pull request for mvl-dove right now
[18:17] <MootBot> New Topic:  Incoming Bugs: Regressions (ogasawara)
[18:17] <ogasawara> 1 regression-potential bug this week (just needs to add a module to the d-i sata-modules file)
[18:18] <bjf> [TOPIC] Incoming Bugs: Bug day report (ogasawara)
[18:18] <MootBot> New Topic:  Incoming Bugs: Bug day report (ogasawara)
[18:18] <rtg> ogasawara, bug number? I can fix it quickly
[18:18] <ogasawara> Today's bug day - https://wiki.ubuntu.com/KernelTeam/BugDay/20090929
[18:18] <ogasawara> Current stats can be seen at http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090929.html
[18:18] <ogasawara> rtg: yup, just a sec and I'll get it
[18:18] <smb> https://bugs.launchpad.net/ubuntu/+bug/434827?comments=all
[18:19] <ogasawara> rtg: ^^
[18:19] <bjf> [TOPIC] Ubuntu Open Week (rtg)
[18:19] <bjf> [LINK] https://wiki.ubuntu.com/UbuntuOpenWeek/Prep
[18:19] <MootBot> New Topic:  Ubuntu Open Week (rtg)
[18:19] <MootBot> LINK received:  https://wiki.ubuntu.com/UbuntuOpenWeek/Prep
[18:19] <rtg> ogasawara, you have a topic picked out?
[18:20] <ogasawara> rtg: no topic in particular just yet, but reserved my time slot
[18:20] <ogasawara> rtg: like something Kernel QA related
[18:20] <ogasawara> s/like/likely/
[18:20] <rtg> is anyone else on the kernel team interested in conducting a session?
[18:21] <rtg> well, if you are then go to that page and sign up.
[18:21] <ogasawara> rtg: you'll likely have to "volunteer" others :)
[18:21] <jjohansen> I could do an AA session
[18:21] <rtg> jjohansen, works for me. thanks.
[18:22] <bjf> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:22] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:22] <jjohansen> csurbhi: AppArmor
[18:22] <csurbhi> ok
[18:22] <csurbhi> thanks
[18:22] <jjohansen> or Alcoholics Anonymous ;)
[18:23] <bjf> going once ....
[18:23] <bjf> going twice ...
[18:23] <bjf> done!
[18:23] <smb> \o/
[18:23] <bjf> #endmeeting
[18:23] <MootBot> Meeting finished at 12:23.
[18:23] <amitk_> thanks folks
[18:23] <rtg> ciao
[18:23] <lieb> bye
[18:23] <csurbhi> ciao