[08:27] <huats> morning
[14:01]  * persia peers about
[14:02] <mpoirier> hello ?
[14:02]  * ogra waves
[14:02] <dyfet> needs coffee
[14:03] <czajkowski> there should be a bot in here that announces which meeting is starting
[14:03] <ogra> czajkowski, arm team :)
[14:03] <persia> czajkowski: Used to be, but google ical is special
[14:03] <czajkowski> ogra: thanks
[14:04] <czajkowski> I can go back to idling now
[14:04] <ogra> you dont want to know about our arms ?
[14:04] <czajkowski> you waved, clearly your arm works
[14:04] <ogra> one at least
[14:04] <persia> If only that was all it took :)
[14:04] <dyfet> he is clearly not disarmed
[14:05] <rsalveti> persia: add a section for rootstock, please
[14:05] <persia> Anyway, our usual chair seems absent.
[14:05] <persia> #startmeeting
[14:05] <MootBot> Meeting started at 08:05. The chair is persia.
[14:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:05] <persia> Agenda is at https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100727
[14:05] <persia> [LINK] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100727
[14:05] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100727
[14:05] <persia> (wait for rsalveti to update it before you load the page :) )
[14:06] <persia> Actions from the prior meeting is incomplete, but some can be dredged from prior logs, so:
[14:06] <persia> [TOPIC] dyfet to work on openjdk FTBFS
[14:06] <MootBot> New Topic:  dyfet to work on openjdk FTBFS
[14:06] <rsalveti> persia: go
[14:06] <ogra> persia, dropped
[14:06] <dyfet> That was dropped
[14:07] <persia> OK, then there's a reason it wasn't there :)
[14:07] <persia> [TOPIC] md5sums and manifests for daily images (NCommander)
[14:07] <MootBot> New Topic:  md5sums and manifests for daily images (NCommander)
[14:07] <ogra> the md5sum stuff is fixed, the manifest file copying isnt
[14:07] <ogra> i'm taking that over
[14:08] <ogra> (so add a new action)
[14:08] <persia> [ACTION] ogra to sort manifest files for live images
[14:08] <MootBot> ACTION received:  ogra to sort manifest files for live images
[14:08] <ogra> tx
[14:08] <persia> [TOPIC] NCommander to unbreak apport retracer
[14:08] <MootBot> New Topic:  NCommander to unbreak apport retracer
[14:08] <ogra> c/o
[14:08] <persia> I think this still isn't working, unless someone knows otherwise
[14:08] <persia> RIght.
[14:09]  * ogra doesnt
[14:09] <persia> [ACTION] NCommander to unbreak apport retracer
[14:09] <MootBot> ACTION received:  NCommander to unbreak apport retracer
[14:09] <persia> OK.  That's all the actions I see from http://irclogs.ubuntu.com/2010/07/13/#ubuntu-meeting.txt
[14:09] <ogra> yeah
[14:09] <persia> [TOPIC] Workitem tracker
[14:09] <MootBot> New Topic:  Workitem tracker
[14:09] <ogra> looks horrid
[14:09] <persia> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:09] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:10] <persia> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-3.html
[14:10] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-3.html
[14:11] <persia> Indeed.  Everyone with alpha-3 tasks should go do them tomorrow.
[14:11] <ogra> rsalveti, we need to make a rootstock release this week to close the spec items
[14:11] <rsalveti> ogra: we'll, don't worry
[14:11] <ogra> persia, tomorrow ?
[14:11] <persia> OK.  Today for those in less advanced timezones :)
[14:11] <ogra> persia, `??
[14:11] <ogra> why is that ?
[14:12] <ogra> there is still a week until A3
[14:12] <ogra> but it would be nice if we got below the trend line for fridays release team meeting
[14:12] <davidm> I'm concerned that we are so far behind for A3
[14:12] <persia> I guess, but if everyone tries to do a task in the next 24 hours, the graph will look better on Friday for the release meeting.  Is the point not to have a pretty graph?
[14:12] <ogra> by either postponing or closing
[14:12] <persia> closing is better.
[14:13] <ogra> well, i'm inclined to postpone lightweight panel
[14:13] <GrueMaster> I'm looking at my tasks and I think I am still blocked.
[14:13] <ogra> what i got from dx is far from even becoming a panel
[14:13] <davidm> I agree, it does not look good for this cycle
[14:13] <ogra> nothing i couls write in a week
[14:13] <GrueMaster> Testing the panel is one of my tasks.
[14:13] <ogra> right
[14:14] <davidm> ogra, can we get by with the old efl launcher?
[14:14] <ogra> NC|Alaska, is unlikely to work on subarch detection before A3 either
[14:14] <ogra> davidm, the panel is *additional* to the launcher
[14:14] <ogra> davidm, to replace the gnome panel, which we have to ship anyway for gdm
[14:14] <davidm> I misunderstood, I thought it was replacing part of it.
[14:15] <ogra> i'll just clean up the session and we're back to the lucid setup
[14:15] <davidm> OK
[14:15] <davidm> I think we have to do that
[14:15] <ogra> persia, [ACTION] ogra to re-enable the lucid efl session
[14:17] <davidm> dyfet, where are you on the mobile-m-omap-edid-autodetection
[14:17] <ogra> from subarch detection: [gruemaster]Test upgrade path [1 day]: TODO
[14:17] <persia> [ACTION] ogra to re-enable the lucid efl session
[14:17] <MootBot> ACTION received:  ogra to re-enable the lucid efl session
[14:17] <dyfet> coordinating the i2c issues with kernel team
[14:17] <ogra> GrueMaster, i think you can do that already, just dist-upgrade a beagle lucid->maverick
[14:17] <davidm> dyfet, when will it close?
[14:17] <ogra> dyfet, are there bugs filed `
[14:17] <GrueMaster> Ok.  Will add that to my todo for today.
[14:17] <persia> ogra: so, postpone subarch generally?  I thought this was nearly done and critical for broad board support.
[14:18] <ogra> dyfet, if so, please note them on the blueprint
[14:18] <dyfet> okay
[14:18] <ogra> persia, no idea for what michael needs it
[14:18] <dyfet> and yes there is a bug for this
[14:18] <ogra> persia, its an *additional* way of detecting subarches
[14:18] <ogra> we're still using the old one anyway
[14:19] <persia> I thought it was a fallback to use SoC-based solutions when the individual board couldn't be identified.
[14:19] <ogra> persia, right, but we only support boards we know atm
[14:20] <ogra> for which we still use cpuinfo
[14:20] <persia> Well, anyway, if it's not ready by Friday, best postpone, as lnding images after that is too tight.
[14:20] <persia> yeah, but that's a bug :)
[14:20] <ogra> well, one item is a warning message
[14:20] <ogra> that he should be able to implement in 1h
[14:20] <ogra> even on monday
[14:21] <persia> anyway* anyone have stuff about *other* blueprints?
[14:21] <rsalveti> there is rootstock
[14:21] <ogra> dyfet, there are a lot of WIs on the EDID spec you could start working on already
[14:21] <rsalveti> but we're planing to do a release this week and close the 2 items
[14:21] <ogra> rsalveti, just a matter of an upload ...
[14:21] <ogra> to close the WIs
[14:21] <rsalveti> yep, no more than that
[14:22] <persia> wasn't robclark working on a bunch of related stuff?
[14:22] <persia> (for EDID)
[14:22] <ogra> dyfet, if you have identified the missing pieces for I2C, coudl you rebuild a kernel with them enabled so you can start developing the script ?
[14:22] <ogra> persia, rob works on panda
[14:22] <ogra> the spec is for omap3 where you dont have edid tdetection in the omapfb driver
[14:22] <dyfet> ogra: I can do that, I got stuff unpacked and back together here
[14:23] <persia> Ah, so yes and no :)
[14:23] <ogra> dyfet, great
[14:23] <persia> Moving on...
[14:24] <persia> [TOPIC] Kernel status
[14:24] <MootBot> New Topic:  Kernel status
[14:24] <persia> cooloney: Why don't you go first
[14:24] <cooloney> yeah
[14:24] <cooloney> i just prepared a new omap4 branch for maverick
[14:25] <cooloney> it includes the latest TI release L24.8
[14:25] <cooloney> i tested on my board, more stable than before
[14:25] <ogra> also robclark's work from pargue ?
[14:25] <ogra> there are plenty of HDMI patches that fix lots of monitor issues
[14:26] <cooloney> robclark helped to figure out the HDMI issue.
[14:26] <ogra> not sure he sent them to you already
[14:26] <cooloney> but i think lag helped to test them
[14:26] <rsalveti> he posted a branch, but not sure if it's included on this one
[14:26]  * ogra doubts that
[14:26] <cooloney> ogra: no problem, i will check it later
[14:26] <ogra> cool! oney
[14:26] <persia> rsalveti: Could you make sure cooloney has the r
[14:27] <persia> branch url?
[14:27]  * ogra hands cooloney an r
[14:27] <rsalveti> http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commits/L24.7_panda-hdmi-patches
[14:27] <MootBot> LINK received:  http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commits/L24.7_panda-hdmi-patches
[14:27] <ogra> so persia is happy :)
[14:27] <persia> THanks :)
[14:27] <cooloney> thanks man
[14:27] <persia> mpoirier: ready?
[14:27] <mpoirier> yep.
[14:28] <mpoirier> https://bugs.launchpad.net/bugs/b563650 - kernel oops in dss/core.c when rebooting: put on hold 'cause no one can reproduce.
[14:28] <ogra> ++
[14:28] <mpoirier> https://bugs.launchpad.net/bugs/b591941 - SDHC card init failure: started looking into u-boot - need to track down default factory images.
[14:28] <mpoirier> Alpha3 kernel will be uploaded on Jul 30, meaning that any patch to be in included in Alpha3 must be submitted and reviewed before Jul 30.
[14:28] <mpoirier> ..
[14:29] <persia> aren't factory images available from the beagleboard wiki?
[14:29] <ogra> what do you call "factory" ?
[14:29] <mpoirier> nop, not the exact same ones you find in nand when first receiving your board.
[14:29] <persia> whatever was used initially in the factory :)
[14:29] <ogra> ah
[14:30] <mpoirier> I need the exact same branch - sd card seems to behave much better with it.
[14:30] <mpoirier> process was very loose at the time.
[14:30] <persia> davidm: Do you have a previously unused board on which dd may be run?
[14:30] <ogra> note that they are built completely differently from our packages
[14:30] <mpoirier> Yes, I know.
[14:31] <mpoirier> the point here is the seem to work.
[14:31] <ogra> since u-boot upstream is never compiled natively
[14:31] <mpoirier> find out what is different and you fix the problem.
[14:31] <ogra> and with a completely different toolchain
[14:31] <ogra> well, i'll upgrade to the latest upstream for sure before A3
[14:31] <persia> Alright.  Does anyone have a board with pristine NAND?
[14:31] <ogra> not anymore
[14:31] <mpoirier> I have one.
[14:31] <davidm> persia, sorry was distracted
[14:31] <mpoirier> that is how I got the lead.
[14:32] <davidm> what was your question I'm not understanding the backscrool
[14:32] <persia> mpoirier: So, what's the issue getting the "factory image"?
[14:32] <mpoirier> I need the branch from where they were compiled.
[14:32] <davidm> I have a new Beagle C4 sitting on my desk, right now.
[14:32] <persia> davidm: Looking for a "factory image" from a beagleboard NAND to troubleshoot bug #591941
[14:32] <davidm> mpoirier, you have an email into TI for the sources correct?
[14:33] <mpoirier> Yes, that is correct.
[14:33] <persia> mpoirier: Ah, that's trickier :)
[14:33]  * ogra recommends to just ask in #beagle
[14:33] <mpoirier> I did.
[14:33] <ogra> they definately know where the source is
[14:33] <mpoirier> no one know.
[14:33] <persia> ugh.
[14:33] <ogra> koen or sarkoman surely do
[14:33] <davidm> OK, mpoirier if using the TI loaders the bug is gone, if using ours the bug is present in the same kernel is that correct?
[14:34] <ogra> since sarkoman maintains all omap3 branches
[14:34] <mpoirier> correct.
[14:34] <mpoirier> I did not talk to sarkoman.
[14:34] <ogra> ah, he is the author mentioned in our package
[14:34] <mpoirier> keon suggested I talk to mhasim, something I did.
[14:34] <ogra> just mail him
[14:34]  * ogra doesnt know mhasim
[14:35] <persia> [ACTION] mpoirer to coordinate with sarkoman or TI internal sources to get branch with "factory" bootloader source.
[14:35]  * cooloney hands up about the robclark's patches
[14:35] <MootBot> ACTION received:  mpoirer to coordinate with sarkoman or TI internal sources to get branch with "factory" bootloader source.
[14:35] <mpoirier> koen claims he built the u-boot image that is found in nand.
[14:35] <ogra> i'd claim the same
[14:35] <ogra> apart from the above i mentioned
[14:35] <ogra> we dont build cross ...
[14:36] <ogra> but effectively all new boards should be shipped with the latest upstream u-boot
[14:36] <ogra> so whatever was recent at the time the board shipped
[14:36] <persia> Right, so we have an action.  Maybe it's worded wrong, but let's move on, and complete in spirit if not by letter.
[14:36] <persia> mpoirier: Anything else?
[14:36] <ogra> if TI adds special patches they tag the version as -dirty
[14:36] <mpoirier> ..
[14:36] <ogra> else its plain upstream
[14:37] <persia> lag: Your turn
[14:37] <ogra> lag, great blogpost :)
[14:38] <cooloney> just a quick interrupt,
[14:38] <cooloney> robclark's patches are not in the release from TI this month
[14:38] <ogra> can you add them to our branch ?
[14:38] <ogra> so they get some testing in advance
[14:38] <persia> cooloney: OK.  I'll actio  you with that after lag
[14:38] <cooloney> ogra: yeah, i already discuss with sebjan
[14:39] <cooloney> he will ping robclark and sync with me
[14:39]  * ogra thinks lag lags
[14:39] <lag> :)
[14:39] <cooloney> and let rob to send out patches for merge
[14:39] <ogra> perfect
[14:39] <lag> What would you like to know?
[14:39] <cooloney> before sebjan leave for vacation
[14:39] <cooloney> i'm done
[14:39] <ogra> lag, any intresting news about you and your work
[14:39] <lag> * Marvel (mvl-dove)
[14:39] <lag>     * Nothing new this week
[14:39] <lag>  * Freescale (fsl-imx51)
[14:39] <lag>     *  Tested security update kernel from smb; however, after installing on 2 Babbage 2.5 boards, both boards are believed to be broken
[14:39] <lag>        * Tobin Davis will retry the kernel again at his home
[14:39] <cooloney> lag: can you read your blog on voice. for us, that's awesome
[14:40] <lag>  * Texas Instruments (ti-omap)
[14:40] <lag>    * REBASE   : ti-omap4 branch is now at 902.6
[14:40] <lag>    * PATCH    : Patches sent to kernel-team and upstream to fix OTG usb issue on OMAP3 in Lucid and Maverick
[14:40] <lag>    * PATCH    : ti-omap4 patches received from TI (~220 of them) - cooloney is fighting his way through them
[14:40] <lag>    * PATCH    : B592295 SYNC_LOST_DIGIT - TI have released a patch for review - awaiting feedback
[14:40] <lag>    * PATCH    : B608095 Sent patches to make USB and Ethernet work on the Beagleboard XM
[14:40] <lag>    * PATCH    : B605832 LG monitor behaving incorrectly - TI have released a patch for review - awaiting feedback
[14:40] <lag>    - ON GOING : B477106 once again made contact with fixer - estimated time until fix 2-3 weeks
[14:40] <lag>    * ON GOING : B591941 work has resumed - initialization in u-boot/xloader is now being looked at
[14:40] <lag>    * ON GOING : B605488 waiting for the daily build to succeed before progressing - last built 20/07/10
[14:40] <lag>    * FIXED    : B601226 Kconfig system no longer allows the module to be built on OMAP devices
[14:40] <lag>    * WONT FIX : B563650 abandoned and won't be looked at until someone is able to reproduce
[14:40] <lag>    * MISC     : Gumstix investigation: Lucid (!display + USB) Maverick (display + !USB)
[14:40] <lag>    * MISC     : Igepv2 board we acquired doesn't seem to hook up with the SD card
[14:40] <lag>    * MISC     : Mobile team is working on a cmd line installer, allowing for headless install
[14:40] <lag> Open out your clients everyone :)
[14:40] <lag> Which blog?
[14:40] <lag> Both or just the latter?
[14:40] <ogra> cooloney, you mean as ogg so we get the aussie accent ?
[14:40]  * lag slaps ogra
[14:41] <ogra> *grin*
[14:41] <lag> ..#
[14:41] <lag> ..
[14:42] <persia> Right then: no questions.
[14:42] <ogra> is aynone looking into the iegp2 issue ?
[14:42]  * persia retracts
[14:42] <lag> Which issue?
[14:42] <lag> The SD card one?
[14:42] <ogra> in case linaro wants to use them
[14:42] <mpoirier> amitk has the board with him
[14:42] <ogra> yeah
[14:42] <lag> Speak to mpoirier
[14:42] <ogra> ah, k
[14:42] <cooloney> mpoirier: i think you make it works
[14:43] <mpoirier> nop, sd card wouldn't work at all, even with the kernel you find on their web site.
[14:43] <ogra> i know GrueMaster had the gumstix kind of working
[14:43] <GrueMaster> Should we put resources into the gumstix issue?  It was indicated at the sprint that these boards were not going to be production.
[14:43] <mpoirier> yes, lucid on gumstix worked but no display.
[14:43] <ogra> and i think including usb and display
[14:43] <lag> * MISC     : Gumstix investigation: Lucid (!display + USB) Maverick (display + !USB)
[14:44] <GrueMaster> That's the result I had working with ogra's gumstix.
[14:44] <ogra> lag, right, thats what i was commenting on
[14:44] <ogra> GrueMaster, you didnt have USB ?
[14:44] <GrueMaster> Although I don't know that usb worked on lucid.
[14:44] <GrueMaster> Not on maverick.
[14:44]  * ogra thought you clicked around in oem-config
[14:44] <ogra> k
[14:44] <ogra> my bad then
[14:44] <GrueMaster> No, I had no response in oem-config.
[14:44] <davidm> GrueMaster, the stix's will be out by Maverick releases, would be nice if it works but not critical
[14:45] <ogra> davidm, these sticks `
[14:45] <ogra> ?
[14:45] <davidm> Gumstix
[14:45] <ogra> i though they were non production stuff
[14:45] <GrueMaster> Ok.  Chris had indicated otherwise.  Maybe I mistook him.
[14:45]  * ogra thought that too
[14:45] <davidm> It's nice to have not hard required
[14:45] <ogra> i thought he said these specific ones will never get produced
[14:46] <persia> That's the sort of thing improved-subarch-detection is intended to solve
[14:46] <GrueMaster> My interpretation was that they were moving up to omap4.
[14:46] <ogra> persia, fixing kernel probs ?
[14:46] <davidm> Perhaps I was not in the room for that conversation
[14:47] <persia> ogra: avoiding board-specific solutions.
[14:47] <persia> Anyway, running out of time, so moving faster.
[14:47] <persia> [ACTION] cooloney to work with robclark and sebjan to merge HDMI patches
[14:47] <MootBot> ACTION received:  cooloney to work with robclark and sebjan to merge HDMI patches
[14:47] <persia> [TOPIC] QA status
[14:47] <MootBot> New Topic:  QA status
[14:47]  * cooloney nods to persia 
[14:48] <ogra> we should probably shuffle the topics on the agenda
[14:48] <persia> OK.  Maybe not.  We'Ll come back if anyone wants it in the AOB section (if there is time)
[14:48] <ogra> Qa is often blocked by non building images
[14:49] <persia> true.
[14:49] <GrueMaster> Nothing new from QA.
[14:49] <ogra> so images should before QA imho
[14:49] <persia> [TOPIC] ARM Porting / Build issues.
[14:49] <MootBot> New Topic:  ARM Porting / Build issues.
[14:50] <ogra> dyfet, ?
[14:50] <dyfet> Ah...
[14:50] <dyfet> Yes...the only additional ftbfs I worked on last week was ido
[14:50] <dyfet> openjdk was dropped for me
[14:51] <dyfet> most of the rest are blocked on qt
[14:51] <ogra> how about firefox and xulrunner
[14:51] <persia> I thought Qt got solved Friday or Saturday
[14:51] <dyfet> it may have
[14:51] <ogra> mutter seems to fail too
[14:52] <ogra> QT was solved thursady already, but a new upload was building at that time
[14:52] <ogra> though it should be possible to fix a good bunch of the issues witth give backs
[14:52] <dyfet> I can look at ftb's post qt later today
[14:53] <persia> Many may just need to be retried.
[14:53] <persia> OK, runnng out of time.
[14:53] <persia> [TOPIC] Image status
[14:53] <MootBot> New Topic:  Image status
[14:53] <ogra> does anyone know the order ?
[14:53] <ogra> images fail to build due to an unfound error in the loop mount code
[14:53] <persia> DO we have a bug number?
[14:54] <ogra> i'm still researching (doing my 8th local testbuild today)
[14:54] <persia> Please file an (incomplete) bug for tracking.
[14:54] <persia> [TOPIC] Rootstock
[14:54] <MootBot> New Topic:  Rootstock
[14:54] <persia> rsalveti: You really want this as a standing item?
[14:55] <rsalveti> persia: it's just because I fixed a lot of stuff
[14:55] <rsalveti> and doesn't belong on the other topics
[14:55] <rsalveti> so :-)
[14:55] <persia> Well, make your announcements quickly :)
[14:55] <rsalveti> more fixes on the repo, planned release for this week
[14:55] <rsalveti> trying to move to user space emulation for root
[14:56] <rsalveti> but also got stuck on the *hang*
[14:56] <rsalveti> and noticed one other qemu bug went back to maverick
[14:56] <rsalveti> the unsupported syscall: 335 that michael fixed on lucid
[14:56] <rsalveti> still debugging and going to check why this bug returned for maverick
[14:56] <persia> Was something dropped on merge?
[14:57] <rsalveti> probably
[14:57] <rsalveti> persia: move on
[14:57] <persia> Great!  It sounds in muvh better shape.
[14:57] <persia> Anyone have anything else that can be discussed in two minutes?
[14:57] <ogra> i'm holding a tutorial hour tomorrow http://www.omappedia.com/wiki/Tutorial_Hour_Topics
[14:58] <ogra> just FYI
[14:58] <persia> [LINK] http://www.omappedia.com/wiki/Tutorial_Hour_Topics
[14:58] <MootBot> LINK received:  http://www.omappedia.com/wiki/Tutorial_Hour_Topics
[14:58] <ogra> (no idea what i'll talk about yet :) )
[14:58] <persia> ogra: Nice to have something in AOB.  Thanks!
[14:59] <persia> OK.  That's it.  Thanks for your attendance.
[14:59] <persia> #endmeeting
[14:59] <MootBot> Meeting finished at 08:59.
[14:59] <ogra> time well filled :)
[14:59] <pitti> hello
[15:00] <sabdfl> hey pitti
[15:00] <pitti> hey Mark, how are you?
[15:00] <kees> \o
[15:01] <Keybuk> Hi
[15:04] <pitti> so, just one topic today?
[15:05]  * pitti pinged mdz
[15:05] <pitti> cjwatson: hello Colin; here?
[15:06] <pitti> ah, no, he said he was on vac
[15:12] <kees> so, meeting?
[15:12] <pitti> mdz doesn't answer, and he's got the only topic
[15:12] <kees> hrm
[15:14] <Keybuk> let's just defer that to the next one then
[15:14] <Keybuk> I think people are either at Debcamp or on holiday
[15:14] <pitti> *nod*
[15:14] <kees> yup
[15:32] <mdz> sorry I'm late
[15:33] <mdz> looks like we canceled
[15:42] <sabdfl> looks like
[17:59]  * manjo o/
[17:59] <lag> o/
[17:59]  * smb \c
[18:00] <cking__> o/
[18:00] <mpoirier> o/
[18:00] <kamal> o/
[18:00] <cnd> |o|
[18:00] <jjohansen> \o
[18:00]  * ogasawara waves
[18:01] <bjf> #startmeeting
[18:01] <MootBot> Meeting started at 12:01. The chair is bjf.
[18:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <MootBot> LINK received:  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:02] <bjf> [TOPIC] ARM Status (lag)
[18:02] <MootBot> New Topic:  ARM Status (lag)
[18:02] <lag>  * Marvel (mvl-dove)
[18:02] <lag>     * Nothing new this week
[18:02] <lag>  * Freescale (fsl-imx51)
[18:02] <lag>     *  Tested security update kernel from smb; however, after installing on 2 Babbage 2.5 boards, both boards are believed to be broken
[18:02] <lag>        * Tobin Davis will retry the kernel again at his home
[18:02] <lag>  * Texas Instruments (ti-omap)
[18:02] <lag>    * REBASE   : ti-omap4 branch is now at 902.6
[18:02] <lag>    * PATCH    : Patches sent to kernel-team and upstream to fix OTG usb issue on OMAP3 in Lucid and Maverick
[18:02] <lag>    * PATCH    : ti-omap4 patches received from TI (~220 of them) - cooloney is fighting his way through them
[18:02] <lag>    * PATCH    : B592295 SYNC_LOST_DIGIT - TI have released a patch for review - awaiting feedback
[18:02] <lag>    * PATCH    : B608095 Sent patches to make USB and Ethernet work on the Beagleboard XM
[18:02] <lag>    * PATCH    : B605832 LG monitor behaving incorrectly - TI have released a patch for review - awaiting feedback
[18:02] <lag>    * ON GOING : B477106 once again made contact with fixer - estimated time until fix 2-3 weeks
[18:02] <lag>    * ON GOING : B591941 work has resumed - initialization in u-boot/xloader is now being looked at
[18:02] <lag>    * ON GOING : B605488 waiting for the daily build to succeed before progressing - last built 20/07/10
[18:02] <lag>    * FIXED    : B601226 Kconfig system no longer allows the module to be built on OMAP devices
[18:02] <lag>    * WONT FIX : B563650 abandoned and won't be looked at until someone is able to reproduce
[18:02] <lag>    * MISC     : Gumstix investigation: Lucid (!display + USB) Maverick (display + !USB)
[18:02] <lag>    * MISC     : Igepv2 board we acquired doesn't seem to hook up with the SD card
[18:02] <lag>    * MISC     : Mobile team is working on a cmd line installer, allowing for headless install
[18:02] <lag> ..
[18:02] <smb> lag, poked tobin today but not have a feedback yet.
[18:02] <smb> ..
[18:03] <lag> Regarding which issue?
[18:03] <lag> Oh, okay
[18:03] <lag> He's worried that it will blow up his board
[18:03] <lag> I've put him on to cooloney
[18:03] <lag> ..
[18:04] <smb> Somehow I cannot believe a kernel would o that. But lets see the outcome
[18:04] <smb> ..
[18:04] <lag> My thoughts exactly
[18:04] <lag> ..
[18:04] <bjf> i just pinged him, "GrueMaster> bjf: I am not going to be able to test it until we hear back from Freescale as to how it broke two other boards.  I don't want to kill my system."
[18:04] <lag> Bingo
[18:04] <bjf> [TOPIC] Release Metrics: (JFo)
[18:04] <MootBot> New Topic:  Release Metrics: (JFo)
[18:05] <bjf> Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)
[18:05] <bjf> Release Meeting Bugs (4 bugs, 9 Blueprints)
[18:05] <bjf> [18:05] <bjf>  * 3 linux kernel bugs (down 1)
[18:05] <bjf>  * 0 linux-fsl-imx51 bugs (no change)
[18:05] <bjf>  * 0 linux-ec2 bugs (no change)
[18:05] <bjf>  * 0 linux-mvl-dove bugs (no change)
[18:05] <bjf>  * 0 linux-ti-omap bugs (down 1)
[18:05] <bjf>  * 1 linux-meta-ti-omap bug (no change)
[18:05] <bjf> [18:05] <bjf>  * 24 linux kernel bugs (up 17)
[18:05] <bjf>  * 2 linux-fsl-imx51 bugs (no change)
[18:05] <bjf>  * 0 linux-ec2 bugs (no change)
[18:05] <bjf>  * 2 linux-mvl-dove bugs (no change)
[18:05] <bjf>  * 2 linux-ti-omap bugs (down 1)
[18:05] <bjf>  * 1 linux-meta-ti-omap bug (no change)
[18:05] <bjf> [18:05] <bjf>  * 16 blueprints (Includes HWE Blueprints)
[18:05] <bjf> [18:05] <bjf>  * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on
[18:05] <bjf>  * Breakdown by status:
[18:05] <bjf>    http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/
[18:06] <bjf> [TOPIC] Blueprint: kernel-maverick-apparmor (jjohansen)
[18:06] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor
[18:06] <MootBot> New Topic:  Blueprint: kernel-maverick-apparmor (jjohansen)
[18:06] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor
[18:06] <jjohansen> Submitted next revision to lkml and issued pull request for Maverick
[18:06] <jjohansen> Includes bug fixes for Bug #599450, Bug #581525.
[18:06] <ogasawara> jjohansen: i've got your pull request applied locally.  will push it up once my test builds finish.
[18:07] <jjohansen> Remaining work items are mostly userspace, and will be sorted out in the next week
[18:07] <jjohansen> ogasawara: sounds good
[18:07] <jjohansen> ..
[18:08] <bjf> jjohansen, i assume the lucid fix went to stable upstream?
[18:08] <jjohansen> bjf: the lucid fix hasn't been posted yet
[18:09] <tgardner> bjf, it won't go stable until after its in Linus tree
[18:09] <jjohansen> We changed what we were doing last week after consulting with the security team
[18:09] <bjf> tgardner, i understand, I was just wondering if stable had been cc'd
[18:10] <bjf> [TOPIC] Blueprint: kernel-maverick-misc (apw)
[18:10] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-misc
[18:10] <MootBot> New Topic:  Blueprint: kernel-maverick-misc (apw)
[18:10] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-misc
[18:10] <apw> Nothing new to report.
[18:10] <apw> ..
[18:10] <bjf> [TOPIC] Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)
[18:10] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-new-kernel-on-lts
[18:10] <MootBot> New Topic:  Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)
[18:10] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-new-kernel-on-lts
[18:10] <tgardner> Still tracking Maverick. No known issues.
[18:10] <tgardner> ..
[18:11] <bjf> [TOPIC] Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)
[18:11] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel
[18:11] <MootBot> New Topic:  Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)
[18:11] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel
[18:11] <jjohansen> pulled in recommend XSAVE patch from fedora kernels, and we are building kernels that will only work with pv-grub or modified ami's  Kernels are in testing and currently available at
[18:11] <jjohansen> http://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_amd64.deb
[18:11] <jjohansen> http://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_i386.deb
[18:11] <jjohansen> git://kernel.ubuntu.com/jj/ubuntu-maverick/pvops
[18:11] <jjohansen> have also set up test kernel with pv-on-hvm drivers from amazon compute cloud.  There are two versions, the unmodified drivers, and the v6 version that is being pushed upstream.  I need to spend more time evaluating each but v6 seems the correct one to use atm.
[18:11] <MootBot> LINK received:  http://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_amd64.deb
[18:11] <MootBot> LINK received:  http://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_i386.deb
[18:12] <bjf> [TOPIC] Blueprint: kernel-maverick-config-review (ogasawara)
[18:12] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-config-review
[18:12] <MootBot> New Topic:  Blueprint: kernel-maverick-config-review (ogasawara)
[18:12] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-config-review
[18:13] <ogasawara> kernel-maverick-config-review
[18:13] <ogasawara> Only major change is we've enabled CONFIG_M686 per blueprint:foundations-m-686-compile
[18:13] <ogasawara> ..
[18:14] <bjf> [TOPIC] Blueprint: kernel-maverick-bug-handling (JFo)
[18:14] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:14] <MootBot> New Topic:  Blueprint: kernel-maverick-bug-handling (JFo)
[18:14] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:14] <bjf>  * The date for the Triage summit is set. It will be on the 11th of September between 10AM EST and 2PM EST. The classroom will be for the instructional sessions in order to allow leverage of the Lernid tool. We have decided no
[18:14] <bjf> t to use the kernel channel other than for wiki development. I'll be sending an e-mail on Wednesday to the parties we want to have deliver this training.
[18:14] <bjf> [TOPIC] Blueprint: kernel-maverick-upstart (apw)
[18:14] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-upstart
[18:14] <MootBot> New Topic:  Blueprint: kernel-maverick-upstart (apw)
[18:14] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-upstart
[18:15] <apw> Testing at the Maverick Rally show threw up a bug in the the readahead tracking patches.  This was resolved and we now have a near final patch set.  This will be pushed to kernel-team list this week for review.
[18:15] <apw> ..
[18:15] <bjf> [TOPIC] Blueprint: kernel-maverick-bios-test-automation (cking)
[18:15] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:15] <MootBot> New Topic:  Blueprint: kernel-maverick-bios-test-automation (cking)
[18:15] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:15] <cking1> Recent changes since last meeting:
[18:15] <cking1>   automate fwts ISO build (for USB keys)
[18:15] <cking1>   check msr registers for nx bit, check nx bit across all CPUs
[18:15] <cking1>   fix typos in man page
[18:15] <cking1>   --batch-experimental, --interactive-experimental options
[18:15] <cking1>   --show-tests reports tests based on --interactive, --batch flags
[18:15] <cking1>   virt: more understandable results output
[18:15] <cking1>   mcfg: improved test failure explanation
[18:16] <cking1>   battery: more thorough, make test interactive
[18:16] <cking1>   s3: add variable delay between each S3 iteration
[18:16] <cking1>   investigate 2TB BIOS disk limits
[18:16] <cking1> ..
[18:16] <bjf> [TOPIC] Status: Maverick (ogasawara)
[18:16] <MootBot> New Topic:  Status: Maverick (ogasawara)
[18:16] <ogasawara> The Maverick kernel saw some significant changes last week while at the Platform Rally:
[18:16] <ogasawara>  * We updated to CONFIG_M686 per the foundations-m-686-compile blueprint.
[18:16] <ogasawara>  * The toolchain saw a last minute update which introduced a serious issue where i386 kernels would no longer boot.  Luckily an upstream patch to resolve the issue has been isolated and applied.
[18:16] <ogasawara>  * We rebased the Maverick kernel to the latest 2.6.35-rc6 mainline kernel and uploaded, ie 2.6.35-12.17.
[18:17] <ogasawara> Considering all the changes, please be sure to help test.
[18:17] <ogasawara> Alpha 3 is Thurs Aug 5th which is ~1week away.  Any patches that are to land in the Alpha3 kernel need to be submitted and garnered the appropriate Ack's *before* this Friday (Jul 30).  For those that have already sent patches, I'll be applying them today.
[18:17] <ogasawara> Also, please note we are significantly above the Alpha 3 burn down chart's trend line.  Review your list of work items for Alpha 3 and start closing out tasks asap.  If your work items won't be completed by the milestone, re-target it or mark it POSTPONED.
[18:17] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-3.html
[18:17] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-3
[18:17] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-3.html
[18:17] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-3
[18:17] <ogasawara> ..
[18:18] <bjf> [TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:18] <MootBot> New Topic:  Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:18] <smb> ||                   || Upd./Sec.     || Proposed      || TiP || Verified    ||
[18:18] <smb> || Dapper: Kernel    || 2.6.15-55.84  ||               ||     ||             ||
[18:18] <smb> || Hardy:  Kernel    || 2.6.24-28.71  ||               ||     ||             ||
[18:18] <smb> || Jaunty: Kernel    || 2.6.28-19.61  ||               ||     ||             ||
[18:18] <smb> || Karmic: Kernel    || 2.6.31-22.60  ||               ||     ||             ||
[18:18] <smb> || =       mvl-dove  || 2.6.31-214.28 ||               ||     ||             ||
[18:18] <smb> || =       fsl-imx51 || 2.6.31-112.28 ||               ||     ||             ||
[18:18] <smb> || =       ec2       || 2.6.31-307.15 ||               ||     ||             ||
[18:18] <smb> || Lucid:  Kernel    || 2.6.32-24.38  ||               ||     ||             ||
[18:19] <smb> || =       LBM       || 2.6.32-24.17  ||               ||     ||             ||
[18:19] <smb> || =       mvl-dove  || 2.6.32-207.20 ||               ||     ||             ||
[18:19] <smb> || =       fsl-imx51 || 2.6.31-608.15 ||               ||     ||             ||
[18:19] <smb> || =       ti-omap   || 2.6.33-502.8  ||               ||     ||             ||
[18:19] <smb> || =       ec2       || 2.6.32-308.13 ||               ||     ||             ||
[18:19] <smb> All proposed packages have moved to updates. Awaiting security release anytime
[18:19] <smb> soon. Since there has been some weird testing problems on Lucid fsl-imx51 we
[18:19] <smb> will hold back on them.
[18:19] <smb> ..
[18:20] <tgardner> who really cares about a security issue on ARM? Is anyone actually vulnerable?
[18:20] <smb> tgardner, Could be due to generic issues
[18:20]  * cking1 cares about it on his nexus one ;-)
[18:20] <smb> tgardner, Anyway we were explicitely told to do arm
[18:21] <smb> cking1, I would care but we have no impact there :)
[18:21] <smb> ..
[18:21] <bjf> since this is supposed to be the 10.04.1 kernel, are we slipping that as well?
[18:21] <tgardner> I'm of the opinion that if x86 passes CVe tests then promote it.
[18:22] <smb> bjf, We agreed to upload all other kernels
[18:22] <ogra> tgardner, our buildds might care about security on ARM
[18:22] <smb> bjf, Just keep back the fsl-imx51 on Lucid
[18:22] <ogra> they all run lucid
[18:22] <bjf> smb, ok, that's not what I thought you just said
[18:23] <smb> Ok, sorry. Seems misleadingly written
[18:23] <tgardner> ogra, the exploits are highly unlikely to be available on a buildd.
[18:24] <smb> ..
[18:24] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[18:24] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[18:24] <bjf> Incoming Bugs
[18:24] <bjf> 171 Maverick Bugs (up 112)
[18:24] <bjf> 1099 Lucid Bugs (up 50)
[18:24] <bjf> Current regression stats (broken down by release):
[18:24] <bjf> [18:24] <bjf>   * 96 maverick bugs (up 61)
[18:24] <bjf>   * 221 lucid bugs (down 2: to be converted to regression-release)
[18:24] <bjf> [18:24] <bjf>   * 40 lucid bugs (no change)
[18:24] <bjf>   * 6 karmic bugs (no change)
[18:24] <bjf>   * 4 jaunty bugs (no change)
[18:24] <bjf>   * 1 hardy bug (no change)
[18:24] <bjf> [18:24] <bjf>   * 173 lucid bugs (up 13)
[18:24] <bjf>   * 44 karmic bugs (down 1)
[18:24] <bjf>   * 19 jaunty bugs (no change)
[18:24] <bjf>   * 2 hardy bugs (no change)
[18:24] <bjf> [18:24] <bjf>   * 4 lucid bugs (up 2)
[18:24] <bjf>   * 1 karmic bug (no change)
[18:24] <bjf> !*Please note the large jump in Maverick bugs.
[18:25] <ogasawara> whoa, up 61 regression-potential
[18:26] <tgardner> ogasawara, sounds like we're starting to get some coverage
[18:26] <bjf> wonder how many rc6 will fix
[18:26] <cking1> or introduce
[18:26] <bjf> thanks cking1 for that reality check
[18:27] <ogasawara> heh
[18:27] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[18:27] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[18:27] <bjf> I decided toward the end of last week to postpone the weekly bug day to next week. We will be reviewing
[18:27] <bjf> new bugs that have been erroneously set to new after information has been provided. We will also urge
[18:27] <bjf> additional commenters to open new bugs for their issues and remove duplicates as we see them. The Kernel
[18:27] <bjf> Team Bug day will once again be on half a day Friday and half a day Monday. please do what you can on
[18:27] <bjf> our top50 list.
[18:28] <bjf> ..
[18:28] <bjf> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:28] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:28] <apw> o/ o/
[18:28] <bjf> go apw
[18:28] <apw> just a heads up that usb-creator on lucid cannot make bootable images of maverick
[18:29] <apw> see bug #608382 for a work-around
[18:29] <apw> also
[18:29] <apw> we mentioned last week getting the stauses reported here pushed into the whiteboards of blueprints
[18:29] <apw> as a 'status:' section
[18:29] <apw> ..
[18:29]  * ogasawara would greatly appreciate that
[18:30] <bjf> anyone else?
[18:31] <bjf> going
[18:31] <manjo> ..
[18:31] <bjf> going
[18:31] <tgardner> apw, we should point folks at the grub/ISO page for building Maverick images
[18:31] <apw> ack
[18:31] <tgardner> ..
[18:32] <bjf> #endmeeting
[18:32] <MootBot> Meeting finished at 12:32.
[18:32] <kamal> thanks bjf
[18:32] <apw> wooo 30 mins
[18:32] <smb> thx bjf
[18:56] <zul> gday
[18:56] <sommer> yo, o//
[18:57] <ttx> ~o~
[18:57] <smoser> ~o~
[18:57] <jiboumans> o// \\o \o/
[18:57] <ttx> All 3 Joses are with us
[18:58] <jiboumans> i can feel the excitement
[18:59] <mathiaz> o/
[18:59] <hggdh> ~o~
[18:59] <jjohansen> \o
[18:59] <Daviey> o/
[19:00] <hggdh> ~ô~ (swimming with a cap)
[19:00] <hallyn> so hygenic
[19:00]  * jiboumans waits for kirkland in the cloud
[19:01] <smoser> remember when people did things not "in the cloud" ? that was so lame.
[19:01] <hallyn> honestly
[19:01] <jiboumans> hell, my irc runs in the cloud
[19:01] <ttx> to the cloud, and beyound !
[19:02] <ttx> beyond, even
[19:02] <jiboumans> i even fly home in the cloud
[19:02] <Daviey> My irc seems to be running in fog.
[19:02] <kirkland> i/
[19:02] <hggdh> heh
[19:03]  * kirkland has been waiting for the coffee to brew ... it took a *really* long time ... it wasn't plugged in
[19:03] <ttx> kirkland: you might want to start up the meeting.
[19:04] <kirkland> doh
[19:04] <kirkland> [START-MEETING]
[19:04] <kirkland> #startmeeting
[19:04] <MootBot> Meeting started at 13:04. The chair is kirkland.
[19:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:04] <kirkland> howdy folks, i seem to have forgotten that I'm chairing
[19:05] <jiboumans> kirkland: rest assured, we're here to remind you ;)
[19:05]  * kirkland grabs stuff
[19:05] <jiboumans> [TOPIC] Review ACTION points from previous meeting
[19:05] <jiboumans> hggdh to discuss the outcome of server-maverick-qa-workflow in ServerMeeting at some point in the future
[19:05]  * jiboumans proxies while kirkland loads
[19:06]  * hggdh fixes on the "some point in the future"
[19:06]  * kirkland has it now
[19:06] <jiboumans> hggdh: postponed until the beta cycle right?
[19:06] <hggdh> jiboumans: I think this is a good idea
[19:07] <kirkland> hggdh: anything more on that?
[19:07] <hggdh> on qa-workflow no, pretty much up-to-date except for 3 postponed items
[19:07] <kirkland> hggdh: k, thanks
[19:07] <kirkland> * sommer to check on getting some cloud-init / cloud-config doc. smoser should be available to help
[19:07] <kirkland> sommer: any progress?
[19:08] <sommer> added a "first boot" section with information from smoser's march blog post
[19:08] <kirkland> sommer: link?
[19:08] <sommer> just added it this morning, so should be available on doc.u.c tomorrow
[19:08] <smoser> sommer, https://help.ubuntu.com/community/CloudInit also
[19:08] <kirkland> #link https://help.ubuntu.com/community/CloudInit
[19:08] <jiboumans> cloud-init++ # totally awesome
[19:09] <kirkland> [LINK]  https://help.ubuntu.com/community/CloudInit
[19:09] <MootBot> LINK received:   https://help.ubuntu.com/community/CloudInit
[19:09] <sommer> smoser: I'll look through that... I used http://ubuntu-smoser.blogspot.com/2010/03/introducing-cloud-inits-cloud-config.html
[19:09] <kirkland> sommer: cool, any action left on this to hold over for next week?
[19:10] <smoser> call it done.
[19:10] <kirkland> [LINK] http://ubuntu-smoser.blogspot.com/2010/03/introducing-cloud-inits-cloud-config.html
[19:10] <MootBot> LINK received:  http://ubuntu-smoser.blogspot.com/2010/03/introducing-cloud-inits-cloud-config.html
[19:10] <sommer> if someone could review the section that'd be awesome
[19:10] <kirkland> smoser: that's you, right?
[19:10] <smoser> sure.
[19:10] <kirkland> [ACTION] smoser to review https://help.ubuntu.com/community/CloudInit
[19:10] <MootBot> ACTION received:  smoser to review https://help.ubuntu.com/community/CloudInit
[19:11] <kirkland>  * SpamapS to send mail to -devel to get ruby community position on ruby gems in ubuntu
[19:11] <kirkland> spamaps does not appear to be here
[19:11] <smoser> well, i wrote that link. so i'm assuming its good.  sommer will provide me with where to look for his doc.
[19:11] <kirkland> jiboumans: is spamaps on holiday today?
[19:11] <sommer> for the record: http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html
[19:12] <jiboumans> kirkland: spamaps is hacking on code
  * SpamapS to send mail to -devel to get ruby community position on ruby gems in ubuntu
[19:12] <jiboumans> he's probably too distracted by the shinies
[19:12] <kirkland> SpamapS: welcome ;-)
[19:12] <kirkland> jiboumans: lucky :-)
[19:12] <SpamapS> thanks
[19:12]  * SpamapS enters with a red face
[19:12] <kirkland> SpamapS: email sent to -devel re: ruby gems?
[19:12]  * ttx does the evil look (again)
[19:12] <jiboumans> if you're late you should totally bring cookies
[19:13] <kirkland> SpamapS: me and you both, kid ;-)  (/me was discombobulated today too)
[19:13] <SpamapS> I did not, because we didn't come to a consensus on the position to take, and are trying to be delicate.
[19:13] <kirkland> SpamapS: okay .... anything blocking that discussion?
[19:13]  * SpamapS Set-Cookie: happy-ubuntu-server-team=1
[19:13] <jiboumans> spamaps: any chance we will get to consensus, or is this blocking going forward?
[19:13] <kirkland> SpamapS: and who needs to be in that quorum to achieve a consensus?
[19:14] <ScottK> For Ruby Gems, it would be important to talk to the Debian Ruby maintainers too.
[19:15] <SpamapS> I'm not sure where we are in the discussion, nothing is blocking it but the whole thing is still just an uncertain mess IMO
[19:15] <jiboumans> spamaps: so what's the next step?
[19:15] <mathiaz> ScottK: agreed - if we can start the conversation with a  concrete proposal it would be helpful
[19:15] <kirkland> SpamapS: okay -- what consensus do we need to send an email?
[19:15] <mathiaz> I think we should come up with a proposal
[19:15] <SpamapS> mathiaz: we had discussed approaching some people who believe there is an FHS solution that makes everyone happy.. right?
[19:15] <mathiaz> SpamapS: yeah - that's one option
[19:16] <mathiaz> I'd start by stating (again) the problem
[19:16] <ScottK> I want to make sure we don't have a repeat of what happened last time.
[19:16] <SpamapS> I believe the next step is proposing a solution that meets the FHS standards and leaves binaries in users' default path
[19:16] <mathiaz> SpamapS: yes
[19:16] <SpamapS> To the debian rubygems maintainers.. and upon rejection, consider carrying a delta in universe.
[19:16] <SpamapS> err
[19:16] <SpamapS> that sounds wrong
[19:16] <SpamapS> IF it is rejected
[19:17] <ScottK> SpamapS: Only if we feel the rejection is unsound.
[19:17] <SpamapS> so next action is to draft a proposal.
[19:17] <ScottK> Last time they rejected something I think they had very good reasons.
[19:17] <SpamapS> The reasons, years ago now, were technically sound, but practically a disaster for rubygems users.
[19:18] <kirkland> okay, so I think we carry over this item to next week
[19:18] <ScottK> The approach was also not handled very collaboratively when it was being developed.
[19:18] <SpamapS> Right, so we want to make a proposal, and get the discussion started.
[19:18] <SpamapS> And get to a decision soon, as users are hurting.
[19:18] <kirkland> [ACTION] SpamapS to work with mathiaz on a proposal, and send proposal to -devel on ruby gems in ubuntu
[19:18] <MootBot> ACTION received:  SpamapS to work with mathiaz on a proposal, and send proposal to -devel on ruby gems in ubuntu
[19:19] <kirkland> okay, that's all from last week's action items
[19:19] <kirkland> [TOPIC] Maverick development (jib)
[19:19] <MootBot> New Topic:  Maverick development (jib)
[19:19] <jiboumans> o/
[19:19] <kirkland> jiboumans: howdy
[19:19] <jiboumans> we're somewhat behind the curve on Alpha3
[19:19] <jiboumans> we knew this going in as we had quite a few extra requests for this cycle
[19:20] <jiboumans> we've been postponing what's reasonable to the Betas and dropping what simply can't be accomodated
[19:20] <jiboumans> only Low priority specs have been affected so far
[19:20] <ttx> Remember: 2 weeks left, 1 week for package updates, 1 week for non-package work
[19:20] <kirkland> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-3.html
[19:20] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-3.html
[19:20] <ttx> so concentrate your package work on this week !
[19:20] <jiboumans> on the upside, we have a few days after Alpha3 but before Feature Freeze so we hope to minimize the culling
[19:20] <jiboumans> .. and what ttx said ;)
[19:21] <jiboumans> at this point, all Low and some work items from Medium specs are at risk
[19:21] <SpamapS> jiboumans: one correction, the monitoring framework was not low priority, but was dropped more to support the UEC monitoring effort than to free up capacity.
[19:21] <jiboumans> SpamapS: good point
[19:21] <jiboumans> during last weeks sprint in Prague we also hashed out the best way to support monitoring & graphing with UEC as the use case
[19:21] <ttx> I'd like to bring attention to the alpha3-milestoned bugs on the team plate:
[19:21] <kirkland> okay, milestoned bugs?
[19:21] <jiboumans> so that spec got re-vamped based on that
[19:22] <jiboumans> ttx, floors all yours
[19:22] <ttx> Bug 591006 - [MIR] haproxy (clint-fewbar)
[19:22] <ttx> Bug 600174 - axis2c fails to build from source in maverick (kirkland)
[19:22] <ttx> Bug 600984 - redhat-cluster-suite fails to build from source in maverick (RoAkSoAx)
[19:22] <ttx> Bug 600220 - libnet-dns-perl fails to build from source in maverick (ttx)
[19:23] <ttx> Bug 600378 - [needs-packaging] python-libgearman (SpamapS ?)
[19:23] <ttx> Bug 607730 - [needs-packaging] ceph (SpamapS ?)
[19:23] <zul> ill look at the ftbfs
[19:23] <ttx> SpamapS: any reason why those two are targeted to alpha3 ?
[19:23] <ttx> zul: they are already assigned
[19:23] <SpamapS> ttx: because they're attached to Alpha3 work items.
[19:23] <zul> ok then
[19:23] <ttx> SpamapS: still ontrack ?
[19:23] <ttx> I'll nominate them for Maverick then
[19:24] <ttx> Bug 605001 - add grub-legacy-ec2 to uec seed (smoser ?)
[19:24] <SpamapS> ttx: all await sponsorship.
[19:24] <smoser> i think mathiaz was going to do that fo rme.
[19:24] <smoser> for me even
[19:24] <ttx> Anyone expecting trouble on those bugs ?
[19:24]  * Daviey nominates 609992, not that we can do much.
[19:24] <SpamapS> ttx: the gearman package, I'd like to get sponsored into debian. Ceph is actually awaiting an upstream release but will need sponsorship as wel, and the HAproxy MIR was approved but the seed change is pending merge review.
[19:25] <ttx> Daviey: please do not nominate to alpha3 bugs that we cannot do anything about :)
[19:25] <ttx> bug 609992
[19:25] <ttx> Daviey: ack
[19:25] <Daviey> ttx, Well i guess my WI for that could be "chase it"
[19:25] <kirkland> ttx: okay; anything else?
[19:25] <ttx> kirkland: done
[19:25]  * hggdh wishes to nominate one... bug 610265
[19:26] <ttx> hggdh: I'll look into it
[19:26] <hggdh> Eucalyptus 2.0 has landed ;-)
[19:26] <kirkland> hggdh: i agree -- it would be nice to get that fixed by alpha3 ISO testing
[19:26] <Daviey> (\o/)
[19:26]  * kirkland high fives davidm 
[19:26] <ttx> or Daviey
[19:26]  * kirkland high fives Daviey, too!
[19:26] <Daviey> yeah, nice work davidm ! :)
[19:27] <kirkland> okay ....
[19:27]  * mathiaz hugs the whole uec team
[19:27] <jjohansen> hggdh: the fix for 610265 is queued it should hit the kernel today
[19:27] <kirkland> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:27] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:27] <jiboumans> awesome work on getting 2.0 landed
[19:27] <hggdh> jjohansen: great, thank you
[19:27] <kirkland> any question for hggdh ?
[19:27] <jiboumans> hggdh: more a workload question
[19:27] <hggdh> I have some news on euca 2.0
[19:27] <SpamapS> hggdh: are you involved with the security team's unit testing framework that they use for regression testing?
[19:28] <jiboumans> you're tasked pretty heavily for Alpha3.. we moved some qa-workflow to beta
[19:28] <jiboumans> do you reckon it's managable now?
[19:28] <hggdh> SpamapS: yes, I am
[19:28] <hggdh> jiboumans: I think it is. The most critical piece is the euca testing
[19:28] <jiboumans> hggdh: agreed, and i want to make sure you have the time needed for that
[19:28] <SpamapS> hggdh: I'd like to suggest we have a papercuts like push to add more tests to that .. meant to bring it up with you in Prague. Keep it in mind... I'm thinking UDS session.
[19:28] <jiboumans> so let me know if we need to find room elsewhere
[19:29] <hggdh> jiboumans: OK. Right now I started playing with Euca 2.0, and already have 4 new bugs to hug
[19:29] <Daviey> hggdh, you rock.
[19:29] <hggdh> SpamapS: we can chat later on that
[19:30] <kirkland> hggdh: cool -- test rig running Euca2.0 ?
[19:30] <hggdh> of the 4, one is already known here, one causes instance failure to start (~10% cases), one deal with inconsistent output
[19:30] <hggdh> kirkland: yes, images from yestrday
[19:30] <hggdh> bug 610479
[19:30] <kirkland> hggdh: cool
[19:31] <hggdh> and bug 610259
[19:31] <kirkland> okay, hggdh anything else for us?
[19:31] <hggdh> these are not critical, but I think we should get them fixed before beta
[19:31] <kirkland> any other questions for hggdh ?
[19:31] <hggdh> kirkland: I am done
[19:31] <Daviey> The test rig has also popped firewall access through to ppa.launchpad.net, making experimental packages MUCH easier..
[19:31] <kirkland> hggdh: great, thanks;  Daviey -- you're tracking eucalyptus bugs, and will work on these as part of your normal euca-maintenance work, right?
[19:32]  * hggdh hugs Daviey
[19:32] <Daviey> kirkland, that is indeed true!
[19:32] <kirkland> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:32] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:32] <kirkland> jjohansen: howdy
[19:32] <jjohansen> hi
[19:33] <jjohansen> so I have a pv-ops kernel that I have just started trying to test, but I believe will work
[19:33] <zul> yay!
[19:33] <jjohansen> it is currently only setup to work with ebs
[19:33] <jiboumans> jjohansen++ # awesome
[19:33] <kirkland> there are 3 bugs in the meeting agenda ...
[19:33] <jjohansen> if my testing pans out I will issue a call for testing with instructions later today
[19:33] <kirkland> Bug 597387: Maverick EC2 kernel issue
[19:33] <kirkland> Bug 599450: getattr/apparmor breaks several packages
[19:33] <kirkland> Bug 574910: High load averages on EC2 with Lucid while idling
[19:33] <kirkland> atop kernel patch
[19:34] <jjohansen> getattr/apparmor breaks - fix is queued and should be pulled into the kernel today
[19:34] <hallyn> woot
[19:34] <jjohansen> there has been some delay as there has been testing of the new tool chain
[19:35] <ttx> the pvops kernel should fix bug 597387 ?
[19:35] <jjohansen> correct, I hope the kernel I am just starting to test fixes pvops
[19:35] <ttx> smoser told me bug 574910 might be an illusion ?
[19:36] <ttx> just an illusion... illusion...
[19:36] <smoser> its up in the air. but jjohansen knows more.
[19:36] <jjohansen> as for High load averages on Lucid while, I have just kicked off a build of new kernel with a small config change that might help
[19:36] <smoser> that is becoming a metabug
[19:36] <jjohansen> ttx: hrmm, the more I look not just an illusion
[19:36] <smoser> for "me too" like posts of "i have high load on lucid"
[19:36] <jjohansen> though, some of it is
[19:37] <ttx> jjohansen: ok
[19:37] <SpamapS> jjohansen: no fair just replacing /proc/uptime with 'printf("%d %d", rand(9999999),rand(123456789));'
[19:37] <jjohansen> hehe, that might work :)
[19:37] <ttx> I think we reached a conclusion on the atop patchset, and that was -1 ?
[19:38]  * jiboumans sniffs
[19:38] <jiboumans> i really want the per process bandwidth monitoring
[19:38] <jjohansen> hrmm, an impass
[19:38] <smoser> s/uptime/loadavg/
[19:38] <ttx> jiboumans: write a KSLM module for it and submit for mainline ?
[19:39] <jiboumans> jjohansen: i'm equally weary though of carrying a patch that's not likely to be supported
[19:39] <jiboumans> ttx: in my copious free time
[19:39] <jjohansen> the kernel team is very relucant to take atop, and sees no reason to at this time
[19:39] <hallyn> jiboumans: we'll be attending the kslm talk at linuxcon...  maybe that'll lead to something
[19:39] <jiboumans> hallyn: mm, good
[19:39] <jiboumans> jjohansen: perhaps we should change the conversation and ask if there's a way this information could be gathered without such an objectionable patch
[19:40] <kirkland> okay ...
[19:40] <jiboumans> jjohansen: not something for now, but perhaps for next UDS
[19:40] <kirkland> anything else kernel-related?
[19:40] <jjohansen> the networking portion should be mostly available with iftop
[19:40] <jiboumans> i'm happy to table this for maverick
[19:40] <SpamapS> Yes, thats probably the next TODO.. make sure atop authors and KSLM authors understand eachother.
[19:41] <kirkland> thanks jjohansen
[19:41] <jjohansen> sounds good
[19:41] <kirkland> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[19:41] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[19:41] <kirkland> sommer: howdy!
[19:41] <sommer> also got the uec section updated from the wiki docs... should be in http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html tomorrow
[19:42] <sommer> all feedback greatly appreciated :-)
[19:42] <sommer> that's all for this week I think
[19:43] <jiboumans> sommer: saw you did a nice clean up too
[19:43] <ttx> kirkland: someone in UECland could review that ?
[19:43] <jiboumans> thanks for that
[19:43] <sommer> oh ya, no problem
[19:43] <kirkland> jiboumans: sure ...
[19:43] <kirkland> Daviey: can you do that?
[19:44] <Daviey> Hmm.. Not until EoW.
[19:44] <kirkland> Daviey: sure ... by next meeting?
[19:44] <Daviey> Action me!
[19:44] <kirkland> [ACTION] Daviey to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html
[19:44] <MootBot> ACTION received:  Daviey to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html
[19:45] <kirkland> I suppose I can do it too
[19:45] <kirkland> [ACTION] kirkland to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html
[19:45] <MootBot> ACTION received:  kirkland to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html
[19:45] <Daviey> 2 eyes > 1
[19:45] <kim0> 4 eyes you mean
[19:45] <Daviey> kim0, Well spotted.
[19:45] <kirkland> :-)
[19:45] <kim0> hehe
[19:45] <kirkland> sommer: anything else?
[19:45]  * mathiaz Daviey EoW -> End of *World*?
[19:46] <hallyn> yeah, i've got that scheduled for thursday.
[19:46] <sommer> kirkland: think that's it... I'll try to have more updates for next week
[19:46] <SpamapS> Crap thats like 2 years away, I can't wait that long
[19:46] <kirkland> mathiaz: End of the Wig;  Daviey is about to stop wearing a wig
[19:46] <Daviey> dammit.
[19:46] <kirkland> [TOPIC] Weekly SRU review (zul)
[19:46] <MootBot> New Topic:  Weekly SRU review (zul)
[19:46] <SpamapS> Wigs? I thought Daviey was Labour for sure.
[19:47] <zul> well lets see 10.04.1 is around the corner and would appreciate an pending SRUs
[19:47] <ttx> I saw that bug 609290 was already nominated, so I didn't reply to the thread.
[19:47] <zul> also help iso testing for 10.04.1 would be nifty to
[19:47] <jiboumans> +1 on what ttx said
[19:47] <ttx> 10.04.1 -> August 12th
[19:47] <zul> ttx: yeah its supposedly fixed in 2.2.16 but I havent had time to fixe it yet
[19:48] <zul> since 2.2.16 got uploaded about an hour ago ;)
[19:48] <ttx> zul++
[19:48] <ttx> the SRUTracker is a bit empty
[19:48] <zul> but yeah ill look at it and we can probably get it in post 10.04.1
[19:48] <zul> ttx: bug that I have to fix in the SRU tracker...launchpad is sending it bad data
[19:49] <ttx> bad LP.
[19:49] <zul> + plus enhancements to it
[19:49] <mathiaz> zul: could you use Production instead of edge?
[19:49] <ttx> SRUs are kinda frozen in preparation for 10.04.1 anyway
[19:49] <zul> mathiaz: probably
[19:49] <zul> mathiaz: ill take a look at it tonight
[19:49] <ttx> we cleared the ones for 10.04.1 in meetign last week.
[19:50] <ttx> the last one in is mathiaz's openldap
[19:50] <zul> the infinite loop in mysql is one of them as well
[19:50] <ttx> which will need some testing
[19:50] <mathiaz> ttx: sitting in -proposed
[19:50] <ttx> zul: anything else ?
[19:50] <zul> ttx: not from me
[19:51] <zul> ttx: just one more thing since you are going to be on holiday you are going to have to show me what needs to be done for 10.04.1 coordination
[19:51] <kirkland> cool
[19:51] <ttx> I'm not in holiday that week.
[19:52] <zul> i thought you were?
[19:52] <zul> ok never mind then :)
[19:52] <ttx> I'm in holiday on week 16 of the schedule
[19:52] <ttx> The date moved quite a bit
[19:52] <kirkland> okay, moving along ;-)
[19:52] <kirkland> [TOPIC] Server papercuts status (ttx)
[19:52] <MootBot> New Topic:  Server papercuts status (ttx)
[19:52] <ttx> See status at: https://launchpad.net/server-papercuts/+milestone/maverick-alpha-3
[19:52] <ttx> Not in very good shape
[19:52] <ttx> Please take the time of fixing your assigned papercut(s) by the end of the week
[19:53] <kirkland> ttx: ack
[19:53] <ttx> if it takes too much time, it's not really a papercut.
[19:53] <kirkland> [ACTION] entire team to fix your papercuts by end-of-the-week
[19:53] <MootBot> ACTION received:  entire team to fix your papercuts by end-of-the-week
[19:53] <kirkland> [TOPIC] Daily triage backlog (ttx)
[19:53] <MootBot> New Topic:  Daily triage backlog (ttx)
[19:53] <ttx> Quick announcement here as well...
[19:54] <ttx> For some mysterious reason we collectively sucked at triaging last week
[19:54]  * hallyn is guilty
[19:54] <ttx> so there is a backlog to clear, please try to take your share
[19:54] <jiboumans> .oO( czech beer )
[19:54] <ttx> so that we can be back to normal soon
[19:54] <ttx> http://webnumbr.com/ubuntu-server-triage
[19:54] <MootBot> LINK received:  http://webnumbr.com/ubuntu-server-triage
[19:54] <kirkland> good idea, ttx
[19:54] <ttx> at 23 rigth now
[19:54] <SpamapS> Seems like the rate of bugs was high too.
[19:55] <ttx> link shows normal / vs. bad week :)
[19:55] <ttx> we get ~ 6 bugs per day looking at the graph
[19:55] <mathiaz> ttx: *18* now
[19:55] <zul> it was at 28 on monday
[19:55] <ttx> kirkland: that's all :)
[19:55] <jiboumans> while we're on it, anyone with moin clue know how to embed an iframe?
[19:55] <SpamapS> it was at 24 on Saturday and I did a few..
[19:55] <kirkland> ttx: okay, we should all pitch in
[19:55] <jiboumans> google's not been helpful on that front =/
[19:56] <Daviey> i frame!?
[19:56] <kirkland> [TOPIC] Open Discussion
[19:56] <MootBot> New Topic:  Open Discussion
[19:56] <kirkland> jiboumans: now you can ask your iframe question :-)
[19:56] <jiboumans> (imagine it's part of the open discussion)
[19:56] <kim0> I have a quick announcement
[19:56] <jiboumans> krikland: i blame latency
[19:56] <Daviey> everyone welcome kim0 o/
[19:56] <ttx> kim0: you like clouds ?
[19:56] <kirkland> kim0: welcome, btw
[19:56] <kim0> ttx: I do :)
[19:56] <jiboumans> o/ kim0
[19:56] <kim0> Here I go
[19:56] <kim0> Since kirkland had pinged me in the sprint, mentioning that for a server release the first point release is the major one, wanting us to beat some drums around the 10.04.1 release.
[19:56] <Daviey> GO
[19:56] <kim0> Here's what I've done. We're launching an initiative called "Ubuntu Server marks your city" till we find a cooler name.
[19:56] <kim0> Basically, I've written a little django app that displays a world map. We'll be pushing the Ubuntu-Server users to hit that webapp, and for every user hitting, we'll display the Ubuntu logo over his city. Meaning this city has been blessed by Ubuntu server
[19:57] <kim0> The target being, by release day (mostly 15 days) we will have covered all world's major cities (hopefully:)
[19:57] <kim0> I'm should be deploying the app tomorrow over ec2
[19:57] <jiboumans> kim0: your job is cool
[19:57] <kim0> EoA
[19:57] <kim0> jiboumans: tell me about it :)
[19:57] <kirkland> kim0: neat :-)
[19:57] <SpamapS> kim0: brilliant!
[19:57] <Daviey> kim0, Rocking!  Is the source avaliable?
[19:57] <kim0> Daviey: YES
[19:57] <jiboumans> kim0: can you let us know the URL so we can tweet/dent/fb/blog the hell out of it?
[19:57] <mathiaz> IIRC we also mentioned we should update the server team meeting agenda to include a section with the community team
[19:57] <kim0> bzr branch lp:mapuntu
[19:58] <Daviey> kim0, thanks!
[19:58] <SpamapS> mathiaz: ++
[19:58] <kirkland> kim0: that's too cool
[19:58] <kim0> jiboumans: will announce tomorrow in this list
[19:58] <jiboumans> kim0: congratulations, you get your own section in the meeting going forward
[19:58] <kim0> I wanted to add a feature
[19:58] <jiboumans> well done!
[19:58] <SpamapS> oh sorry ubuntu is all about python..    +=1
[19:58] <RoAkSoAx> I also have updates in the HA team: We are back on track working on cluster related stuff. We are targeting to have the cluster in Main for this cycle
[19:58] <jiboumans> spamaps++ # hah
[19:58] <kim0> a div with tweets with ubuntu server scrolling by
[19:58] <kim0> if anyone with enough javascript karma wants to hack on that
[19:58] <Daviey> RoAkSoAx, \o/
[19:58] <kim0> be my guest
[19:58] <ttx> RoAkSoAx: saw the alpha3-milestoned bug assigned to you ?
[19:59]  * ScottK has an issue to discuss.
[19:59] <ttx> redhat-cluster-suite FTBFS
[19:59] <RoAkSoAx> ttx: redhat cluster?
[19:59] <ttx> yep
[19:59] <kirkland> ScottK: please
[19:59] <ScottK> I've been working on the server piece of the Kolab spec.
[19:59] <RoAkSoAx> ttx: yep. I'll request sync, but will FTBFS again till all the other cluster packages are in main (pacemaker, cluster-glue, etc)
[20:00] <ScottK> It turns out that in order to get away from a code copy, Kolab needs a couple of php5 patches.
[20:00] <ttx> RoAkSoAx: will they all be in by alpha3 ?
[20:00] <ScottK> They look ~safe to me as they just add functions and don't change any existing functions, but I'm not the right person to review this.
[20:01] <SpamapS> ScottK: we're going to need some scaffolding to hold up our pile of php5 patches. :)
[20:01] <ScottK> Who would be the best person to review?
[20:01] <zul> ScottK: SpamapS ;)
[20:01]  * jiboumans watches zul throw his buddy under the bus
[20:01]  * SpamapS agrees
[20:01] <RoAkSoAx> ttx: I surely hope so. I'm about to start updating the MIRs, and it will just be a matter of time
[20:01] <zul> jiboumans: i only do the packaging ;)
[20:01] <mathiaz> SpamapS: are there a lot of ubuntu specific patches?
[20:01] <ttx> RoAkSoAx: ok, cool
[20:01] <ScottK> kirkland: Can we have an action for SpamapS and I to reivew Kolab php5 patches and we'll handle it offline.
[20:02] <zul> mathiaz: not for 5.3.3
[20:02] <SpamapS> yeah, zul deals with PHP drudgery.. I'm the weirdo who actually kind of likes php. ;)
[20:02] <mathiaz> SpamapS: otherwise I'd recommend to talk to the Debian maintainer
[20:02] <ScottK> (or whoever is running the meeting, I lost track)
[20:02] <kirkland> [ACTION] SpamapS and ScottK to reivew Kolab php5 patches
[20:02] <MootBot> ACTION received:  SpamapS and ScottK to reivew Kolab php5 patches
[20:02] <ScottK> kirkland: Thanks.
[20:02] <SpamapS> ScottK: whats your timezone?
[20:02] <ScottK> I'm done.
[20:02] <kirkland> okay
[20:02] <kirkland> [TOPIC] Announce next meeting date and time
[20:02] <MootBot> New Topic:  Announce next meeting date and time
[20:02] <kirkland> Tuesday 2010-08-03 at 1800 UTC - #ubuntu-meeting
[20:03] <kirkland> #endmeeting
[20:03] <MootBot> Meeting finished at 14:03.
[20:03] <ScottK> SpamapS: -0400
[20:03] <Daviey> \o/
[20:03] <jiboumans> thanks all
[20:03] <jiboumans> nice chairing kirkland; an hour exact!
[20:03]  * Daviey has pitty for the poor scribe of that meeting!
[20:03] <kirkland> jiboumans: ;-)