/srv/irclogs.ubuntu.com/2010/07/27/#ubuntu-meeting.txt

=== mdeslaur is now known as mdeslaur-afk
=== jjohansen is now known as jj-afk
=== mdz is now known as 92AAAT9W3
=== alsroot is now known as Guest14691
=== jussi is now known as Guest88035
=== v is now known as stalcup
=== jj-afk is now known as jjohansen
huatsmorning08:27
=== Tm_K is now known as Tm_T
=== zyga is now known as zyga-afk
=== oubiwann` is now known as oubiwann
=== mr_pouit is now known as mrpouit
* persia peers about14:01
mpoirierhello ?14:02
* ogra waves14:02
=== Ursinha` is now known as Ursinha
dyfetneeds coffee14:02
czajkowskithere should be a bot in here that announces which meeting is starting14:03
ograczajkowski, arm team :)14:03
persiaczajkowski: Used to be, but google ical is special14:03
czajkowskiogra: thanks14:03
czajkowskiI can go back to idling now14:04
ograyou dont want to know about our arms ?14:04
czajkowskiyou waved, clearly your arm works14:04
ograone at least14:04
persiaIf only that was all it took :)14:04
dyfethe is clearly not disarmed14:04
rsalvetipersia: add a section for rootstock, please14:05
persiaAnyway, our usual chair seems absent.14:05
persia#startmeeting14:05
MootBotMeeting started at 08:05. The chair is persia.14:05
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:05
persiaAgenda is at https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010072714:05
persia[LINK] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010072714:05
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010072714:05
persia(wait for rsalveti to update it before you load the page :) )14:05
persiaActions from the prior meeting is incomplete, but some can be dredged from prior logs, so:14:06
persia[TOPIC] dyfet to work on openjdk FTBFS14:06
MootBotNew Topic:  dyfet to work on openjdk FTBFS14:06
rsalvetipersia: go14:06
ograpersia, dropped14:06
dyfetThat was dropped14:06
persiaOK, then there's a reason it wasn't there :)14:07
persia[TOPIC] md5sums and manifests for daily images (NCommander)14:07
MootBotNew Topic:  md5sums and manifests for daily images (NCommander)14:07
ograthe md5sum stuff is fixed, the manifest file copying isnt14:07
ograi'm taking that over14:07
ogra(so add a new action)14:08
persia[ACTION] ogra to sort manifest files for live images14:08
MootBotACTION received:  ogra to sort manifest files for live images14:08
ogratx14:08
persia[TOPIC] NCommander to unbreak apport retracer14:08
MootBotNew Topic:  NCommander to unbreak apport retracer14:08
ograc/o14:08
persiaI think this still isn't working, unless someone knows otherwise14:08
persiaRIght.14:08
* ogra doesnt14:09
persia[ACTION] NCommander to unbreak apport retracer14:09
MootBotACTION received:  NCommander to unbreak apport retracer14:09
persiaOK.  That's all the actions I see from http://irclogs.ubuntu.com/2010/07/13/#ubuntu-meeting.txt14:09
ograyeah14:09
persia[TOPIC] Workitem tracker14:09
MootBotNew Topic:  Workitem tracker14:09
ogralooks horrid14:09
persia[LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html14:09
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html14:09
persia[LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-3.html14:10
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-maverick-alpha-3.html14:10
persiaIndeed.  Everyone with alpha-3 tasks should go do them tomorrow.14:11
ograrsalveti, we need to make a rootstock release this week to close the spec items14:11
rsalvetiogra: we'll, don't worry14:11
ograpersia, tomorrow ?14:11
persiaOK.  Today for those in less advanced timezones :)14:11
ograpersia, `??14:11
ograwhy is that ?14:11
ograthere is still a week until A314:12
ograbut it would be nice if we got below the trend line for fridays release team meeting14:12
davidmI'm concerned that we are so far behind for A314:12
persiaI 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
ograby either postponing or closing14:12
persiaclosing is better.14:12
ograwell, i'm inclined to postpone lightweight panel14:13
GrueMasterI'm looking at my tasks and I think I am still blocked.14:13
ograwhat i got from dx is far from even becoming a panel14:13
davidmI agree, it does not look good for this cycle14:13
ogranothing i couls write in a week14:13
GrueMasterTesting the panel is one of my tasks.14:13
ograright14:13
davidmogra, can we get by with the old efl launcher?14:14
ograNC|Alaska, is unlikely to work on subarch detection before A3 either14:14
ogradavidm, the panel is *additional* to the launcher14:14
ogradavidm, to replace the gnome panel, which we have to ship anyway for gdm14:14
davidmI misunderstood, I thought it was replacing part of it.14:14
ograi'll just clean up the session and we're back to the lucid setup14:15
davidmOK14:15
davidmI think we have to do that14:15
ograpersia, [ACTION] ogra to re-enable the lucid efl session14:15
davidmdyfet, where are you on the mobile-m-omap-edid-autodetection14:17
ografrom subarch detection: [gruemaster]Test upgrade path [1 day]: TODO14:17
persia[ACTION] ogra to re-enable the lucid efl session14:17
MootBotACTION received:  ogra to re-enable the lucid efl session14:17
dyfetcoordinating the i2c issues with kernel team14:17
ograGrueMaster, i think you can do that already, just dist-upgrade a beagle lucid->maverick14:17
davidmdyfet, when will it close?14:17
ogradyfet, are there bugs filed `14:17
GrueMasterOk.  Will add that to my todo for today.14:17
persiaogra: so, postpone subarch generally?  I thought this was nearly done and critical for broad board support.14:17
ogradyfet, if so, please note them on the blueprint14:18
dyfetokay14:18
ograpersia, no idea for what michael needs it14:18
dyfetand yes there is a bug for this14:18
ograpersia, its an *additional* way of detecting subarches14:18
ograwe're still using the old one anyway14:18
persiaI thought it was a fallback to use SoC-based solutions when the individual board couldn't be identified.14:19
ograpersia, right, but we only support boards we know atm14:19
ografor which we still use cpuinfo14:20
persiaWell, anyway, if it's not ready by Friday, best postpone, as lnding images after that is too tight.14:20
persiayeah, but that's a bug :)14:20
ograwell, one item is a warning message14:20
ograthat he should be able to implement in 1h14:20
ograeven on monday14:20
persiaanyway* anyone have stuff about *other* blueprints?14:21
rsalvetithere is rootstock14:21
ogradyfet, there are a lot of WIs on the EDID spec you could start working on already14:21
rsalvetibut we're planing to do a release this week and close the 2 items14:21
ograrsalveti, just a matter of an upload ...14:21
ograto close the WIs14:21
rsalvetiyep, no more than that14:21
persiawasn't robclark working on a bunch of related stuff?14:22
persia(for EDID)14:22
ogradyfet, 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
ograpersia, rob works on panda14:22
ograthe spec is for omap3 where you dont have edid tdetection in the omapfb driver14:22
dyfetogra: I can do that, I got stuff unpacked and back together here14:22
persiaAh, so yes and no :)14:23
ogradyfet, great14:23
persiaMoving on...14:23
persia[TOPIC] Kernel status14:24
MootBotNew Topic:  Kernel status14:24
persiacooloney: Why don't you go first14:24
cooloneyyeah14:24
cooloneyi just prepared a new omap4 branch for maverick14:24
cooloneyit includes the latest TI release L24.814:25
cooloneyi tested on my board, more stable than before14:25
ograalso robclark's work from pargue ?14:25
ograthere are plenty of HDMI patches that fix lots of monitor issues14:25
cooloneyrobclark helped to figure out the HDMI issue.14:26
ogranot sure he sent them to you already14:26
cooloneybut i think lag helped to test them14:26
rsalvetihe posted a branch, but not sure if it's included on this one14:26
* ogra doubts that14:26
cooloneyogra: no problem, i will check it later14:26
ogracool! oney14:26
persiarsalveti: Could you make sure cooloney has the r14:26
persiabranch url?14:27
* ogra hands cooloney an r14:27
rsalvetihttp://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commits/L24.7_panda-hdmi-patches14:27
MootBotLINK received:  http://gitorious.org/~robclark/pandaboard/robclarks-kernel-omap4/commits/L24.7_panda-hdmi-patches14:27
ograso persia is happy :)14:27
persiaTHanks :)14:27
cooloneythanks man14:27
persiampoirier: ready?14:27
mpoirieryep.14:27
mpoirierhttps://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
mpoirierhttps://bugs.launchpad.net/bugs/b591941 - SDHC card init failure: started looking into u-boot - need to track down default factory images.14:28
mpoirierAlpha3 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:28
persiaaren't factory images available from the beagleboard wiki?14:29
ograwhat do you call "factory" ?14:29
mpoiriernop, not the exact same ones you find in nand when first receiving your board.14:29
persiawhatever was used initially in the factory :)14:29
ograah14:29
mpoirierI need the exact same branch - sd card seems to behave much better with it.14:30
mpoirierprocess was very loose at the time.14:30
persiadavidm: Do you have a previously unused board on which dd may be run?14:30
ogranote that they are built completely differently from our packages14:30
mpoirierYes, I know.14:30
mpoirierthe point here is the seem to work.14:31
ograsince u-boot upstream is never compiled natively14:31
mpoirierfind out what is different and you fix the problem.14:31
ograand with a completely different toolchain14:31
ograwell, i'll upgrade to the latest upstream for sure before A314:31
persiaAlright.  Does anyone have a board with pristine NAND?14:31
ogranot anymore14:31
mpoirierI have one.14:31
davidmpersia, sorry was distracted14:31
mpoirierthat is how I got the lead.14:31
davidmwhat was your question I'm not understanding the backscrool14:32
persiampoirier: So, what's the issue getting the "factory image"?14:32
mpoirierI need the branch from where they were compiled.14:32
davidmI have a new Beagle C4 sitting on my desk, right now.14:32
persiadavidm: Looking for a "factory image" from a beagleboard NAND to troubleshoot bug #59194114:32
ubottuLaunchpad bug 591941 in linux (Ubuntu Maverick) "SDHC card not recognized" [High,In progress] https://launchpad.net/bugs/59194114:32
davidmmpoirier, you have an email into TI for the sources correct?14:32
mpoirierYes, that is correct.14:33
persiampoirier: Ah, that's trickier :)14:33
* ogra recommends to just ask in #beagle14:33
mpoirierI did.14:33
ograthey definately know where the source is14:33
mpoirierno one know.14:33
persiaugh.14:33
ograkoen or sarkoman surely do14:33
davidmOK, 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:33
ograsince sarkoman maintains all omap3 branches14:34
mpoiriercorrect.14:34
mpoirierI did not talk to sarkoman.14:34
ograah, he is the author mentioned in our package14:34
mpoirierkeon suggested I talk to mhasim, something I did.14:34
ograjust mail him14:34
* ogra doesnt know mhasim14:34
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 patches14:35
MootBotACTION received:  mpoirer to coordinate with sarkoman or TI internal sources to get branch with "factory" bootloader source.14:35
mpoirierkoen claims he built the u-boot image that is found in nand.14:35
ograi'd claim the same14:35
ograapart from the above i mentioned14:35
ograwe dont build cross ...14:35
ograbut effectively all new boards should be shipped with the latest upstream u-boot14:36
ograso whatever was recent at the time the board shipped14:36
persiaRight, 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
persiampoirier: Anything else?14:36
ograif TI adds special patches they tag the version as -dirty14:36
mpoirier..14:36
ograelse its plain upstream14:36
persialag: Your turn14:37
ogralag, great blogpost :)14:37
cooloneyjust a quick interrupt,14:38
cooloneyrobclark's patches are not in the release from TI this month14:38
ogracan you add them to our branch ?14:38
ograso they get some testing in advance14:38
persiacooloney: OK.  I'll actio  you with that after lag14:38
cooloneyogra: yeah, i already discuss with sebjan14:38
cooloneyhe will ping robclark and sync with me14:39
* ogra thinks lag lags14:39
lag:)14:39
cooloneyand let rob to send out patches for merge14:39
ograperfect14:39
lagWhat would you like to know?14:39
cooloneybefore sebjan leave for vacation14:39
cooloneyi'm done14:39
ogralag, any intresting news about you and your work14:39
lag* Marvel (mvl-dove)14:39
lag    * Nothing new this week14: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 broken14:39
lag       * Tobin Davis will retry the kernel again at his home14:39
cooloneylag: can you read your blog on voice. for us, that's awesome14:39
lag * Texas Instruments (ti-omap)14:40
lag   * REBASE   : ti-omap4 branch is now at 902.614:40
lag   * PATCH    : Patches sent to kernel-team and upstream to fix OTG usb issue on OMAP3 in Lucid and Maverick14:40
lag   * PATCH    : ti-omap4 patches received from TI (~220 of them) - cooloney is fighting his way through them14:40
lag   * PATCH    : B592295 SYNC_LOST_DIGIT - TI have released a patch for review - awaiting feedback14:40
lag   * PATCH    : B608095 Sent patches to make USB and Ethernet work on the Beagleboard XM14:40
lag   * PATCH    : B605832 LG monitor behaving incorrectly - TI have released a patch for review - awaiting feedback14:40
lag   - ON GOING : B477106 once again made contact with fixer - estimated time until fix 2-3 weeks14:40
lag   * ON GOING : B591941 work has resumed - initialization in u-boot/xloader is now being looked at14:40
lag   * ON GOING : B605488 waiting for the daily build to succeed before progressing - last built 20/07/1014:40
lag   * FIXED    : B601226 Kconfig system no longer allows the module to be built on OMAP devices14:40
lag   * WONT FIX : B563650 abandoned and won't be looked at until someone is able to reproduce14: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 card14:40
lag   * MISC     : Mobile team is working on a cmd line installer, allowing for headless install14:40
lagOpen out your clients everyone :)14:40
lagWhich blog?14:40
lagBoth or just the latter?14:40
ogracooloney, you mean as ogg so we get the aussie accent ?14:40
* lag slaps ogra14:40
ogra*grin*14:41
lag..#14:41
lag..14:41
persiaRight then: no questions.14:42
ograis aynone looking into the iegp2 issue ?14:42
* persia retracts14:42
lagWhich issue?14:42
lagThe SD card one?14:42
ograin case linaro wants to use them14:42
mpoirieramitk has the board with him14:42
ograyeah14:42
lagSpeak to mpoirier14:42
ograah, k14:42
cooloneympoirier: i think you make it works14:42
mpoiriernop, sd card wouldn't work at all, even with the kernel you find on their web site.14:43
ograi know GrueMaster had the gumstix kind of working14:43
GrueMasterShould we put resources into the gumstix issue?  It was indicated at the sprint that these boards were not going to be production.14:43
mpoirieryes, lucid on gumstix worked but no display.14:43
ograand i think including usb and display14:43
lag* MISC     : Gumstix investigation: Lucid (!display + USB) Maverick (display + !USB)14:43
GrueMasterThat's the result I had working with ogra's gumstix.14:44
ogralag, right, thats what i was commenting on14:44
ograGrueMaster, you didnt have USB ?14:44
GrueMasterAlthough I don't know that usb worked on lucid.14:44
GrueMasterNot on maverick.14:44
* ogra thought you clicked around in oem-config14:44
ograk14:44
ogramy bad then14:44
GrueMasterNo, I had no response in oem-config.14:44
davidmGrueMaster, the stix's will be out by Maverick releases, would be nice if it works but not critical14:44
ogradavidm, these sticks `14:45
ogra?14:45
davidmGumstix14:45
ograi though they were non production stuff14:45
GrueMasterOk.  Chris had indicated otherwise.  Maybe I mistook him.14:45
* ogra thought that too14:45
davidmIt's nice to have not hard required14:45
ograi thought he said these specific ones will never get produced14:45
persiaThat's the sort of thing improved-subarch-detection is intended to solve14:46
GrueMasterMy interpretation was that they were moving up to omap4.14:46
ograpersia, fixing kernel probs ?14:46
davidmPerhaps I was not in the room for that conversation14:46
persiaogra: avoiding board-specific solutions.14:47
persiaAnyway, running out of time, so moving faster.14:47
persia[ACTION] cooloney to work with robclark and sebjan to merge HDMI patches14:47
MootBotACTION received:  cooloney to work with robclark and sebjan to merge HDMI patches14:47
persia[TOPIC] QA status14:47
MootBotNew Topic:  QA status14:47
* cooloney nods to persia 14:47
ograwe should probably shuffle the topics on the agenda14:48
persiaOK.  Maybe not.  We'Ll come back if anyone wants it in the AOB section (if there is time)14:48
ograQa is often blocked by non building images14:48
persiatrue.14:49
GrueMasterNothing new from QA.14:49
ograso images should before QA imho14:49
persia[TOPIC] ARM Porting / Build issues.14:49
MootBotNew Topic:  ARM Porting / Build issues.14:49
ogradyfet, ?14:50
dyfetAh...14:50
dyfetYes...the only additional ftbfs I worked on last week was ido14:50
dyfetopenjdk was dropped for me14:50
dyfetmost of the rest are blocked on qt14:51
ograhow about firefox and xulrunner14:51
persiaI thought Qt got solved Friday or Saturday14:51
dyfetit may have14:51
ogramutter seems to fail too14:51
ograQT was solved thursady already, but a new upload was building at that time14:52
ograthough it should be possible to fix a good bunch of the issues witth give backs14:52
dyfetI can look at ftb's post qt later today14:52
persiaMany may just need to be retried.14:53
persiaOK, runnng out of time.14:53
persia[TOPIC] Image status14:53
MootBotNew Topic:  Image status14:53
ogradoes anyone know the order ?14:53
ograimages fail to build due to an unfound error in the loop mount code14:53
persiaDO we have a bug number?14:53
ograi'm still researching (doing my 8th local testbuild today)14:54
persiaPlease file an (incomplete) bug for tracking.14:54
persia[TOPIC] Rootstock14:54
MootBotNew Topic:  Rootstock14:54
persiarsalveti: You really want this as a standing item?14:54
rsalvetipersia: it's just because I fixed a lot of stuff14:55
rsalvetiand doesn't belong on the other topics14:55
rsalvetiso :-)14:55
persiaWell, make your announcements quickly :)14:55
rsalvetimore fixes on the repo, planned release for this week14:55
rsalvetitrying to move to user space emulation for root14:55
rsalvetibut also got stuck on the *hang*14:56
rsalvetiand noticed one other qemu bug went back to maverick14:56
rsalvetithe unsupported syscall: 335 that michael fixed on lucid14:56
rsalvetistill debugging and going to check why this bug returned for maverick14:56
persiaWas something dropped on merge?14:56
rsalvetiprobably14:57
rsalvetipersia: move on14:57
persiaGreat!  It sounds in muvh better shape.14:57
persiaAnyone have anything else that can be discussed in two minutes?14:57
ograi'm holding a tutorial hour tomorrow http://www.omappedia.com/wiki/Tutorial_Hour_Topics14:57
ograjust FYI14:58
persia[LINK] http://www.omappedia.com/wiki/Tutorial_Hour_Topics14:58
MootBotLINK received:  http://www.omappedia.com/wiki/Tutorial_Hour_Topics14:58
ogra(no idea what i'll talk about yet :) )14:58
persiaogra: Nice to have something in AOB.  Thanks!14:58
persiaOK.  That's it.  Thanks for your attendance.14:59
persia#endmeeting14:59
MootBotMeeting finished at 08:59.14:59
ogratime well filled :)14:59
pittihello14:59
sabdflhey pitti15:00
pittihey Mark, how are you?15:00
kees\o15:00
KeybukHi15:01
pittiso, just one topic today?15:04
* pitti pinged mdz15:05
pitticjwatson: hello Colin; here?15:05
pittiah, no, he said he was on vac15:06
keesso, meeting?15:12
pittimdz doesn't answer, and he's got the only topic15:12
keeshrm15:12
Keybuklet's just defer that to the next one then15:14
KeybukI think people are either at Debcamp or on holiday15:14
pitti*nod*15:14
keesyup15:14
=== 92AAAT9W3 is now known as mdz
mdzsorry I'm late15:32
mdzlooks like we canceled15:33
sabdfllooks like15:42
=== Ursinha is now known as Ursinha-lunch
=== Ursinha-lunch is now known as Ursinha
=== jjohansen1 is now known as jjohansen
=== Guest88035 is now known as jussi
=== jussi is now known as Guest14592
=== Guest14592 is now known as jussi01
=== jussi01 is now known as jussi
* manjo o/17:59
lago/17:59
* smb \c17:59
cking__o/18:00
mpoiriero/18:00
kamalo/18:00
=== cking__ is now known as cking1
cnd|o|18:00
jjohansen\o18:00
* ogasawara waves18:00
bjf#startmeeting18:01
MootBotMeeting started at 12:01. The chair is bjf.18:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:01
bjf#18:01
bjf# NOTE: '..' indicates that you are finished with your input.18:01
bjf#18:01
bjf[TOPIC] ARM Status (lag)18:02
MootBotNew Topic:  ARM Status (lag)18:02
lag * Marvel (mvl-dove)18:02
lag    * Nothing new this week18: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 broken18:02
lag       * Tobin Davis will retry the kernel again at his home18:02
lag * Texas Instruments (ti-omap)18:02
lag   * REBASE   : ti-omap4 branch is now at 902.618:02
lag   * PATCH    : Patches sent to kernel-team and upstream to fix OTG usb issue on OMAP3 in Lucid and Maverick18:02
lag   * PATCH    : ti-omap4 patches received from TI (~220 of them) - cooloney is fighting his way through them18:02
lag   * PATCH    : B592295 SYNC_LOST_DIGIT - TI have released a patch for review - awaiting feedback18:02
lag   * PATCH    : B608095 Sent patches to make USB and Ethernet work on the Beagleboard XM18:02
lag   * PATCH    : B605832 LG monitor behaving incorrectly - TI have released a patch for review - awaiting feedback18:02
lag   * ON GOING : B477106 once again made contact with fixer - estimated time until fix 2-3 weeks18:02
lag   * ON GOING : B591941 work has resumed - initialization in u-boot/xloader is now being looked at18:02
lag   * ON GOING : B605488 waiting for the daily build to succeed before progressing - last built 20/07/1018:02
lag   * FIXED    : B601226 Kconfig system no longer allows the module to be built on OMAP devices18:02
lag   * WONT FIX : B563650 abandoned and won't be looked at until someone is able to reproduce18: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 card18:02
lag   * MISC     : Mobile team is working on a cmd line installer, allowing for headless install18:02
lag..18:02
smblag, poked tobin today but not have a feedback yet.18:02
smb..18:02
lagRegarding which issue?18:03
lagOh, okay18:03
lagHe's worried that it will blow up his board18:03
lagI've put him on to cooloney18:03
lag..18:03
smbSomehow I cannot believe a kernel would o that. But lets see the outcome18:04
smb..18:04
lagMy thoughts exactly18:04
lag..18:04
bjfi 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
lagBingo18:04
bjf[TOPIC] Release Metrics: (JFo)18:04
MootBotNew Topic:  Release Metrics: (JFo)18:04
bjfBugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)18:05
bjfRelease Meeting Bugs (4 bugs, 9 Blueprints)18:05
bjf==== Alpha 3 Milestoned Bugs (40 across all packages (down 6)) ====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==== Release Targeted Bugs (127 across all packages (up 25)) ====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=== Milestoned Features ====18:05
bjf * 16 blueprints (Includes HWE Blueprints)18:05
bjf==== Bugs with Patches Attached:125 (up 5) ====18:05
bjf * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on18:05
bjf * Breakdown by status:18:05
bjf   http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/18:05
bjf[TOPIC] Blueprint: kernel-maverick-apparmor (jjohansen)18:06
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor18:06
MootBotNew Topic:  Blueprint: kernel-maverick-apparmor (jjohansen)18:06
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor18:06
=== Ursinha is now known as Ursinha-afk
jjohansenSubmitted next revision to lkml and issued pull request for Maverick18:06
jjohansenIncludes bug fixes for Bug #599450, Bug #581525.18:06
ubottuLaunchpad bug 599450 in linux (Ubuntu Maverick) "[apparmor] getattr handled incorrectly in 2.6.35-6.7" [High,New] https://launchpad.net/bugs/59945018:06
ubottuLaunchpad bug 581525 in apparmor (Ubuntu) "Lucid: system becomes unstable randomly, seems related with apparmor" [Undecided,New] https://launchpad.net/bugs/58152518:06
ogasawarajjohansen: i've got your pull request applied locally.  will push it up once my test builds finish.18:06
=== Ursinha-afk is now known as Ursinha
jjohansenRemaining work items are mostly userspace, and will be sorted out in the next week18:07
jjohansenogasawara: sounds good18:07
jjohansen..18:07
bjfjjohansen, i assume the lucid fix went to stable upstream?18:08
jjohansenbjf: the lucid fix hasn't been posted yet18:08
tgardnerbjf, it won't go stable until after its in Linus tree18:09
jjohansenWe changed what we were doing last week after consulting with the security team18:09
bjftgardner, i understand, I was just wondering if stable had been cc'd18:09
bjf[TOPIC] Blueprint: kernel-maverick-misc (apw)18:10
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-misc18:10
MootBotNew Topic:  Blueprint: kernel-maverick-misc (apw)18:10
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-misc18:10
apwNothing 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-lts18:10
MootBotNew Topic:  Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)18:10
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-new-kernel-on-lts18:10
tgardnerStill tracking Maverick. No known issues.18:10
tgardner..18:10
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-kernel18:11
MootBotNew Topic:  Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)18:11
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel18:11
jjohansenpulled 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 at18:11
jjohansenhttp://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_amd64.deb18:11
jjohansenhttp://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_i386.deb18:11
jjohansengit://kernel.ubuntu.com/jj/ubuntu-maverick/pvops18:11
jjohansenhave 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
MootBotLINK received:  http://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_amd64.deb18:11
MootBotLINK received:  http://kernel.ubuntu.com/~jj/linux-image-2.6.35-12-virtual_2.6.35-12.17~pvops_i386.deb18:11
bjf[TOPIC] Blueprint: kernel-maverick-config-review (ogasawara)18:12
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-config-review18:12
MootBotNew Topic:  Blueprint: kernel-maverick-config-review (ogasawara)18:12
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-config-review18:12
ogasawarakernel-maverick-config-review18:13
ogasawaraOnly major change is we've enabled CONFIG_M686 per blueprint:foundations-m-686-compile18:13
ogasawara..18:13
bjf[TOPIC] Blueprint: kernel-maverick-bug-handling (JFo)18:14
bjf[LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling18:14
MootBotNew Topic:  Blueprint: kernel-maverick-bug-handling (JFo)18:14
MootBotLINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling18: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 no18:14
bjft 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-upstart18:14
MootBotNew Topic:  Blueprint: kernel-maverick-upstart (apw)18:14
MootBotLINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-upstart18:14
apwTesting 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-automation18:15
MootBotNew Topic:  Blueprint: kernel-maverick-bios-test-automation (cking)18:15
MootBotLINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation18:15
cking1Recent 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 CPUs18:15
cking1  fix typos in man page18:15
cking1  --batch-experimental, --interactive-experimental options18:15
cking1  --show-tests reports tests based on --interactive, --batch flags18:15
cking1  virt: more understandable results output18:15
cking1  mcfg: improved test failure explanation18:15
cking1  battery: more thorough, make test interactive18:16
cking1  s3: add variable delay between each S3 iteration18:16
cking1  investigate 2TB BIOS disk limits18:16
cking1..18:16
bjf[TOPIC] Status: Maverick (ogasawara)18:16
MootBotNew Topic:  Status: Maverick (ogasawara)18:16
ogasawaraThe 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:16
ogasawaraConsidering all the changes, please be sure to help test.18:17
ogasawaraAlpha 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
ogasawaraAlso, 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.html18:17
ogasawara[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-318:17
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-maverick-alpha-3.html18:17
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-318:17
ogasawara..18:17
bjf[TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)18:18
MootBotNew 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:18
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
smbAll proposed packages have moved to updates. Awaiting security release anytime18:19
smbsoon. Since there has been some weird testing problems on Lucid fsl-imx51 we18:19
smbwill hold back on them.18:19
smb..18:19
tgardnerwho really cares about a security issue on ARM? Is anyone actually vulnerable?18:20
smbtgardner, Could be due to generic issues18:20
* cking1 cares about it on his nexus one ;-)18:20
smbtgardner, Anyway we were explicitely told to do arm18:20
smbcking1, I would care but we have no impact there :)18:21
smb..18:21
bjfsince this is supposed to be the 10.04.1 kernel, are we slipping that as well?18:21
tgardnerI'm of the opinion that if x86 passes CVe tests then promote it.18:21
smbbjf, We agreed to upload all other kernels18:22
ogratgardner, our buildds might care about security on ARM18:22
smbbjf, Just keep back the fsl-imx51 on Lucid18:22
ograthey all run lucid18:22
bjfsmb, ok, that's not what I thought you just said18:22
smbOk, sorry. Seems misleadingly written18:23
tgardnerogra, the exploits are highly unlikely to be available on a buildd.18:23
smb..18:24
bjf[TOPIC] Incoming Bugs: Regressions (JFo)18:24
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)18:24
bjfIncoming Bugs18:24
bjf171 Maverick Bugs (up 112)18:24
bjf1099 Lucid Bugs (up 50)18:24
bjfCurrent regression stats (broken down by release):18:24
bjf==== regression-potential ====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==== regression-update ====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==== regression-release ====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==== regression-proposed ====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:24
ubottuError: I am only a bot, please don't think I'm intelligent :)18:24
ogasawarawhoa, up 61 regression-potential18:25
=== Ursinha is now known as Ursinha-afk
tgardnerogasawara, sounds like we're starting to get some coverage18:26
bjfwonder how many rc6 will fix18:26
cking1or introduce18:26
=== Ursinha-afk is now known as Ursinha
bjfthanks cking1 for that reality check18:26
ogasawaraheh18:27
bjf[TOPIC] Incoming Bugs: Bug day report (JFo)18:27
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)18:27
bjfI decided toward the end of last week to postpone the weekly bug day to next week. We will be reviewing18:27
bjfnew bugs that have been erroneously set to new after information has been provided. We will also urge18:27
bjfadditional commenters to open new bugs for their issues and remove duplicates as we see them. The Kernel18:27
bjfTeam Bug day will once again be on half a day Friday and half a day Monday. please do what you can on18:27
bjfour top50 list.18:27
bjf..18:28
bjf[TOPIC] Open Discussion or Questions: Anyone have anything?18:28
MootBotNew Topic:  Open Discussion or Questions: Anyone have anything?18:28
apwo/ o/18:28
bjfgo apw18:28
apwjust a heads up that usb-creator on lucid cannot make bootable images of maverick18:28
apwsee bug #608382 for a work-around18:29
ubottuLaunchpad bug 608382 in syslinux (Ubuntu) "USB images of Maverick CDs fail to boot with -- Error: Unkown keyword in configuration file" [Low,Triaged] https://launchpad.net/bugs/60838218:29
apwalso18:29
apwwe mentioned last week getting the stauses reported here pushed into the whiteboards of blueprints18:29
apwas a 'status:' section18:29
apw..18:29
* ogasawara would greatly appreciate that18:29
bjfanyone else?18:30
bjfgoing18:31
manjo..18:31
bjfgoing18:31
tgardnerapw, we should point folks at the grub/ISO page for building Maverick images18:31
apwack18:31
tgardner..18:31
bjf#endmeeting18:32
MootBotMeeting finished at 12:32.18:32
kamalthanks bjf18:32
apwwooo 30 mins18:32
smbthx bjf18:32
zulgday18:56
sommeryo, o//18:56
ttx~o~18:57
smoser~o~18:57
jiboumanso// \\o \o/18:57
ttxAll 3 Joses are with us18:57
jiboumansi can feel the excitement18:58
mathiazo/18:59
hggdh~o~18:59
jjohansen\o18:59
Davieyo/18:59
hggdh~ô~ (swimming with a cap)19:00
hallynso hygenic19:00
* jiboumans waits for kirkland in the cloud19:00
smoserremember when people did things not "in the cloud" ? that was so lame.19:01
hallynhonestly19:01
jiboumanshell, my irc runs in the cloud19:01
ttxto the cloud, and beyound !19:01
ttxbeyond, even19:02
jiboumansi even fly home in the cloud19:02
DavieyMy irc seems to be running in fog.19:02
kirklandi/19:02
hggdhheh19:02
* kirkland has been waiting for the coffee to brew ... it took a *really* long time ... it wasn't plugged in19:03
ttxkirkland: you might want to start up the meeting.19:03
kirklanddoh19:04
kirkland[START-MEETING]19:04
kirkland#startmeeting19:04
MootBotMeeting started at 13:04. The chair is kirkland.19:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:04
kirklandhowdy folks, i seem to have forgotten that I'm chairing19:04
jiboumanskirkland: rest assured, we're here to remind you ;)19:05
* kirkland grabs stuff19:05
jiboumans[TOPIC] Review ACTION points from previous meeting19:05
jiboumanshggdh to discuss the outcome of server-maverick-qa-workflow in ServerMeeting at some point in the future19:05
* jiboumans proxies while kirkland loads19:05
* hggdh fixes on the "some point in the future"19:06
* kirkland has it now19:06
jiboumanshggdh: postponed until the beta cycle right?19:06
hggdhjiboumans: I think this is a good idea19:06
kirklandhggdh: anything more on that?19:07
hggdhon qa-workflow no, pretty much up-to-date except for 3 postponed items19:07
kirklandhggdh: k, thanks19:07
kirkland* sommer to check on getting some cloud-init / cloud-config doc. smoser should be available to help19:07
kirklandsommer: any progress?19:07
sommeradded a "first boot" section with information from smoser's march blog post19:08
kirklandsommer: link?19:08
sommerjust added it this morning, so should be available on doc.u.c tomorrow19:08
smosersommer, https://help.ubuntu.com/community/CloudInit also19:08
kirkland#link https://help.ubuntu.com/community/CloudInit19:08
jiboumanscloud-init++ # totally awesome19:08
kirkland[LINK]  https://help.ubuntu.com/community/CloudInit19:09
MootBotLINK received:   https://help.ubuntu.com/community/CloudInit19:09
sommersmoser: I'll look through that... I used http://ubuntu-smoser.blogspot.com/2010/03/introducing-cloud-inits-cloud-config.html19:09
kirklandsommer: cool, any action left on this to hold over for next week?19:09
smosercall it done.19:10
kirkland[LINK] http://ubuntu-smoser.blogspot.com/2010/03/introducing-cloud-inits-cloud-config.html19:10
MootBotLINK received:  http://ubuntu-smoser.blogspot.com/2010/03/introducing-cloud-inits-cloud-config.html19:10
sommerif someone could review the section that'd be awesome19:10
kirklandsmoser: that's you, right?19:10
smosersure.19:10
kirkland[ACTION] smoser to review https://help.ubuntu.com/community/CloudInit19:10
MootBotACTION received:  smoser to review https://help.ubuntu.com/community/CloudInit19:10
kirkland * SpamapS to send mail to -devel to get ruby community position on ruby gems in ubuntu19:11
kirklandspamaps does not appear to be here19:11
smoserwell, i wrote that link. so i'm assuming its good.  sommer will provide me with where to look for his doc.19:11
kirklandjiboumans: is spamaps on holiday today?19:11
sommerfor the record: http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html19:11
jiboumanskirkland: spamaps is hacking on code19:12
kirkland<kirkland>  * SpamapS to send mail to -devel to get ruby community position on ruby gems in ubuntu19:12
jiboumanshe's probably too distracted by the shinies19:12
kirklandSpamapS: welcome ;-)19:12
kirklandjiboumans: lucky :-)19:12
SpamapSthanks19:12
* SpamapS enters with a red face19:12
kirklandSpamapS: email sent to -devel re: ruby gems?19:12
* ttx does the evil look (again)19:12
jiboumansif you're late you should totally bring cookies19:12
kirklandSpamapS: me and you both, kid ;-)  (/me was discombobulated today too)19:13
SpamapSI did not, because we didn't come to a consensus on the position to take, and are trying to be delicate.19:13
kirklandSpamapS: okay .... anything blocking that discussion?19:13
* SpamapS Set-Cookie: happy-ubuntu-server-team=119:13
jiboumansspamaps: any chance we will get to consensus, or is this blocking going forward?19:13
kirklandSpamapS: and who needs to be in that quorum to achieve a consensus?19:13
ScottKFor Ruby Gems, it would be important to talk to the Debian Ruby maintainers too.19:14
SpamapSI'm not sure where we are in the discussion, nothing is blocking it but the whole thing is still just an uncertain mess IMO19:15
jiboumansspamaps: so what's the next step?19:15
mathiazScottK: agreed - if we can start the conversation with a  concrete proposal it would be helpful19:15
kirklandSpamapS: okay -- what consensus do we need to send an email?19:15
mathiazI think we should come up with a proposal19:15
SpamapSmathiaz: we had discussed approaching some people who believe there is an FHS solution that makes everyone happy.. right?19:15
mathiazSpamapS: yeah - that's one option19:15
mathiazI'd start by stating (again) the problem19:16
ScottKI want to make sure we don't have a repeat of what happened last time.19:16
SpamapSI believe the next step is proposing a solution that meets the FHS standards and leaves binaries in users' default path19:16
mathiazSpamapS: yes19:16
SpamapSTo the debian rubygems maintainers.. and upon rejection, consider carrying a delta in universe.19:16
SpamapSerr19:16
SpamapSthat sounds wrong19:16
SpamapSIF it is rejected19:16
ScottKSpamapS: Only if we feel the rejection is unsound.19:17
SpamapSso next action is to draft a proposal.19:17
ScottKLast time they rejected something I think they had very good reasons.19:17
SpamapSThe reasons, years ago now, were technically sound, but practically a disaster for rubygems users.19:17
kirklandokay, so I think we carry over this item to next week19:18
ScottKThe approach was also not handled very collaboratively when it was being developed.19:18
SpamapSRight, so we want to make a proposal, and get the discussion started.19:18
SpamapSAnd 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 ubuntu19:18
MootBotACTION received:  SpamapS to work with mathiaz on a proposal, and send proposal to -devel on ruby gems in ubuntu19:18
kirklandokay, that's all from last week's action items19:19
kirkland[TOPIC] Maverick development (jib)19:19
MootBotNew Topic:  Maverick development (jib)19:19
jiboumanso/19:19
kirklandjiboumans: howdy19:19
jiboumanswe're somewhat behind the curve on Alpha319:19
jiboumanswe knew this going in as we had quite a few extra requests for this cycle19:19
jiboumanswe've been postponing what's reasonable to the Betas and dropping what simply can't be accomodated19:20
jiboumansonly Low priority specs have been affected so far19:20
ttxRemember: 2 weeks left, 1 week for package updates, 1 week for non-package work19:20
kirkland[LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-3.html19:20
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-3.html19:20
ttxso concentrate your package work on this week !19:20
jiboumanson the upside, we have a few days after Alpha3 but before Feature Freeze so we hope to minimize the culling19:20
jiboumans.. and what ttx said ;)19:20
jiboumansat this point, all Low and some work items from Medium specs are at risk19:21
SpamapSjiboumans: 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
jiboumansSpamapS: good point19:21
jiboumansduring last weeks sprint in Prague we also hashed out the best way to support monitoring & graphing with UEC as the use case19:21
ttxI'd like to bring attention to the alpha3-milestoned bugs on the team plate:19:21
kirklandokay, milestoned bugs?19:21
jiboumansso that spec got re-vamped based on that19:21
jiboumansttx, floors all yours19:22
ttxBug 591006 - [MIR] haproxy (clint-fewbar)19:22
ubottuLaunchpad bug 591006 in haproxy (Ubuntu) "[MIR] haproxy" [Wishlist,In progress] https://launchpad.net/bugs/59100619:22
ttxBug 600174 - axis2c fails to build from source in maverick (kirkland)19:22
ubottuLaunchpad bug 600174 in axis2c (Ubuntu Maverick) "axis2c fails to build from source in maverick" [High,Confirmed] https://launchpad.net/bugs/60017419:22
ttxBug 600984 - redhat-cluster-suite fails to build from source in maverick (RoAkSoAx)19:22
ubottuLaunchpad bug 600984 in redhat-cluster (Ubuntu Maverick) "redhat-cluster-suite fails to build from source in maverick" [High,In progress] https://launchpad.net/bugs/60098419:22
ttxBug 600220 - libnet-dns-perl fails to build from source in maverick (ttx)19:22
ubottuLaunchpad bug 600220 in libnet-dns-perl (Ubuntu Maverick) "libnet-dns-perl fails to build from source in maverick" [High,Confirmed] https://launchpad.net/bugs/60022019:22
ttxBug 600378 - [needs-packaging] python-libgearman (SpamapS ?)19:23
ubottuLaunchpad bug 600378 in Ubuntu "[needs-packaging] python-libgearman" [Wishlist,Confirmed] https://launchpad.net/bugs/60037819:23
ttxBug 607730 - [needs-packaging] ceph (SpamapS ?)19:23
ubottuLaunchpad bug 607730 in Ubuntu "[needs-packaging] ceph" [Wishlist,In progress] https://launchpad.net/bugs/60773019:23
zulill look at the ftbfs19:23
ttxSpamapS: any reason why those two are targeted to alpha3 ?19:23
ttxzul: they are already assigned19:23
SpamapSttx: because they're attached to Alpha3 work items.19:23
zulok then19:23
ttxSpamapS: still ontrack ?19:23
ttxI'll nominate them for Maverick then19:23
ttxBug 605001 - add grub-legacy-ec2 to uec seed (smoser ?)19:24
ubottuLaunchpad bug 605001 in cloud-init (Ubuntu) "add grub-legacy-ec2 to uec seed" [Medium,Triaged] https://launchpad.net/bugs/60500119:24
SpamapSttx: all await sponsorship.19:24
smoseri think mathiaz was going to do that fo rme.19:24
=== bjf is now known as bjf[food]
smoserfor me even19:24
ttxAnyone expecting trouble on those bugs ?19:24
* Daviey nominates 609992, not that we can do much.19:24
SpamapSttx: 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:24
ttxDaviey: please do not nominate to alpha3 bugs that we cannot do anything about :)19:25
ttxbug 60999219:25
ubottuLaunchpad bug 609992 in Ubuntu "[MIR] libcrypt-openssl-x509-perl" [Undecided,New] https://launchpad.net/bugs/60999219:25
ttxDaviey: ack19:25
Davieyttx, Well i guess my WI for that could be "chase it"19:25
kirklandttx: okay; anything else?19:25
ttxkirkland: done19:25
* hggdh wishes to nominate one... bug 61026519:25
ubottuLaunchpad bug 610265 in eucalyptus (Ubuntu) "apparmor: cannot successfully start an Eucalyptus KVM instance" [Undecided,New] https://launchpad.net/bugs/61026519:25
ttxhggdh: I'll look into it19:26
hggdhEucalyptus 2.0 has landed ;-)19:26
kirklandhggdh: i agree -- it would be nice to get that fixed by alpha3 ISO testing19:26
Daviey(\o/)19:26
* kirkland high fives davidm 19:26
ttxor Daviey19:26
* kirkland high fives Daviey, too!19:26
Davieyyeah, nice work davidm ! :)19:26
kirklandokay ....19:27
* mathiaz hugs the whole uec team19:27
jjohansenhggdh: the fix for 610265 is queued it should hit the kernel today19:27
kirkland[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)19:27
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)19:27
jiboumansawesome work on getting 2.0 landed19:27
hggdhjjohansen: great, thank you19:27
kirklandany question for hggdh ?19:27
jiboumanshggdh: more a workload question19:27
hggdhI have some news on euca 2.019:27
SpamapShggdh: are you involved with the security team's unit testing framework that they use for regression testing?19:27
jiboumansyou're tasked pretty heavily for Alpha3.. we moved some qa-workflow to beta19:28
jiboumansdo you reckon it's managable now?19:28
hggdhSpamapS: yes, I am19:28
hggdhjiboumans: I think it is. The most critical piece is the euca testing19:28
jiboumanshggdh: agreed, and i want to make sure you have the time needed for that19:28
SpamapShggdh: 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
jiboumansso let me know if we need to find room elsewhere19:28
hggdhjiboumans: OK. Right now I started playing with Euca 2.0, and already have 4 new bugs to hug19:29
Davieyhggdh, you rock.19:29
hggdhSpamapS: we can chat later on that19:29
kirklandhggdh: cool -- test rig running Euca2.0 ?19:30
hggdhof the 4, one is already known here, one causes instance failure to start (~10% cases), one deal with inconsistent output19:30
hggdhkirkland: yes, images from yestrday19:30
hggdhbug 61047919:30
ubottuLaunchpad bug 610479 in eucalyptus (Ubuntu) "Instance fails to start" [Undecided,New] https://launchpad.net/bugs/61047919:30
kirklandhggdh: cool19:30
hggdhand bug 61025919:31
ubottuLaunchpad bug 610259 in eucalyptus (Ubuntu) "inconsistent output euca_conf and euca-describe-availability-zones" [Undecided,New] https://launchpad.net/bugs/61025919:31
kirklandokay, hggdh anything else for us?19:31
hggdhthese are not critical, but I think we should get them fixed before beta19:31
kirklandany other questions for hggdh ?19:31
hggdhkirkland: I am done19:31
DavieyThe test rig has also popped firewall access through to ppa.launchpad.net, making experimental packages MUCH easier..19:31
kirklandhggdh: great, thanks;  Daviey -- you're tracking eucalyptus bugs, and will work on these as part of your normal euca-maintenance work, right?19:31
* hggdh hugs Daviey19:32
Davieykirkland, that is indeed true!19:32
kirkland[TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)19:32
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)19:32
kirklandjjohansen: howdy19:32
jjohansenhi19:32
jjohansenso I have a pv-ops kernel that I have just started trying to test, but I believe will work19:33
zulyay!19:33
jjohansenit is currently only setup to work with ebs19:33
jiboumansjjohansen++ # awesome19:33
kirklandthere are 3 bugs in the meeting agenda ...19:33
jjohansenif my testing pans out I will issue a call for testing with instructions later today19:33
kirklandBug 597387: Maverick EC2 kernel issue19:33
kirklandBug 599450: getattr/apparmor breaks several packages19:33
kirklandBug 574910: High load averages on EC2 with Lucid while idling19:33
kirklandatop kernel patch19:33
ubottuLaunchpad bug 597387 in Ubuntu Maverick "pv-ops kernel only works in 3 or 4 zones in EC2" [High,Confirmed] https://launchpad.net/bugs/59738719:33
ubottuLaunchpad bug 599450 in linux (Ubuntu Maverick) "[apparmor] getattr handled incorrectly in 2.6.35-6.7" [High,New] https://launchpad.net/bugs/59945019:33
ubottuLaunchpad bug 574910 in linux-ec2 (Ubuntu) "High load averages on Lucid while idling" [Undecided,In progress] https://launchpad.net/bugs/57491019:33
jjohansengetattr/apparmor breaks - fix is queued and should be pulled into the kernel today19:34
hallynwoot19:34
jjohansenthere has been some delay as there has been testing of the new tool chain19:34
ttxthe pvops kernel should fix bug 597387 ?19:35
ubottuLaunchpad bug 597387 in Ubuntu Maverick "pv-ops kernel only works in 3 or 4 zones in EC2" [High,Confirmed] https://launchpad.net/bugs/59738719:35
jjohansencorrect, I hope the kernel I am just starting to test fixes pvops19:35
ttxsmoser told me bug 574910 might be an illusion ?19:35
ubottuLaunchpad bug 574910 in linux-ec2 (Ubuntu) "High load averages on Lucid while idling" [Undecided,In progress] https://launchpad.net/bugs/57491019:36
ttxjust an illusion... illusion...19:36
smoserits up in the air. but jjohansen knows more.19:36
jjohansenas for High load averages on Lucid while, I have just kicked off a build of new kernel with a small config change that might help19:36
smoserthat is becoming a metabug19:36
jjohansenttx: hrmm, the more I look not just an illusion19:36
smoserfor "me too" like posts of "i have high load on lucid"19:36
jjohansenthough, some of it is19:36
=== bjf[food] is now known as bjf
ttxjjohansen: ok19:37
SpamapSjjohansen: no fair just replacing /proc/uptime with 'printf("%d %d", rand(9999999),rand(123456789));'19:37
jjohansenhehe, that might work :)19:37
ttxI think we reached a conclusion on the atop patchset, and that was -1 ?19:37
* jiboumans sniffs19:38
jiboumansi really want the per process bandwidth monitoring19:38
jjohansenhrmm, an impass19:38
smosers/uptime/loadavg/19:38
ttxjiboumans: write a KSLM module for it and submit for mainline ?19:38
jiboumansjjohansen: i'm equally weary though of carrying a patch that's not likely to be supported19:39
jiboumansttx: in my copious free time19:39
jjohansenthe kernel team is very relucant to take atop, and sees no reason to at this time19:39
hallynjiboumans: we'll be attending the kslm talk at linuxcon...  maybe that'll lead to something19:39
jiboumanshallyn: mm, good19:39
jiboumansjjohansen: perhaps we should change the conversation and ask if there's a way this information could be gathered without such an objectionable patch19:39
kirklandokay ...19:40
jiboumansjjohansen: not something for now, but perhaps for next UDS19:40
kirklandanything else kernel-related?19:40
jjohansenthe networking portion should be mostly available with iftop19:40
jiboumansi'm happy to table this for maverick19:40
SpamapSYes, thats probably the next TODO.. make sure atop authors and KSLM authors understand eachother.19:40
kirklandthanks jjohansen19:41
jjohansensounds good19:41
kirkland[TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)19:41
MootBotNew Topic:  Weekly Updates & Questions for the Documentation Team (sommer)19:41
kirklandsommer: howdy!19:41
sommeralso got the uec section updated from the wiki docs... should be in http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html tomorrow19:41
sommerall feedback greatly appreciated :-)19:42
sommerthat's all for this week I think19:42
jiboumanssommer: saw you did a nice clean up too19:43
ttxkirkland: someone in UECland could review that ?19:43
jiboumansthanks for that19:43
sommeroh ya, no problem19:43
kirklandjiboumans: sure ...19:43
kirklandDaviey: can you do that?19:43
DavieyHmm.. Not until EoW.19:44
kirklandDaviey: sure ... by next meeting?19:44
DavieyAction me!19:44
kirkland[ACTION] Daviey to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html19:44
MootBotACTION received:  Daviey to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html19:44
kirklandI suppose I can do it too19:45
kirkland[ACTION] kirkland to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html19:45
MootBotACTION received:  kirkland to review http://doc.ubuntu.com/ubuntu/serverguide/C/uec.html19:45
Daviey2 eyes > 119:45
kim04 eyes you mean19:45
Davieykim0, Well spotted.19:45
kirkland:-)19:45
kim0hehe19:45
kirklandsommer: anything else?19:45
* mathiaz Daviey EoW -> End of *World*?19:45
hallynyeah, i've got that scheduled for thursday.19:46
sommerkirkland: think that's it... I'll try to have more updates for next week19:46
SpamapSCrap thats like 2 years away, I can't wait that long19:46
kirklandmathiaz: End of the Wig;  Daviey is about to stop wearing a wig19:46
Davieydammit.19:46
kirkland[TOPIC] Weekly SRU review (zul)19:46
MootBotNew Topic:  Weekly SRU review (zul)19:46
SpamapSWigs? I thought Daviey was Labour for sure.19:46
zulwell lets see 10.04.1 is around the corner and would appreciate an pending SRUs19:47
ttxI saw that bug 609290 was already nominated, so I didn't reply to the thread.19:47
zulalso help iso testing for 10.04.1 would be nifty to19:47
ubottuLaunchpad bug 609290 in apache2 (Ubuntu Lucid) "overlapping memcpy in ssl_io_input_read" [High,In progress] https://launchpad.net/bugs/60929019:47
jiboumans+1 on what ttx said19:47
ttx10.04.1 -> August 12th19:47
zulttx: yeah its supposedly fixed in 2.2.16 but I havent had time to fixe it yet19:47
zulsince 2.2.16 got uploaded about an hour ago ;)19:48
ttxzul++19:48
ttxthe SRUTracker is a bit empty19:48
zulbut yeah ill look at it and we can probably get it in post 10.04.119:48
zulttx: bug that I have to fix in the SRU tracker...launchpad is sending it bad data19:48
ttxbad LP.19:49
zul+ plus enhancements to it19:49
mathiazzul: could you use Production instead of edge?19:49
ttxSRUs are kinda frozen in preparation for 10.04.1 anyway19:49
zulmathiaz: probably19:49
zulmathiaz: ill take a look at it tonight19:49
ttxwe cleared the ones for 10.04.1 in meetign last week.19:49
ttxthe last one in is mathiaz's openldap19:50
zulthe infinite loop in mysql is one of them as well19:50
ttxwhich will need some testing19:50
mathiazttx: sitting in -proposed19:50
ttxzul: anything else ?19:50
zulttx: not from me19:50
zulttx: 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 coordination19:51
kirklandcool19:51
ttxI'm not in holiday that week.19:51
zuli thought you were?19:52
zulok never mind then :)19:52
ttxI'm in holiday on week 16 of the schedule19:52
ttxThe date moved quite a bit19:52
kirklandokay, moving along ;-)19:52
kirkland[TOPIC] Server papercuts status (ttx)19:52
MootBotNew Topic:  Server papercuts status (ttx)19:52
ttxSee status at: https://launchpad.net/server-papercuts/+milestone/maverick-alpha-319:52
ttxNot in very good shape19:52
ttxPlease take the time of fixing your assigned papercut(s) by the end of the week19:52
kirklandttx: ack19:53
ttxif 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-week19:53
MootBotACTION received:  entire team to fix your papercuts by end-of-the-week19:53
kirkland[TOPIC] Daily triage backlog (ttx)19:53
MootBotNew Topic:  Daily triage backlog (ttx)19:53
ttxQuick announcement here as well...19:53
ttxFor some mysterious reason we collectively sucked at triaging last week19:54
* hallyn is guilty19:54
ttxso there is a backlog to clear, please try to take your share19:54
jiboumans.oO( czech beer )19:54
ttxso that we can be back to normal soon19:54
ttxhttp://webnumbr.com/ubuntu-server-triage19:54
MootBotLINK received:  http://webnumbr.com/ubuntu-server-triage19:54
kirklandgood idea, ttx19:54
ttxat 23 rigth now19:54
SpamapSSeems like the rate of bugs was high too.19:54
ttxlink shows normal / vs. bad week :)19:55
ttxwe get ~ 6 bugs per day looking at the graph19:55
mathiazttx: *18* now19:55
zulit was at 28 on monday19:55
ttxkirkland: that's all :)19:55
jiboumanswhile we're on it, anyone with moin clue know how to embed an iframe?19:55
SpamapSit was at 24 on Saturday and I did a few..19:55
kirklandttx: okay, we should all pitch in19:55
jiboumansgoogle's not been helpful on that front =/19:55
Davieyi frame!?19:56
kirkland[TOPIC] Open Discussion19:56
MootBotNew Topic:  Open Discussion19:56
kirklandjiboumans: now you can ask your iframe question :-)19:56
jiboumans(imagine it's part of the open discussion)19:56
kim0I have a quick announcement19:56
jiboumanskrikland: i blame latency19:56
Davieyeveryone welcome kim0 o/19:56
ttxkim0: you like clouds ?19:56
kirklandkim0: welcome, btw19:56
kim0ttx: I do :)19:56
jiboumanso/ kim019:56
kim0Here I go19:56
kim0Since 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
DavieyGO19:56
kim0Here's what I've done. We're launching an initiative called "Ubuntu Server marks your city" till we find a cooler name.19:56
kim0Basically, 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 server19:56
kim0The target being, by release day (mostly 15 days) we will have covered all world's major cities (hopefully:)19:57
kim0I'm should be deploying the app tomorrow over ec219:57
jiboumanskim0: your job is cool19:57
kim0EoA19:57
kim0jiboumans: tell me about it :)19:57
kirklandkim0: neat :-)19:57
SpamapSkim0: brilliant!19:57
Davieykim0, Rocking!  Is the source avaliable?19:57
kim0Daviey: YES19:57
jiboumanskim0: can you let us know the URL so we can tweet/dent/fb/blog the hell out of it?19:57
mathiazIIRC we also mentioned we should update the server team meeting agenda to include a section with the community team19:57
kim0bzr branch lp:mapuntu19:57
Davieykim0, thanks!19:58
SpamapSmathiaz: ++19:58
kirklandkim0: that's too cool19:58
kim0jiboumans: will announce tomorrow in this list19:58
jiboumanskim0: congratulations, you get your own section in the meeting going forward19:58
kim0I wanted to add a feature19:58
jiboumanswell done!19:58
SpamapSoh sorry ubuntu is all about python..    +=119:58
RoAkSoAxI 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 cycle19:58
jiboumansspamaps++ # hah19:58
kim0a div with tweets with ubuntu server scrolling by19:58
kim0if anyone with enough javascript karma wants to hack on that19:58
DavieyRoAkSoAx, \o/19:58
kim0be my guest19:58
ttxRoAkSoAx: saw the alpha3-milestoned bug assigned to you ?19:58
* ScottK has an issue to discuss.19:59
ttxredhat-cluster-suite FTBFS19:59
RoAkSoAxttx: redhat cluster?19:59
ttxyep19:59
kirklandScottK: please19:59
ScottKI've been working on the server piece of the Kolab spec.19:59
RoAkSoAxttx: yep. I'll request sync, but will FTBFS again till all the other cluster packages are in main (pacemaker, cluster-glue, etc)19:59
ScottKIt turns out that in order to get away from a code copy, Kolab needs a couple of php5 patches.20:00
ttxRoAkSoAx: will they all be in by alpha3 ?20:00
ScottKThey 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:00
SpamapSScottK: we're going to need some scaffolding to hold up our pile of php5 patches. :)20:01
ScottKWho would be the best person to review?20:01
zulScottK: SpamapS ;)20:01
* jiboumans watches zul throw his buddy under the bus20:01
* SpamapS agrees20:01
RoAkSoAxttx: I surely hope so. I'm about to start updating the MIRs, and it will just be a matter of time20:01
zuljiboumans: i only do the packaging ;)20:01
mathiazSpamapS: are there a lot of ubuntu specific patches?20:01
ttxRoAkSoAx: ok, cool20:01
ScottKkirkland: Can we have an action for SpamapS and I to reivew Kolab php5 patches and we'll handle it offline.20:01
zulmathiaz: not for 5.3.320:02
SpamapSyeah, zul deals with PHP drudgery.. I'm the weirdo who actually kind of likes php. ;)20:02
mathiazSpamapS: otherwise I'd recommend to talk to the Debian maintainer20:02
ScottK(or whoever is running the meeting, I lost track)20:02
kirkland[ACTION] SpamapS and ScottK to reivew Kolab php5 patches20:02
MootBotACTION received:  SpamapS and ScottK to reivew Kolab php5 patches20:02
ScottKkirkland: Thanks.20:02
SpamapSScottK: whats your timezone?20:02
ScottKI'm done.20:02
kirklandokay20:02
kirkland[TOPIC] Announce next meeting date and time20:02
MootBotNew Topic:  Announce next meeting date and time20:02
kirklandTuesday 2010-08-03 at 1800 UTC - #ubuntu-meeting20:02
kirkland#endmeeting20:03
MootBotMeeting finished at 14:03.20:03
ScottKSpamapS: -040020:03
Daviey\o/20:03
jiboumansthanks all20:03
jiboumansnice chairing kirkland; an hour exact!20:03
* Daviey has pitty for the poor scribe of that meeting!20:03
kirklandjiboumans: ;-)20:03
=== Ng_ is now known as Ng
=== bjf is now known as bjf[afk]
=== Ursinha is now known as Ursinha-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!