[09:35] <huats> morning
[14:00] <NCommander> #startmeeting
[14:00] <MootBot> Meeting started at 08:00.  I need to rebuild it
[14:03] <NCommander> Oops
[14:04] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100810
[14:04] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100810
[14:04]  * NCommander is still not awake
[14:04] <NCommander> [topic] ogra to re-enable the lucid efl session (c/o)
[14:04] <MootBot> New Topic:  ogra to re-enable the lucid efl session (c/o)
[14:05] <ogra> done
[14:05]  * rsalveti needs caffeine
[14:05] <ogra> still needs adjustment and given the uninstallability we have atm i cant make these
[14:05] <NCommander> ogra: so c/o or?
[14:06] <ogra> no, its done
[14:06] <ogra> the package is in and is installed by default
[14:06] <ogra> just needs adjustments
[14:06] <NCommander> ah
[14:06] <NCommander> [topic] mpoirer to coordinate with sarkoman or TI internal sources to get branch with "factory" bootloader source (c/o - hold)
[14:06] <MootBot> New Topic:  mpoirer to coordinate with sarkoman or TI internal sources to get branch with "factory" bootloader source (c/o - hold)
[14:07] <mpoirier> That was abandoned
[14:07] <mpoirier> the tree was located but impossible to reproduce factory image.
[14:07] <NCommander> oh,oops
[14:07] <mpoirier> despite, the rogue patch was identify.  Kernel team is not convinced the best way to address the problem is to revert patch.  Further discussion will take place today.
[14:07] <ogra> strike it theb
[14:07] <ogra> *then
[14:07] <NCommander> k
[14:08] <NCommander> [topic] cooloney to work with robclark and sebjan to merge HDMI patches (c/o)
[14:08] <MootBot> New Topic:  cooloney to work with robclark and sebjan to merge HDMI patches (c/o)
[14:08] <ogra> mpoirier, for which bug was that originally btw ?
[14:08] <ogra> the MMC issues ?
[14:08]  * ogra forgot
[14:08] <mpoirier> /bugs.launchpad.net/bugs/591941 - yes, mmc
[14:08] <ogra> great, k, seems we have other patches that just got into linux-omap at least
[14:09] <rsalveti> mpoirier: were you able to get in contact with the  patch owner? maybe he can help you on this
[14:09] <mpoirier> Nope, didn't contact anyone yet.
[14:09] <mpoirier> we still have to see how we'll proceed.
[14:09] <ogra> NCommander, sebjan is on vacation this week and ndec is working on the tree merge, i dont think we need the tiem for cooloney anymore, robs patches will be in the next TI tree
[14:09] <ogra> s/tiem/item/
[14:09] <rsalveti> yep, I'm testing a couple of patches from rob
[14:10] <rsalveti> still not fully working with hdmi and dvi yet
[14:10] <ogra> as long as you dont break my working monitor :P
[14:10] <rsalveti> there's one patch that breaks the screen for hdmi, rob said he's going to work on this during this week
[14:11] <rsalveti> currently I'm using some patches that will be inside the latest TI release plus some more rob's patches
[14:11] <rsalveti> the question is, are we expecting to merge any other kernel patch until we get the official release from TI?
[14:11] <ogra> i dont think so
[14:11] <ogra> afaik the next merge will be the .35 kernel
[14:11] <rsalveti> ogra: but the other problem is that we still don't know when we're going to get it :-)
[14:12] <ogra> this week, ask ndec
[14:12] <ogra> or cooloney
[14:12] <rsalveti> the patches will be inside the new release, so the only problem is that in the future we should look at the release carefully to skip those patches
[14:12] <rsalveti> but, cooloney or lag can say more about it
[14:13] <rsalveti> I'm afraid of getting this patch into our tree just by the end of the month
[14:13] <rsalveti> and until we get it, at least the LG monitors will be broken :-)
[14:13] <NCommander> can I move on?
[14:14] <rsalveti> NCommander: sure
[14:14] <NCommander> [topic] standing items
[14:14] <MootBot> New Topic:  standing items
[14:14] <NCommander> [link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-3.html
[14:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-3.html
[14:15] <NCommander> [link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10-beta.html
[14:15] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10-beta.html
[14:15] <ogra> NCommander, wrong chart :P
[14:15] <ogra> oh, heh
[14:15] <ogra> you already corrected yourself
[14:15] <NCommander> ogra: figure I should post both since we just concluded A3 and started beta
[14:16] <ogra> right, everyone who still has A3 items open, please move them to beta in the spec pages
[14:17] <ogra> dyfet, ^^^
[14:17] <dyfet> ok
[14:17] <ogra> do we know when persia will be done moving ?
[14:17] <ogra> NCommander, any idea ?
[14:18] <NCommander> ogra: he's done moving.
[14:18] <NCommander> I honestly don't know why he's not here, he was supposed to have internet restored yesterday
[14:18] <ogra> he has a lot of items for beta
[14:19] <NCommander> ogra: I'll call him after I call davidm later today
[14:19] <ogra> well, three of ten :)
[14:19] <NCommander> [topic] Kernel Status (cooloney, mpoirier, lag)
[14:19] <MootBot> New Topic:  Kernel Status (cooloney, mpoirier, lag)
[14:19]  * NCommander should add ericm to that
[14:19] <ogra> NCommander, do you have any testplan for the "test unsupported hardware" item ?
[14:19] <ogra> i.e. something you can give to GrueMaster
[14:20] <ogra> (i know the upgrade tests failed miserably)
[14:20] <mpoirier> /bugs.launchpad.net/bugs/591941: mmc -110 error - Rogue patch was identify.  Kernel team is not convinced the best way to address the problem is to revert patch.  Further discussion will take place today.
[14:20] <mpoirier> /bugs.launchpad.net/bugs/608266: no more /dev/mtdblock - the driver is compiled in but the base address is not properly set.  Init of mtd device changed between Lucid and Maverick.  Base address seem to have been left out.
[14:20] <mpoirier> ...
[14:20] <ogra> mpoirier, there were new patches added today
[14:20] <NCommander> ogra: using a Dove AVD1 board mostly. The flash-kernel changes work properly at this point if you trick the installer to install -dove kernel
[14:20] <NCommander> ogra: I'm just working on the installer bits now
[14:20] <ogra> mpoirier, weird, i thought the base address needs to come from userspace tools
[14:21] <mpoirier> no, not for the initial scan.
[14:21] <ogra> ah, k
[14:22] <ogra> lag, anything to add to the above ?
[14:24] <NCommander> I'm guessingnot
[14:24] <NCommander> [topic] QA Status (GrueMaster)
[14:24] <MootBot> New Topic:  QA Status (GrueMaster)
[14:24] <GrueMaster> Alpha 3 testing was rather rushed.
[14:24] <ogra> omap4 was really good though
[14:24] <ogra> i stopwatched the resizing today ;)
[14:24] <GrueMaster> Last minute churn in the pool cause the images to be delayed until Wednesday.
[14:25] <ogra> 2:30 for the whole resizing from plugging in power to seeing the oem-config wallpaper
[14:25] <GrueMaster> Most of the image testing was done on omap4 as it was faster, and both images are the same but for the kernel & boot loader bits.
[14:26] <ogra> right, and we have the MMC errors in omap3
[14:26] <ogra> which kind of block the whol installation
[14:26] <lag> Sorry
[14:26] <lag>  * Marvel (mvl-dove)
[14:26] <lag>    * Nothing new this week
[14:26] <lag>  * Freescale (fsl-imx51)
[14:26] <lag>    * MISC     : Prepared a kernel package for Freescale to verify fix for the board bricking issue
[14:26] <lag>  * Texas Instruments (ti-omap)
[14:26] <lag>    * GIT PULL : ti-omap4 branch is now at 903.7 which contains latest 2.6.34 TI kernel release.
[14:26] <lag>    * ON GOING : B591941 found issue using bisect. In discussions to decide on a solution
[14:26] <lag>    * PATCH    : B592295 this should have been fixed in the latest TI release
[14:26] <lag>    * PATCH    : B605832 as above
[14:26] <lag>    * PATCH    : B612895 as above
[14:26] <lag>    * ON GOING : B605488 no one has seen this since it was reported
[14:26] <lag> ..
[14:27] <lag> Was practising my presentation for UHS *embarrassed smiley*
[14:27] <lag> ..
[14:28] <ogra> UHS ?
[14:28] <ogra> ubuntu hardware shop ?
[14:28] <lag> Summit
[14:28] <ogra> ah
[14:29] <GrueMaster> Are we done with kernel updates?
[14:29] <lag> Yep
[14:30] <ogra> other QA topics ?
[14:30] <GrueMaster> Current images fail to run oem-config.  Churn in the X drivers is holdig back image builds today.
[14:30] <ogra> i still dont get why oem-config fails though
[14:30] <ogra> it seems to detect an already running X server
[14:30] <ogra> and then X refuses to start
[14:31] <GrueMaster> Updates from A3 to current now make Unity run as default on Beagle.  Performance REAL slow now.
[14:31] <ogra> additionally we seem to have an issue with console switching, the X session stays up even though oem-config died
[14:31] <ogra> you need to hit enter to actually see the console thats already up on that tty
[14:31] <rsalveti> GrueMaster: probably will be better with the sgx driver
[14:32] <rsalveti> but still no support for it
[14:32] <ogra> rsalveti, we wont have the SGX driver in our images
[14:32] <rsalveti> ogra: I know, but won't we have the option to install it later on?
[14:32] <rsalveti> last step on oem-config, for example?
[14:32] <NCommander> rsalveti: bit hard to install it without X in the first place
[14:32] <GrueMaster> Issue I reported at Sprint about Unity and bleed through was clearly visible on beagle.
[14:32]  * rsalveti heard something like that
[14:32] <ogra> GrueMaster, file a bug for the upgrade issue please, seems didrocks enforces unity somehow in his settings package
[14:33] <ogra> NCommander, we have X and should provide the 2D session by default
[14:33] <rsalveti> yep
[14:33] <ogra> the breakage is that unity enforces the switch during an upgrade
[14:33] <GrueMaster> ok
[14:34] <NCommander> [topic] ARM Porting/FTBFS status (NCommander, dyfet)
[14:34] <MootBot> New Topic:  ARM Porting/FTBFS status (NCommander, dyfet)
[14:34] <NCommander> Nothing new to report expect I need to fix KDE sometime soon.
[14:34]  * NCommander is finally done travelling constantly thus might have a chance to do so
[14:34]  * ogra sees a ton of new packages
[14:34] <dyfet> and I will have a patch for mutter
[14:35] <Riddell> KDE SC 4.5 just got uploaded last night
[14:35] <ogra> NCommander, are you on top of the dh-shlibs thing ?
[14:35] <Riddell> only kdebindings is broken on ARM, everything else is fine I think
[14:35] <ogra> NCommander, still blocks libgd2
[14:35] <NCommander> ogra: no.
[14:35] <NCommander> ogra: *sigh*, I'll get right on that.
[14:35] <ogra> NCommander, thanks
[14:35] <dyfet> I had a temporary patch for libgd2 itself
[14:35] <ogra> NCommander, i think there is a libc fix in debian we just need to pull
[14:36] <ogra> dyfet, that makes it not use libc ?
[14:36] <NCommander> ogra: I talked to doko about that awhile ago, he wasn't sure what the cause is
[14:36] <NCommander> I'm not inclined to spend a lot of time trying to properly fix it for maverick TBH
[14:36] <dyfet> yes, but i wanted to see what happens with the other changes
[14:37] <ogra> NCommander, well, worst case just pull the old fix back into dh-shlibs
[14:37] <NCommander> ogra: that was the plan
[14:37] <ogra> it worked for two reelases already ...
[14:37] <ogra> i dont see a reason to not use the same until upstream is actually fixed
[14:37]  * ogra sees clutk on the ftbfs list
[14:37] <ogra> thats critical for TI work, please priorize
[14:38] <NCommander> sure, no problem
[14:38] <ogra> dyfet, how about telepathy-glib ?
[14:38] <ogra> you said last wee you wanted to take a look
[14:39] <dyfet> yes this was a dbus test failure
[14:42] <ogra> any fix in sight ?
[14:42] <ogra> did you talk to seb128 ?
[14:43] <dyfet> yes, but mostly what I had tested in it looks too ugly for a fix yet
[14:45] <NCommander> can I move on?
[14:45] <ogra> NCommander, move ?
[14:45] <ogra> hsnap
[14:45] <NCommander> [topic] ARM Image Status (ogra, NCommander)
[14:45] <MootBot> New Topic:  ARM Image Status (ogra, NCommander)
[14:45] <NCommander> They exist :-)
[14:45] <ogra> weel, mostly covered above already :)
[14:45] <ogra> they built until the X team broke them ...
[14:45] <NCommander> Dove images are buildable, but still in manual mode
[14:45] <ogra> and the last build has oem-config issues
[14:46] <ogra> nothing to see here, move on :)
[14:46] <NCommander> [topic] Any Other Business
[14:47] <MootBot> New Topic:  Any Other Business
[14:47]  * NCommander has none
[14:47]  * ogra neither
[14:47] <NCommander> ok
[14:47] <NCommander> I'm going to close the meeting unless anyone objects
[14:47] <NCommander> 5
[14:47] <NCommander> 4
[14:47] <NCommander> 3
[14:47] <NCommander> 2
[14:47] <NCommander> 1
[14:47] <NCommander> #endmeeting
[14:47] <MootBot> Meeting finished at 08:47.
[14:47] <ogra> booo
[14:47] <NCommander> ogra: :-P
[14:47] <ogra> :)
[14:55] <pitti> kees, Keybuk, cjwatson: meeting in 5?
[14:55] <pitti> is "chair: Keybuk" still correct on https://wiki.ubuntu.com/TechnicalBoardAgenda ?
[14:55] <pitti> (we skipped the previous meeting, so the date is obviously wrong)
[14:56] <Keybuk> pitti: I'm at Linuxcon, hard to chair from here
[14:56] <pitti> ok, can do today
[14:57] <Keybuk> I'll take the next one though, since the big item in that meeting will be mine
[14:58] <pitti> Keybuk: ok, I'll put you down as chair in two weeks then
[14:58]  * pitti pung sabdfl
[14:59] <pitti> mdz: will you join the TB meeting?
[15:00] <Keybuk> not sure where he is; he's either here, or in Lexington
[15:01] <pitti> SMSed mdz, cjwatson, and kees
[15:02] <pitti> Keybuk: did you follow the post app release process discussion on the ML?
[15:02] <Keybuk> pitti: I haven't had working e-mail for over a week
[15:02] <Keybuk> by this point, mailman has almost certainly unsubscribed me from the ML
[15:02] <pitti> Keybuk: we got votes from sabdfl, cjwatson, kees, and me, but your's is still msssing
[15:02] <pitti> Keybuk: oh, this was July 23
[15:03] <Keybuk> I don't remember seeing it, sorry
[15:03] <pitti> np
[15:04] <pitti> Keybuk: do you have something to discuss for the meeting?
[15:04] <pitti> if nobody else turns up, I'll ask the "kill sparc/ia64" topic on the ML
[15:04]  * ScottK thought it was just kill sparc this cycle?
[15:04] <Keybuk> pitti: that's the big topic for the next meeting
[15:05] <Keybuk> we said we'd give until feature freeze
[15:05] <pitti> there was an announcement/question some weeks ago, and I thought it included both
[15:05] <Keybuk> it's _not_quite_ feature freeze yet
[15:05] <pitti> Keybuk: ah, understood
[15:05] <pitti> Keybuk: so, I'll just leave it on https://wiki.ubuntu.com/TechnicalBoardAgenda then
[15:05] <Keybuk> it does include both
[15:05] <Keybuk> both ia64 and sparc will be dropped after thursday
[15:05] <Keybuk> we'll do that formally at the next meeting I think
[15:05] <Keybuk> or maybe just in the ML in the meantime
[15:06] <sabdfl> hello all, sorry i'm late
[15:07] <Keybuk> pitti: yes please
[15:07] <pitti> hey Mark
[15:08] <sabdfl> howdy
[15:08] <pitti> still no quorum yet
[15:08] <pitti> I pinged/SMSed cjwatson/mdz/kees 8 mins ago, let's see whether someone else turns up
[15:09] <pitti> sabdfl: do you have anything to discuss?
[15:09] <pitti> https://wiki.ubuntu.com/TechnicalBoardAgenda is the current topic list; ports already got moved to next meeting
[15:10] <sabdfl> nothing from me to add to the agenda
[15:15] <pitti> ok, timing out I'd say; we don't have quorum, and the two topics are from absent members
[15:16] <pitti> next meeting on 2010-08-24, Keybuk agreed to chair
[15:21] <kees> timezone failure. I'm at LinuxCon (I think mdz is here too), but there are sessions running
[15:41] <sabdfl> ok, cheers all, hope you are all well
[17:59] <manjo> \o
[17:59] <lag> o/
[17:59] <lag> manjo: Dude!
[17:59] <cking_> \o
[17:59] <manjo> lag, dude
[17:59] <lag> "My eyes dude!"
[18:00] <manjo> heh
[18:00] <kamal> o/
[18:00] <lag> ;)
[18:00] <JFo> o/
[18:00] <smb> \o
[18:00] <manjo> lag, currently its my throat... lost my voice
[18:00] <JFo> dood
[18:00] <bjf> #startmeeting
[18:00] <MootBot> Meeting started at 12:00. The chair is bjf.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <lag> JFo: :D
[18:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <JFo> :)
[18:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:01] <bjf> #
[18:01] <bjf> # NOTE: '..' indicates that you are finished with your input.
[18:01] <bjf> #
[18:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:01] <bjf> [TOPIC] ARM Status (lag)
[18:01] <MootBot> New Topic:  ARM Status (lag)
[18:01] <lag>  * Marvel (mvl-dove)
[18:01] <lag>    * Nothing new this week
[18:01] <lag>  * Freescale (fsl-imx51)
[18:01] <lag>    * MISC     : Prepared a kernel package for Freescale to verify
[18:01] <lag>  * Texas Instruments (ti-omap)
[18:01] <lag>    * GIT PULL : ti-omap4 branch is now at 903.7 which contains latest 2.6.34 TI kernel release.
[18:01] <lag>    * ON GOING : B591941 found issue using bisect. In discussions to decide on a solution
[18:01] <lag>    * PATCH    : B592295 this should have been fixed in the latest TI release
[18:01] <lag>    * PATCH    : B605832 as above
[18:01] <lag>    * PATCH    : B612895 as above
[18:01] <lag>    * ON GOING : B605488 no one has seen this since it was reported
[18:01] <lag> ..
[18:02] <tgardner> lag, any feedback on the freescale board killer?
[18:02] <lag> tgardner: * MISC     : Prepared a kernel package for Freescale to verify
[18:02] <tgardner> lag, so, no feedback then?
[18:02] <lag> tgardner: I was told off for mentioning it in the ARM status meeting earlier today so I took it off the end of the disc
[18:03] <lag> tgardner: Not that I know of, no
[18:03] <tgardner> lag, ack
[18:03] <tgardner> ..
[18:03] <lag> ..
[18:03] <bjf> [TOPIC] Release Metrics: (JFo)
[18:03] <MootBot> New Topic:  Release Metrics: (JFo)
[18:03] <JFo> Release Meeting Bugs (3 bugs, 9 Blueprints)
[18:03] <JFo> [18:03] <JFo>  * 2 linux kernel bugs (up 1)
[18:03] <JFo>  * 0 linux-fsl-imx51 bugs (no change)
[18:03] <JFo>  * 0 linux-ec2 bugs (no change)
[18:03] <JFo>  * 0 linux-mvl-dove bugs (no change)
[18:03] <JFo>  * 0 linux-ti-omap bugs (no change)
[18:03] <JFo>  * 0 linux-meta-ti-omap bug (down 1)
[18:03] <JFo> [18:03] <JFo>  * 25 linux kernel bugs (no change)
[18:03] <JFo>  * 0 linux-fsl-imx51 bugs (down 2)
[18:03] <JFo>  * 0 linux-ec2 bugs (no change)
[18:03] <JFo>  * 2 linux-mvl-dove bugs (no change)
[18:03] <JFo>  * 2 linux-ti-omap bugs (no change)
[18:03] <JFo>  * 0 linux-meta-ti-omap bug (down 1)
[18:03] <JFo> [18:04] <JFo>  * 14 blueprints
[18:04] <JFo> *** NOTE: This listing includes HWE Blueprints***
[18:04] <JFo> [18:04] <JFo>  * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on
[18:04] <JFo>  * Breakdown by status:
[18:04] <JFo>    http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/
[18:04] <JFo> ..
[18:04] <bjf> [TOPIC] Blueprint: kernel-maverick-apparmor (jjohansen)
[18:04] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor
[18:04] <MootBot> New Topic:  Blueprint: kernel-maverick-apparmor (jjohansen)
[18:04] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor
[18:04] <bjf> Bug 615947 - Fixed and updated regression test suites.  Will get a patch
[18:04] <bjf> out to kernel list tonight.
[18:04] <bjf> User side updates to log parsing should be commited today or tomorrow.
[18:05] <bjf> ..
[18:05] <bjf> [TOPIC] Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)
[18:05] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-new-kernel-on-lts
[18:05] <MootBot> New Topic:  Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)
[18:05] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-new-kernel-on-lts
[18:05] <tgardner> LTS backports are tracking Maverick at 2.6.35-14.20
[18:05] <tgardner> ..
[18:05] <bjf> [TOPIC] Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)
[18:05] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel
[18:05] <MootBot> New Topic:  Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)
[18:05] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel
[18:05] <bjf> Bug #612875 virtual kernel in EC2 only boots from pv-grub.  This is
[18:05] <bjf> going to require user image creation work on packaging up an aki.
[18:05] <bjf> Basically we need to strip the bzImage header off leaving only the
[18:05] <bjf> gzipped vmlinux.  This is low priority and probably won't be done.
[18:05] <bjf> Bug # 574910 High load averages on Lucid while idling.  This is in
[18:05] <bjf> the Xen patchset, and I have a new kernel being built to test later today.
[18:05] <bjf> I have 4 bugs that I haven't really gotten a chance to look at yet,
[18:05] <bjf> and anyone who wants is more than welcome to them.
[18:05] <bjf> Bug #606373 cloud-init output does not get to console when booted with and
[18:06] <bjf> ramdisk.  This looks like it is a variation on Bug #431103, except with
[18:06] <bjf> the pv-ops hvc console instead of xvc0.
[18:06] <bjf> Bug #613083 user-data is corrupted inside metadata service
[18:06] <bjf> Bug #613022 ssh daemon hangs after publickey packet sent
[18:06] <bjf> Bug # 613273 kernel panic on ec2 in system_call_fastpath
[18:06] <bjf> ..
[18:06]  * smb blinks
[18:06] <bjf> [TOPIC] Blueprint: kernel-maverick-bug-handling (JFo)
[18:06] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:06] <MootBot> New Topic:  Blueprint: kernel-maverick-bug-handling (JFo)
[18:06] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:06] <JFo> Nothing to report
[18:06] <JFo> ..
[18:07] <bjf> [TOPIC] Blueprint: kernel-maverick-upstart (apw)
[18:07] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-upstart
[18:07] <MootBot> New Topic:  Blueprint: kernel-maverick-upstart (apw)
[18:07] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-upstart
[18:08] <apw> Looking into an issue wherein console opens are being failed.  Believe we have the issue diagnosed, a solution is in progress.
[18:08] <apw> Nothing else to report.
[18:08] <apw> ..
[18:08] <bjf> [TOPIC] Blueprint: kernel-maverick-bios-test-automation (cking)
[18:08] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:08] <MootBot> New Topic:  Blueprint: kernel-maverick-bios-test-automation (cking)
[18:08] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:08] <cking_> Changes since last week:
[18:08] <cking_> * update fwts from 0.17.2 to 0.17.9 in maverick universe
[18:08] <cking_> * USB key images at http://kernel.ubuntu.com/~kernel-ppa/testing (with help from bjf)
[18:08] <cking_> * --P, --power-states category for S3 S4 tests
[18:08] <cking_> * better AML parsing for hpet_check test
[18:08] <cking_> * nx test: print out model number as integer (fixes segfault)
[18:08] <cking_> * fix typos in man page
[18:08] <cking_> ..
[18:08] <bjf> [TOPIC] Status: Maverick (ogasawara)
[18:08] <MootBot> New Topic:  Status: Maverick (ogasawara)
[18:08] <ogasawara> Since our Maverick kernel is now rebased on v2.6.35, we've started applying 2.6.35.y pre-stable patches.  We'll keep Maverick in sync with the 2.6.35.y releases as they become available.
[18:09] <ogasawara> Maverick Beta is Thurs Sept 2nd, ie ~3weeks away.  Also keep in mind that Kernel Freeze is Thurs Sept 16th, ie ~5weeks away.  We are above our Beta burn down chart's trend line but I'm not too worried as most of the open tasks are investigative in nature and not release critical.
[18:09] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-ubuntu-10.10-beta.html
[18:09] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10-beta
[18:09] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-ubuntu-10.10-beta.html
[18:09] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10-beta
[18:09] <ogasawara> ..
[18:09] <bjf> [TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:09] <MootBot> New Topic:  Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:09] <smb> ||                   || Upd./Sec.     || Proposed      || TiP || Verified    ||
[18:09] <smb> || Dapper: Kernel    || 2.6.15-55.86  ||               ||     ||             ||
[18:09] <smb> || Hardy:  Kernel    || 2.6.24-28.73  ||               ||     ||             ||
[18:09] <smb> || Jaunty: Kernel    || 2.6.28-19.62  ||               ||     ||             ||
[18:10] <smb> || Karmic: Kernel    || 2.6.31-22.61  ||               ||     ||             ||
[18:10] <smb> || =       mvl-dove  || 2.6.31-214.29 ||               ||     ||             ||
[18:10] <smb> || =       fsl-imx51 || 2.6.31-112.28 ||               ||     ||             ||
[18:10] <smb> || =       ec2       || 2.6.31-307.16 ||               ||     ||             ||
[18:10] <smb> || Lucid:  Kernel    || 2.6.32-24.39  ||               ||     ||             ||
[18:10] <smb> || =       mvl-dove  || 2.6.32-207.21 ||               ||     ||             ||
[18:10] <smb> || =       fsl-imx51 || 2.6.31-608.15 ||               ||     ||             ||
[18:10] <smb> || =       ti-omap   || 2.6.33-502.9  ||               ||     ||             ||
[18:10] <smb> || =       ec2       || 2.6.32-308.14 ||               ||     ||             ||
[18:10] <smb> fsl-imx51 has not been released in security this time as there had been
[18:10] <smb> problems with certain board revisions. We need to add one more SRU patch
[18:10] <smb> before next upload.
[18:10] <smb> For Lucid a new proposed kernel which addresses a few priority issues has been
[18:10] <smb> uploaded and will get accepted into proposed as soon as the CD images for the
[18:10] <smb> point release are settled.
[18:10] <smb> tgardner, Re: fsl board killer
[18:10] <smb> I think I got a rough idea. There seem to be v2.5 and v3 boards. Claims are that there is something with an acronym I  don't know
[18:11] <smb> which can get destroyed by apparently all older kernels. Bryan just made a SRU reguest for a patch that fsl claims prevents this
[18:11] <smb> How we could have ended up with testing only on v3 boards before is a bit of a miracle.
[18:11] <smb> ..
[18:11] <tgardner> smb, but with no feedback from FSL that it actually fixes the problem.
[18:12] <smb> I have not heard anything direct
[18:12] <tgardner> I'd wait to apply until we know for sure
[18:12] <tgardner> ..
[18:12] <smb> I think Bryan had build a kernel with it and sent it to them
[18:12] <smb> We need to get out of him what they said to it
[18:12] <smb> ..
[18:13] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[18:13] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[18:13] <JFo> 233 Maverick Bugs (up 32)
[18:13] <JFo> 1132 Lucid Bugs (up 8)
[18:13] <JFo> Current regression stats (broken down by release):
[18:13] <JFo> [18:13] <JFo>   * 118 maverick bugs (up 7)
[18:13] <JFo>   * 226 lucid bugs (no change: to be converted to regression-release)
[18:13] <JFo> [18:13] <JFo>   * 42 lucid bugs (down 1)
[18:13] <JFo>   * 6 karmic bugs (no change)
[18:13] <JFo>   * 4 jaunty bugs (no change)
[18:13] <JFo>   * 1 hardy bug (no change)
[18:13] <JFo> [18:13] <JFo>   * 181 lucid bugs (no change)
[18:13] <JFo>   * 44 karmic bugs (no change)
[18:13] <JFo>   * 19 jaunty bugs (no change)
[18:13] <JFo>   * 2 hardy bugs (no change)
[18:13] <JFo> [18:13] <JFo>   * 3 lucid bugs (down 1)
[18:13] <JFo>   * 1 karmic bug (no change)
[18:13] <JFo> ..
[18:14] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[18:14] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[18:14] <JFo> Today is the Bug Day. We are focusing on bugs incorrectly listed as new. These will be put in the correct state and their subsystem tag will be added. I'll update next week with the result. We will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday, as these seem to be working out very well. Reviewers, please take a look at your needs-review lists and help us keep the process moving. I will be in Oxford,
[18:14] <JFo>  UK next week, so I'll send my metrics update to bjf via e-mail.
[18:14] <JFo> ..
[18:15] <bjf> [TOPIC] Triage Status (JFo)
[18:15] <MootBot> New Topic:  Triage Status (JFo)
[18:15] <JFo> Great work is being done daily in our bugs due to many folks from other userspace systems helping to triage as well as providing numerous nuggets of wisdom to the bug reporters themselves. We met simar during last weeks meeting. simar is workin on expanding multitouch knowledge and looking over those bugs. holstein has been looking at kernel bugs and is currently undergoing bug mentorship with hggdh. I have been mentoring chazn85 also, focusing on
[18:15] <JFo>  tagging and requests for information. chazn85 has also been looking through our wiki documentation to bring inconsistencies to my attention.
[18:15] <JFo> I'd also like to thank charlie-tca for all of the work he has been doing ion kernel bugs as well.
[18:16] <JFo> ..
[18:16] <bjf> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:16] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:16] <JFo> o/
[18:16] <bjf> JFo, go
[18:16] <JFo> I'm having an intermittent issue with my e-mail as far as sending goes
[18:17] <JFo> if I ask you about something I sent you that you don't remember or didn't get
[18:17] <JFo> I apologize in advance :)
[18:17] <JFo> ..
[18:17] <JFo> oh
[18:17] <JFo> one other think
[18:17] <JFo> thing*
[18:17] <bjf> JFo, keep going :-)
[18:17] <JFo> we will be having our Monday bug chat on Friday since I will be in Oxford and unavailable next week
[18:18] <JFo> just FYI
[18:18] <JFo> ..
[18:18] <ogasawara> JFo: same time?
[18:18] <JFo> :-)
[18:18] <JFo> ogasawara, yes indeed
[18:18] <JFo> I'll put a calendar item up
[18:18] <tgardner> JFo, update the calendar?
[18:18] <JFo> tgardner, ;)
[18:18] <JFo> doing it now
[18:18] <bjf> going ..
[18:18] <bjf> going ..
[18:18] <bjf> #endmeeting
[18:18] <MootBot> Meeting finished at 12:18.
[18:18] <smb> thanks bjf
[18:19] <kamal> thanks bjf
[18:20] <JFo> thanks bjf
[18:20] <cking_> ta bjf
[18:57] <jiboumans> o/
[18:58] <ttx> ~o~
[18:58] <hggdh> ~ô~
[18:59] <Daviey> o/
[18:59] <mathiaz> O:P
[19:00] <ttx> let's get started !
[19:00] <ttx> #startmeeting
[19:00] <MootBot> Meeting started at 13:00. The chair is ttx.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:00] <ttx> Incredible agenda is here: https://wiki.ubuntu.com/ServerTeam/Meeting
[19:00] <ttx> [TOPIC] Review ACTION points from previous meeting
[19:00] <MootBot> New Topic:  Review ACTION points from previous meeting
[19:00] <ttx> * SpamapS to send ruby gems proposel to ubuntu-devel
[19:01] <ttx> * zul to clean up the SRU assigne list by prodding people on status
[19:01] <ttx> (maybe we are missing spamaps)
[19:01] <ttx> (maybe we are missing zul)
[19:01] <ttx> * everyone to pick 1 or 2 papercuts for the beta cycle
[19:01] <hggdh> isn't zul on LinuxConf?
[19:01] <ttx> ^that one is incomplete, looking at https://launchpad.net/server-papercuts/+milestone/maverick-beta
[19:01] <jiboumans> we are missing zul afaik, but spamaps should be around
[19:02]  * kim0 is not able to attend this meeting (have to run). But you all know the maps app made its splash. Nothing else to discuss
[19:02] <ttx> kim0: ack
[19:02] <smoser> o/
[19:02] <Daviey> kim0: top work on that :)
[19:02] <kim0> thanks folks
[19:02] <ttx> so I'll action you all again... please do it by next week
[19:02] <ttx> [ACTION] everyone to pick 1 or 2 papercuts for the beta cycle
[19:02] <MootBot> ACTION received:  everyone to pick 1 or 2 papercuts for the beta cycle
[19:02] <jiboumans> kim0++ # nice job on the maps
[19:03]  * hggdh is already geo-located there...
[19:04] <ttx> Looking at http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html the list could use more cleaning
[19:04] <ttx> so I'll action zul again :)
[19:04] <ttx> [ACTION] zul to continue clean up the SRU assigne list by prodding people on status
[19:04] <MootBot> ACTION received:  zul to continue clean up the SRU assigne list by prodding people on status
[19:04] <ttx> mathiaz: did we have the rubygems proposal posted to ubuntu-devel ?
[19:04] <jiboumans> spamaps is waiting on the thumbs up afaik
[19:04] <mathiaz> ttx: not yet - we're currenlty reviewingit
[19:05] <ttx> ok
[19:05] <mathiaz> ttx: it should go out in the next week
[19:05] <ttx> [ACTION] SpamapS to finalize and send ruby gems proposel to ubuntu-devel
[19:05] <MootBot> ACTION received:  SpamapS to finalize and send ruby gems proposel to ubuntu-devel
[19:05] <jiboumans> mathiaz: fix still viable for maverick right?
[19:05] <mathiaz> jiboumans: I don't think so
[19:05] <mathiaz> jiboumans: was the goal to get it fixed in maverick?
[19:05] <jiboumans> mathiaz: the hope
[19:05] <mathiaz> jiboumans: I think it will take more time
[19:06] <jiboumans> mathiaz: i know maverick+1 is more realistic
[19:06] <mathiaz> jiboumans: ah - hope
[19:06] <ttx> I remember hope, it was good.
[19:06] <mathiaz> jiboumans: agreed - maverick+1 is more realistic
[19:06] <jiboumans> heh ttx
[19:06] <ttx> ok, moving on then :)
[19:06] <ttx> [TOPIC] Maverick development (jib)
[19:06] <MootBot> New Topic:  Maverick development (jib)
[19:06] <jiboumans> alpha3 delivered last week
[19:06] <jiboumans> beta started with this list: http://people.canonical.com/~pitti/workitems/maverick/canonical-server-ubuntu-10.10-beta.html
[19:07] <jiboumans> should be vetted by everyone, so that's the deliverable as far as i'm concerned
[19:07] <jiboumans> not much more to say to that ;)
[19:08] <ttx> ok, comments ?
[19:08] <jiboumans> i think it's a bit early to check on progress as we just started
[19:08] <ttx> ok, moving on then
[19:08] <ttx> [TOPIC] 10.04.1 release (ttx)
[19:08] <MootBot> New Topic:  10.04.1 release (ttx)
[19:09] <ttx> so this Thursday we have yet another milestone, with 10.04.1
[19:09] <smoser> or next tuesday
[19:09] <ttx> smoser: ?
[19:09] <hggdh> yes, robbiew just postponed it
[19:09] <jiboumans> it just got postponed
[19:09] <ttx> robbiew: damn you !
[19:10] <ttx> all my effects are gone
[19:10] <hggdh> :-)
[19:10]  * ttx thinks the server team will have to release it without him
[19:10] <smoser> the stare of death works on triceritops, but not on robbiew
[19:10] <ttx> ok, so...
[19:10]  * jiboumans would rather have a scuff with a triceratops
[19:10]  * SpamapS wonders who would win that epic battle.. robbiew vs. triceratops
[19:11] <jiboumans> spamaps: judging by museums world-wide, my money is on robbiew
[19:11] <Daviey> ttx: Should we be spending time testing Hardy -> 10.04.1 upgrades?
[19:11] <ttx> Daviey: yes, and some ISO should be spun early next week (or late this week)
[19:12] <ttx> in both cases I won't be around, so I'll brief someone (Daviey ?) to replace me
[19:12] <Daviey> ttx: OK.. will you be tracking that?
[19:12] <Daviey> ttx: I'm /away next week aswell :/
[19:12] <ttx> or a Daviey-mathiaz team, maybe
[19:12] <ttx> Daviey: and that got approved ? Let me fix that.
[19:12] <Daviey> hah
[19:13] <ttx> any volunteer ?
[19:13] <smoser> hm... I half raise a hand.
[19:13] <ttx> I could nominate zul, since he is having fun at Linuxcon
[19:13] <jiboumans> ttx: we'll sort it between me and mathiaz
[19:13] <smoser> and zul just dropped.
[19:14] <ttx> right, we'll sort it off-meeting
[19:14] <ttx> and I'll send out an email
[19:14] <ttx> Our last minte thing is Last-minute merge/reupload for bug 571057
[19:14] <ttx> which was handled succesfully by mathiaz
[19:15] <ttx> and in verification-needed
[19:15] <mathiaz> I'll do the verification later today
[19:15] <mathiaz> once the package has built
[19:15] <ttx> great, thanks for taking care of that
[19:15] <ttx> mvo might do some upgrade testing, I'll check that with him
[19:16] <ttx> any questions before we move on ?
[19:16] <ttx> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:16] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:17] <ttx> hggdh: floor is yours
[19:17] <hggdh> nothing new, except having lots of fun with eucalyptus
[19:17] <ttx> "fun" as in regressions ?
[19:17] <hggdh> er, yes, I would say so. Very much fun
[19:17] <jiboumans> hggdh: what's the state on the blocking issues found last week(s)?
[19:17] <Daviey> jiboumans: I have pushed to a PPA, which should fix the major issues we were concerned about
[19:18] <Daviey> ie, registration and topology
[19:18] <hggdh> jiboumans: Daviey just built a new revision, and I just installed it. Will begin to test ASAP
[19:18] <hggdh> jiboumans: OTOH, we cannot use volumes anymore...
[19:18] <jiboumans> hggdh, daviey: excellent. let us know how it goes
[19:18] <hggdh> which I will also test on this revision
[19:19] <Daviey> If that works out well, i'll get it uploaded loater tonight / tomorrow morning
[19:19] <ttx> Daviey: so we should have an ISO tomorrow morning to test topology2 ?
[19:20] <Daviey> ttx: Hmm.. that means uploading it tonight then
[19:20] <Daviey> which i can prepare..
[19:20] <hggdh> Daviey: I would get it done no matter what
[19:20] <hggdh> so, early tomorrow morning (early for me) I can hit topo2
[19:20] <ttx> Daviey: we can do tomorrow morning
[19:21] <smoser> is it appropriate for me to ask if anyone is [successfully] using uec-provisioning  ? or should that wait till "open discussion"
[19:21] <hggdh> Daviey: reasoning is it is difficult to get worse than what we have now
[19:21] <ttx> smoser: go ahead
[19:21] <smoser> anyone ? ccheney  ?
[19:21] <ttx> smoser: haven't used it yet
[19:22] <hggdh> I have not, not prepared for it
[19:22] <smoser> i'm wanting to give it a try, but my last attempts ran into all sorts of archive problems that generally blocked me.
[19:22] <ttx> smoser: might play with it tomorrow
[19:22] <Daviey> ttx: I'm guessing you'll be around in a few hours.. fancy sponsoring that please?
[19:22] <Daviey> ttx; Assuming you are on US timezone still
[19:23] <ttx> I can sponsor in the next 2 hours if needed
[19:23] <ttx> any other question to hggdh / topic for QA ?
[19:23] <SpamapS> I had added one
[19:23] <Daviey> smoser: I'm using uec-provisioning
[19:23] <ttx> Bug rate extremely high last few weeks -- Triaging getting behind (SpamapS)
[19:23] <smoser> Daviey, sweet.
[19:23] <SpamapS> about bug triaging.. I just noticed that it has been spiking a lot the last 3 weeks
[19:24] <ttx> SpamapS: http://webnumbr.com/ubuntu-server-triage shows a good current status...
[19:24] <SpamapS> It was at 16 this morning...
[19:24] <ttx> I'm not sure it's highly unusual
[19:24] <mathiaz> SpamapS: I went through them today
[19:25] <SpamapS> I've been triaging one every day..
[19:25] <SpamapS> but, n/m .. I guess its normal ;)
[19:25] <SpamapS> I'd love to see the *rate* graphed, not just the state.
[19:25] <ttx> ok, mocing on then :)
[19:26] <ttx> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:26] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:26] <ttx> I don't think we have John
[19:26] <ttx> I wanted to raise the EC2 kernel issues, I guess that will wait a few
[19:27] <jiboumans> pinging him now
[19:27] <jiboumans> take the next topic, we'll revisit
[19:27] <smoser> jjohansen is in boston linuxcon
[19:27] <ttx> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[19:27] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[19:27] <jiboumans> smoser: aye, but not idle on irc... so if he's around, we'll do the topic.. if not, later
[19:27] <ttx> we don't have sommer either :)
[19:28] <ttx> [TOPIC] Weekly Updates & Questions for the Community Team (kim0)
[19:28] <MootBot> New Topic:  Weekly Updates & Questions for the Community Team (kim0)
[19:28] <jiboumans> .. nor kim0 ;)
[19:28] <Daviey> heh, not here either :)
[19:28] <jiboumans> jjohansen is here though
[19:28] <ttx> So we had the update at the beginning of the meeting
[19:28] <jiboumans> wee
[19:28] <ttx> back to kernel, I guess
[19:28] <ttx> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:28] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:28] <jjohansen> hey \o
[19:28] <ttx> jjohansen: quick update on bug 597387 and Bug 574910: ?
[19:28] <jiboumans> hey jjohansen. thanks for making time during linuxcon
[19:30] <jjohansen> alright 597387 - is a couple issues it will need some user side support in stripping and packaging a kernel special as it is built different
[19:30] <jjohansen> erg no disregard wrong bug
[19:31] <jjohansen> 597387 - we are working in all zones
[19:31] <smoser> 597387 should probably be closed.
[19:31] <jjohansen> yeah
[19:31] <ttx> ah, good news
[19:31] <jiboumans> jjohansen++ smoser++ # awesome
[19:31]  * ttx closes
[19:32] <jjohansen> 574910 - I have a test kernel building, and I should have an update for that tonight
[19:32] <smoser> there are open issues though.
[19:32] <jjohansen> yes lots of bugs
[19:32] <smoser> http://paste.ubuntu.com/476072/ is the list i had from alpha-3
[19:32] <MootBot> LINK received:  http://paste.ubuntu.com/476072/ is the list i had from alpha-3
[19:32] <ttx> jjohansen: ok, so it sounds like you're on top on this one
[19:32] <jiboumans> jjohansen: i care very strongly about 574910 - is there anything we can do to expedite a fix?
[19:33] <jjohansen> well, the problem is the bug is in the large xen patchset, and its not bisectable so it is slow going
[19:34] <jjohansen> The 3 points I have is karmic version of it and Lucid, and future point
[19:34] <jiboumans> jjohansen: understood.. can we help testing? or ask pete nicely to give you more time? :)
[19:34] <jjohansen> and working through the thousands of changes is slow
[19:34] <jjohansen> jiboumans: basically I have been on it full time for the last few days
[19:35] <jjohansen> testing will help, I am going to publish a kernel tonight and get results back would be helpful
[19:36] <jiboumans> jjohansen: ttx and smoser should be able to coordinate testing help - don't hesitate to ask
[19:37] <jjohansen> jibousmans, right I will be bugging smoser
[19:37] <ttx> ok, moving on then
[19:37] <jjohansen> the other bugs I have poked at a bit, but no real results yet
[19:38] <jjohansen> ..
[19:38] <ttx> anything else for John ?
[19:38] <jiboumans> a beer next time i see him :)
[19:38] <jjohansen> hehe :)
[19:39] <ttx> [TOPIC] Weekly Updates & Questions for the Community Team (kim0)
[19:39] <MootBot> New Topic:  Weekly Updates & Questions for the Community Team (kim0)
[19:40] <ttx> pasting for reference:
[19:40] <ttx> * kim0 is not able to attend this meeting (have to run). But you all know the maps app made its splash. Nothing else to discuss
[19:40] <ttx> comments ?
[19:40] <jiboumans> tweet/blog it
[19:41] <jiboumans> see here:  http://foss-boss.blogspot.com/2010/08/ubuntu-server-10041-virtual-release.html
[19:41] <jiboumans> and here:  http://maps.ubuntu.com/
[19:42] <ttx> [TOPIC] Open Discussion
[19:42] <MootBot> New Topic:  Open Discussion
[19:44] <ttx> ...
[19:44] <Daviey> We need to get some movement on, Bug #613463 . I had hoped to have a discussion between cjwatson, smoser and myself.  However, cjwatson is on holiday at the moment; so we need to grab someone else suitable from foundations.  Scott?
[19:44] <smoser> i can really only think of the 2 ways to solve it.
[19:44] <ttx> Daviey: looks like not depending on grub would fix that, no ?
[19:44] <smoser> a.) cut up grub more
[19:45] <smoser> b.) do not list a dependency
[19:45] <ttx> I'd go for (b) for the time being
[19:45] <ttx> and ask Colin when he gets back
[19:45] <smoser> yeah. its definitely easy short term.
[19:45] <Daviey> Okay.. i'll push a fix for that.. easy nuff.
[19:46]  * Daviey done.
[19:46] <smoser> Daviey, i can push that
[19:46] <smoser> if you'd like
[19:47] <smoser> i'm touching it right now
[19:47] <Daviey> smoser: go for it.
[19:48] <ttx> ok, anything else ?
[19:48] <SpamapS> CEPH is in Maverick now! :)
[19:48]  * SpamapS ^5's mathiaz
[19:49] <ttx> [TOPIC] Announce next meeting date and time
[19:49] <MootBot> New Topic:  Announce next meeting date and time
[19:50] <ttx> Tuesday 2010-08-17 at 1800 UTC - #ubuntu-meeting
[19:50] <ttx> I won't be there, but have fun
[19:51] <ttx> #endmeeting
[19:51] <MootBot> Meeting finished at 13:51.
[19:51] <jiboumans> thanks all!
[23:59] <nhandler> Meeting time
[23:59] <PabloRubianes> yes meeting