[00:13] <rad-net> il est  y a des marrocain la non
[00:13] <rad-net> quel est le sujet de cette nuit
[11:16] <ramadasan> hi
[11:17] <aamachu> hi
[11:19] <aamachu> persia: elky: lifeless: Hi
[11:25] <elky> oh hai
[11:26] <elky> aamachu, hi!
[11:26] <elky> sorry, was cooking food
[11:26] <aamachu> elky: what's special at kitchen?
[11:26] <aamachu> elky: thats ok
[11:26] <aamachu> i din't send a reminder today..
[11:26] <aamachu> and was also late
[11:27] <elky> just the world's most boring chow mein. mince, water chestnuts, diced capsicum.
[11:28] <elky> i thought i had cabbage, but no :(
[11:28] <aamachu> oh ok.. even then its different for me from chennai..
[11:28] <aamachu> was twenty min late
[11:29] <aamachu> just wanted to know, did anyone else turned up other than us
[11:29] <elky> just you and i it seems
[11:29] <aamachu> http://wiki.ubuntu.com/Membership/RegionalBoards/AsiaOceania
[11:29] <aamachu> also the participants are not here
[11:30] <elky> well, i guess we adjourn then
[11:30] <aamachu> yes
[11:31] <aamachu> we will meet on 27 Oct, same time
[11:31] <aamachu> do you have anything else to share?
[11:32] <elky> nope, see you on the 27th
[11:32] <aamachu> ok.. bye then.. have fun
[11:32] <elky> :)
[11:33] <persia> Sorry to be late.
[11:33] <aamachu> persia: we all are
[11:34] <aamachu> i should have sent the reminder
[11:34] <persia> Such is life sometimes.  Until next time.
[11:34] <elky> persia, we still lack quorum and applicants, so you get off easy ;)
[11:34] <persia> heh :)
[11:41] <aamachu> persia: elky: bye
[14:01] <lool> NCommander: Hey
[14:02] <paulliu> hi
[14:02] <JamieBennett> hi
[14:02] <dyfet> hi
[14:02] <plars> ih
[14:02]  * StevenK says hi, just to be different
[14:03] <JamieBennett> moo
[14:03] <lool> Can someone please pick up the meeting from NCommander?
[14:03] <davidm> I'm ringing him
[14:04] <StevenK> Ooh, it's only 9am
[14:04] <lool> GrueMaster: ping
[14:04] <lool> ogra: ping
[14:04] <GrueMaster> pong.
[14:05] <GrueMaster> 6am here.
[14:05] <lool> 3pm here
[14:05] <davidm> lool, can't reach NCommander neither phone is answered
[14:05] <StevenK> 9am where NCommander is, it's midnight here
[14:05] <plars> 8:00 AM in the correct time zone
[14:05] <lool> Someone please pick up the meeting; everybody knows how it goes, right?  :-)
[14:05] <davidm> ogra, can you take the meeting please
[14:05] <GrueMaster> plars: pffft.
[14:06] <ogra> oh, no NCommander ?
[14:06] <ogra> [startmeeting]
[14:06] <ogra> bah
[14:06] <lool> #
[14:06] <ogra> [#startmeeting]
[14:06] <lool> Without brackets
[14:06] <ogra> #startmeeting
[14:06] <MootBot> Meeting started at 08:06. The chair is ogra.
[14:06] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:06] <StevenK> ogra was just waiting for one of us to type it so we would chair it
[14:06] <ogra> aha
[14:06] <lool> Exactly
[14:06] <lool> It was very tempting  :)
[14:07] <StevenK> Haha
[14:07]  * ogra tried at least
[14:07] <StevenK> I nearly fell for it
[14:07] <lool> No meeting page i'm afraid
[14:07] <ogra> yeah, i was just searching
[14:08] <ogra> i guess we can take last weeks
[14:08] <ogra> [topic] action items
[14:08] <MootBot> New Topic:  action items
[14:08] <ogra> [link] https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:08] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:08] <ogra> ah, i't just slow
[14:09] <ogra> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20091006
[14:09] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20091006
[14:09] <ogra> bit recycling :P
[14:09]  * NCommander coughs
[14:09] <lool> lubuntu seed was finally fixed
[14:09] <ogra> dyfet to move lubuntu seed to proper location and enable the meta on amd64
[14:09] <ogra> lool to test fix for RTC battery charging
[14:10] <ogra> lool, fsl asked for more measuring
[14:10] <dyfet> this was done, the problem was I always generated the seed when I built the meta and did not save the seed list in the meta...so others after broke the architecture building new instances
[14:10] <StevenK> NCommander: Ah ha! You're late to avoid chairing!
[14:10] <dyfet> because I run ./update before debuild...
[14:10] <ogra> NCommander, slacker !
[14:10] <ogra> dyfet, well, thats the right thing usually
[14:10] <NCommander> StevenK, my laptop decided to fsck itself booting up. 10 minutes later ...
[14:10] <lool> dyfet: I don't understand a thing but I dont think we need to cover details since it works now
[14:11] <dyfet> lool: agreed its done
[14:11] <ogra> well, if it surely does
[14:11] <lool> ogra: I didn't get the query from FSL part
[14:11] <lool> ogra: Which one is that?
[14:11] <lool> ogra: RTC isn't charging for me with latest ubuntu kernel; I didnt remove the resistors since you tested a 2.6.28 kernel where that wasnt needed IIUC
[14:12] <ogra> Bug 427289
[14:12] <lool> There was an action on "bjf to check with amit on going indepth on armel bugs"
[14:12] <lool> ogra: Are you actually covering the actions from last week?
[14:12] <ogra> yes
[14:13] <ogra> we dont have any new ones
[14:13] <ogra> given we dont have any new wikipage :P
[14:13] <plars> there was a new post in that bug with a kernel config from fsl
[14:13] <lool> ogra: I already answered on the RTC thing last week
[14:13] <ogra> right
[14:13] <lool> "I tested the RTC fix and it doesn't work for me"
[14:13] <plars> anyone looked at that yet?
[14:13] <plars> lool: that's the one you tested with?
[14:13] <ogra> my voltage values were attached already
[14:13] <lool> plars: No I did not
[14:14] <plars> good timing!
[14:14] <ogra> "I am measuring 2.69V on the coin-cell. Can you measure on your board what is the coin-cell voltage?"
[14:14] <lool> I dont quite get how a b 3.0 config is relevant though
[14:14] <ogra> thats the request
[14:14] <lool> The voltages were wildly different between b2.0 and 2.5
[14:14] <ogra> indeed
[14:15] <lool> This is by far the most important issue affecting us now though
[14:15] <lool> amitk: Did you and bjf discuss a process for covering armel bugs every week?
[14:15] <GrueMaster> Is it?  What about bug #431963?
[14:15] <ogra> plus the gpu patch
[14:15] <amitk> AFAIK, Freescale is actively looking at the RTC issue currently
[14:15] <lool> Something more in depth than what we can do for kernel bugs in our meeting
[14:15] <ogra> lool, did you see amitk's comment on the regulator bug
[14:16] <lool> GrueMaster: It is less serious?
[14:16] <amitk> lool: yes. We see no reason to have a separate meeting for those bugs. They are kernel bugs and should be discussed in the kernel meeting IMO
[14:16] <ogra> i think that justifies bumping it up to high
[14:16] <lool> amitk: Ok; so I can check the last kernel meeting to get an up to date status on all the linux* armel bugs?
[14:16] <plars> GrueMaster: probably less serious, but should probably be a high
[14:17] <GrueMaster> I would think it is a high as well.
[14:17] <amitk> lool: no, but we can start discussing each of the high/critical bugs in the meetings from now on, starting today's meeting
[14:17]  * ogra wouldnt bump that one to high unless we have actually tested HW that has the exact form factor for the socket
[14:17] <lool> amitk: Well yes, that's what I expected: a weekly review of progress on important armel kernel bugs
[14:18] <lool> amitk: But doing it in the kernel meeting is fine
[14:18] <lool> I just care that it's covered weekly somewhere where we can attend
[14:18] <amitk> it is in 3hr34min same place
[14:18] <plars> ogra: already bumped, bug feel free to disagree. We've hit it on 2 different boards with two different (externally powered) drives
[14:18] <ogra> plars, not a single one of them was actually shipped witzh a compatible plug :)
[14:18] <lool> I dont care about high versus medium for the SATA bug; the RTC bug should get priority, the rest depends of availability of developer time to fix the bugs
[14:19] <ogra> right, and the gpu patch :)
[14:19] <ogra> and probably the regulator bug since it can affect the world
[14:19] <amitk> ogra: as I pointed out yesterday the gpu patch is already applied
[14:19] <amitk> what is still missing?
[14:19] <ogra> amitk, oh, i didnt get that, thanks
[14:20] <ogra> amitk, but not in any current package, is it ?
[14:20] <lool> amitk: I just discovered a config issue on the dove kernel this morning
[14:20] <lool> http://people.canonical.com/~lool/IMG_2345.JPG
[14:20] <MootBot> LINK received:  http://people.canonical.com/~lool/IMG_2345.JPG
[14:20] <ogra> (i saw no changelog entry mentioning it)
[14:20] <lool> amitk: I didn't have a chance to report it, but binfmt_misc sseems to be missing in dove
[14:20] <amitk> ogra: it has always been, since i applied the sdk1.6 patches.
[14:20] <amitk> 17:14 < amitk> ogra: bjf: sha id ff4e565bfe81f10ca8aa64e24038683d5837cc51
[14:20] <amitk> from yesterday ^
[14:21] <ogra> amitk, hmm, then something is wrong, that should get me a device ...
[14:21] <ogra> but nothing to dicuss in the meeting
[14:21] <ogra> lool, are you trying to run a karmic ext4 fs with a jaunty kernel ?
[14:21] <amitk> lool: bug number with armel tag?
[14:22] <lool> You'll get one ASAP
[14:23] <ogra> lool, i have seen the exact same when trying to boot a babbage jaunty kernel with ext4 from karmic ... it goes into constant reboot for me though
[14:23] <lool> ogra: I think we covered action items
[14:23] <ogra> anyway ...
[14:23] <ogra> [topic] Specification Review
[14:23] <MootBot> New Topic:  Specification Review
[14:23] <ogra> anything to discuss here ?
[14:23]  * amitk retires
[14:23] <lool> GrueMaster: UNR ISO > did you look into that?
[14:24]  * ogra guesses everything is closed and implemented by now 
[14:24] <GrueMaster> Not much I can really look into.  I don't know beyond the manifest what to look for, unless you want me to look at package sizes.
[14:24] <lool> amitk: Ok; thanks; FYI we also have an armel bugs section -- we were just covering actions and got distracted -- but thanks for coming for the bugs meeting action
[14:24] <amitk> np
[14:24] <lool> GrueMaster: Anything really
[14:25] <ogra> anything else about specs ?
[14:25] <GrueMaster> I'll look at it again today and see if there is anything glaring.
[14:25] <paulliu> Do we need to freeze the versions of packages for Moblin? Or we just catch up the latest version?
[14:25] <lool> StevenK: Can you pickup UNR ISO size tweaks?  a) re-adding as many langpacks as possible b) looking for things which could save us some room?
[14:25] <StevenK> FinalFreeze is next week
[14:25] <lool> Perhaps non-UNRish things we could drop
[14:26] <StevenK> lool: Oh, like X? :-)
[14:26] <paulliu> OK.
[14:26] <lool> paulliu: We want to be conservative at this point; unless it's a bugfix only release and is safe to include (wont regress anything), abstain
[14:26] <ogra> [action] StevenK to look into UNR ISO size tweaks
[14:26] <MootBot> ACTION received:  StevenK to look into UNR ISO size tweaks
[14:26] <lool> paulliu: Ping StevenK and me if you see any issue or need to go through a transition
[14:26] <paulliu> lool: ok.
[14:26] <StevenK> Oh, bleh. We're oversize by 1MB
[14:27] <ogra> [action] lool to file a bug about armel fsck issues
[14:27] <MootBot> ACTION received:  lool to file a bug about armel fsck issues
[14:27] <GrueMaster> Last time I looked, the best I could come up with is dropping some X drivers that are installed (Trident, Cirrus Logic, etc) that aren't used in any known netbook configuration I could find.
[14:27] <lool> ogra: Uh
[14:27] <ogra> StevenK, bump the default to 1G ?
[14:28] <StevenK> ogra: I wish, it used to be.
[14:28] <ogra> right
[14:28] <GrueMaster> ogra: Needs to be CD distributable.
[14:28] <GrueMaster> 700M.
[14:28] <ogra> what's keeping us from doing it ?
[14:28] <StevenK> ogra: It's your fault, I added de to live :-P
[14:28] <ogra> GrueMaster, why ?
[14:28] <GrueMaster> Marketing.
[14:28] <ogra> make it DVD distributable :)
[14:29] <ogra> anyway, more issues for specs ?
[14:29] <GrueMaster> It is easier to distribute.  CD's cost $.25 DVD's cost $1.50
[14:29] <StevenK> Wubi needs someone who has a Windows install to test it
[14:29] <GrueMaster> (or something like that).
[14:30] <ogra> ok, nothing spec related i see and you guys moved on to UNR already
[14:30] <GrueMaster> StevenK: I can test it.  Is it ready again?
[14:30] <ogra> [topic] UNR Status
[14:30] <MootBot> New Topic:  UNR Status
[14:30] <StevenK> GrueMaster: I hope so.
[14:30] <lool> (I filed 450363 on the binfmt issue)
[14:30] <ogra> bug 450363
[14:31] <lool> StevenK: Could you please cover UNR status this week?
[14:31] <lool> StevenK: Are we up-to-date in upstream tarballs, and seed commits?
[14:31]  * ogra listens
[14:31] <StevenK> lool: Yes, and yes
[14:31] <StevenK> Just checked
[14:31] <ogra> sounds good
[14:31] <lool> https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:31]  * StevenK double checks seeds
[14:32] <ogra> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:32] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:32] <lool> The maximus crasher was closed as it was old
[14:32] <StevenK> I've been triaging that list, and pointing njpatel at things I'm unclear on
[14:32] <StevenK> I'd like to get that list down a lot before release
[14:32] <lool> StevenK: any bugs worth mention here?
[14:32] <ogra> looks fine to me
[14:32] <ogra> StevenK, what list ?
[14:32] <ogra> it's empty
[14:32] <lool> ogra: the non-karmic one
[14:32] <ogra> oh, ok
[14:33] <ogra> is that all about UNR ?
[14:33] <plars> there are probably some that need to move over... will take a look later today
[14:33] <StevenK> lool: Yeah
[14:33] <StevenK> lool: Er, no, sorry. I'm done.
[14:33] <ogra> [action] plars to move UNR bugs from non-karmic to karmic where necessary
[14:33] <lool> StevenK: We got a new clutter release uploaded; would be good to test the UI in the latest images
[14:33] <MootBot> ACTION received:  plars to move UNR bugs from non-karmic to karmic where necessary
[14:34]  * StevenK blames the time, since it's 0034
[14:34] <lool> Anything else WRT UNR?
[14:34] <StevenK> Nope, I'm good
[14:34] <ogra> doesnt look like
[14:34] <StevenK> I'm unsure about GrueMaster's suggestion
[14:34] <ogra> [topic] UMR Status
[14:35] <MootBot> New Topic:  UMR Status
[14:35] <lool> (Can we please name UMR "moblin remix" instead; it's too close to UNR otherwise)
[14:35] <paulliu> The 3-rd round sync is acked.
[14:35] <lool> paulliu: Do we have anerley and anjal-anerley in karmic?
[14:36] <paulliu> Waiting for anerley binaries.
[14:36] <lool> Ok
[14:36] <lool> paulliu: Is the Dbus issue in live systems still problematic?
[14:36] <lool> Does it happen all the time?
[14:36] <paulliu> Sorry. What's the issue?
[14:37] <paulliu> I didn't see dbus issues currently on my hardwares.
[14:37] <lool> bug #449230
[14:37] <lool> plars, GrueMaster, StevenK: You guys saw this?
[14:37] <StevenK> I tried to test that in Virtualbox, and couldn't run UMR in it :-(
[14:38] <lool> StevenK: Did you flip the enable 3d pref?
[14:38] <lool> it's off by default
[14:38] <StevenK> lool: Aye
[14:38] <plars> just came in yesterday I think, hadn't had a chance to look at it yet but I saw it in my bugmail
[14:38] <GrueMaster> I'll try to reproduce it later today when I do a fresh install for Moblin Compliance testing.
[14:38] <lool> StevenK: It used to work for me last week; what's the issue?
[14:38] <GrueMaster> There were some ubiquity bugs that went through all the images last week.
[14:38] <StevenK> lool: I get a screen with a background image that I can't interact with
[14:38] <lool> plars, GrueMaster: If you find it fixed, please dup it against 448981
[14:39] <StevenK> (On a live CD boot)
[14:39] <paulliu> StevenK: Today's image?
[14:39] <StevenK> paulliu: The latest, 1013
[14:39] <lool> plars, GrueMaster: Did you guys complete installs last week?
[14:40] <paulliu> StevenK: Yeah. I'm trying to downloading it now. I saw mutter is updated. From 2.27.5 to 2.28.0. Some API bumped.
[14:40] <lool> Are the APT issues solved?
[14:40] <lool> (deb deb sources.list entry and APT error popup during install)
[14:40] <plars> lool: for iso tracker?
[14:40] <paulliu> StevenK: That might break mutter-moblin so only background image that can't do anything.
[14:40] <GrueMaster> Last image I installed from scratch was 10/8
[14:40] <ogra> wasnt ubiuquity broken the whole last week ?
[14:40] <StevenK> The former should be, but modulo doing an install to actually test
[14:40] <GrueMaster> Worked fine then.
[14:40] <lool> plars: I mean the installation issue; I dont think that relates to ISO tracker
[14:40] <StevenK> paulliu: But the same image works fine on my NC10
[14:40] <lool> *issues
[14:41] <paulliu> StevenK: hmm....
[14:41] <plars> lool: I do installs as often as I can, but sometimes update if I'm actively using that machine for some other testing (i.e. testing kernels on imx51 last week)
[14:42] <GrueMaster> I need to verify the ppa issue.  IIRC, it was listed incorrectly with two "deb" tags.
[14:42] <lool> plars, GrueMaster: So on your next install, plesae check sources.list to see whether it's correct (correct PPA entry with deb-src if needed)
[14:42] <plars> will do
[14:42] <GrueMaster> will do.
[14:42] <lool> (And reopen the APT error popup bug if you get it)
[14:42] <ogra> why are there no bugs open for all the above issues ?
[14:42] <lool> Was an ubiquity issue
[14:42] <lool> ogra: there are bugs open for all the above issues
[14:43] <ogra> https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-moblin
[14:43] <ogra> not here
[14:43] <lool> bug #439485
[14:43] <lool> ogra: Becasue these are closed
[14:43] <ogra> oh, ok
[14:43] <lool> or were affecting moblin remix which is not karmic stuff
[14:43] <ogra> i thought they were moblin specific ones
[14:43] <GrueMaster> ogra: I know about these bugs, and have ready access to them for updating.  Just don't know the numbers off the top of my head.
[14:43] <lool> the sources.list issue is bug #420048
[14:43] <lool> paulliu, StevenK: Anything else for moblin remix?
[14:44] <lool> Critical bugs etc.?
[14:44] <StevenK> Only my virtualbox issue :-(
[14:44] <ogra> file a bug :)
[14:44] <GrueMaster> I would like to point out that we are getting close to full compliance.
[14:44] <GrueMaster> Last image had 171 errors, down from 449.
[14:44] <lool> I'm so excited, which moblin compliant apps will I be able to run there?!  </sarcasm>
[14:44] <paulliu> lool: nothing else.
[14:44] <lool> :-P
[14:45] <lool> paulliu: thakns
[14:45] <lool> ogra: I guess we can move to armel
[14:45] <ogra> [topic] armel status
[14:45] <MootBot> New Topic:  armel status
[14:45] <StevenK> GrueMaster: Are these still useful errors, or the ones like "You don't have <useless kernel config change> enabled" ?
[14:45] <lool> doko: Around?
[14:45] <ogra> (i subscribed ubuntu-moblin to bug 420048 so it shows up on the list)
[14:46] <lool> doko: What's the plan for oo.o now?  .jaunty thingie for release?
[14:46] <GrueMaster> StevenK: which are you referring to?  Moblin?
[14:46] <StevenK> GrueMaster: Yeah
[14:46] <lool> ogra: it wont
[14:46] <lool> ogra: the list is specific to karmic
[14:46] <ogra> humm, why ?
[14:46] <GrueMaster> I'll show you after the meeting.
[14:46] <lool> ogra: we should use a second link for high bugs in moblin-remix or smth
[14:46] <ogra> why isnt the bug karmic specific ?
[14:47] <ogra> well, we should just make them show up properly imho
[14:47] <lool> ogra: When it's a cdimage or moblin remix bug, it's by definition not a karmic bug
[14:47] <ogra> hrm
[14:47] <ogra> well, anyway, armel ...
[14:48] <lool> https://bugs.launchpad.net/~ubuntu-moblin/+subscribedbugs
[14:48] <ogra> my boards survived the upgrades i did yesterday, images seem to build again, we had an ABI bump on imx51
[14:48] <lool> my dove y1 hangs regularly under load
[14:48] <lool> like completely dead
[14:48] <ogra> (need to bump d-i before tonights build)
[14:48] <lool> NCommander: Is partman-uboot out of new?
[14:48] <lool> NCommander: what do we need to do about it still?
[14:49] <lool> TB meeting in 10 mns
[14:49] <ogra> right, NCommander ?
[14:49] <pitti> cjwatson, Keybuk, dholbach: we have the DMB meeting in 10, right?
[14:50] <Keybuk> right
[14:50] <NCommander> sorry, phone rang
[14:50]  * kees waves
[14:50] <NCommander> Uh, partman-uboot is still in NEW to my knowledge
[14:50] <ogra> anyway, for imx51 bug 446140 and bug 427289 are still on my critical list
[14:50] <ogra> NCommander, any open bugs on dove we should know about ?
[14:51] <NCommander> ogra, just the one about us needing partman-uboot
[14:51] <ogra> (apart from the one lool just filed)
[14:51] <ogra> ok
[14:51] <ogra> i guess thats it for armel then
[14:51] <ogra> [topic] AOB
[14:51] <MootBot> New Topic:  AOB
[14:51] <lool> ogra: Could you attend weekly kernel meetings?
[14:51] <ogra> lool, bad timing, FSL call
[14:51]  * NCommander will handle minutes for this meeting and fix last weeks as well :-/
[14:52] <lool> And make sure 446140 431963 427289 are updated?
[14:52] <ogra> will do
[14:52] <lool> why is 420447 fix committed and not uploaded?
[14:52] <ogra> oi have one AOB topic
[14:52] <lool> 383240 > I have packages in my PPA and need testers
[14:52] <GrueMaster> What's up with the Ubuntu MID remix? (It's on last weeks agenda).
[14:52] <lool> I'm looking for anybody really to test the ffmpeg packages in my PPA
[14:52] <StevenK> Tis not a remix
[14:52] <lool> On amd64 or armel
[14:52] <ogra> everyone in the team needs to commit one hour per week to fix sponsoring bugs
[14:53] <lool> GrueMaster: I think it's a leftover, just delete it
[14:53] <ogra> [action] new rolling action: everyone with upload privs to look inot sponsoring bugs next week and report which ones he closed
[14:53] <MootBot> ACTION received:  new rolling action: everyone with upload privs to look inot sponsoring bugs next week and report which ones he closed
[14:53] <ogra> bah, typoed
[14:54] <ogra> [action] anyone who has spare test cycles to test lool's ffmpeg packages
[14:54] <lool> Can anybody please commit to testing ffmpeg from my PPA?  Basically play some files with ffplay or a ffmpeg based player and see whether there are regressions with the PPA pacakges
[14:54] <MootBot> ACTION received:  anyone who has spare test cycles to test lool's ffmpeg packages
[14:54] <ogra> is that it ?
[14:54] <GrueMaster> What platform?
[14:55] <ogra> armel or amd64
[14:55] <ogra> as lool said above
[14:55] <JamieBennett> lool: I can take a look
[14:55] <davidm> lool, sorry I can't help, I don't have either platform
[14:55] <ogra> anything else we need to bring up ?
[14:55] <lool> Thanks
[14:56] <ogra> going once
[14:56] <GrueMaster> I have an AMD64 system for LSB testing.  I can look at those this week.
[14:56] <ogra> going twice ...
[14:56] <ogra> sold to the man with the yellow hat !
[14:56] <ogra> #endmeeting
[14:56] <MootBot> Meeting finished at 08:56.
[14:56] <JamieBennett> GrueMaster probably best for you to do AMD64 aswell as I'm not around after today
[14:56] <JamieBennett> Just in case
[15:03] <cjwatson> developer membership board meeting?
[15:04] <jpds> Good afternoon.
[15:04] <cjwatson> mdz,Keybuk,kees,pitti: ping
[15:04] <cjwatson> no sabdfl?
[15:04] <Keybuk> I'm here
[15:05] <pitti> on the TB ML we already had some long discussion with dholbach about simplifying/changing https://wiki.ubuntu.com/UbuntuDevelopers#Applying%20for%20team%20membership for the new "smaller teams" archive reorganization
[15:05] <cjwatson> #startmeeting
[15:05] <MootBot> Meeting started at 09:05. The chair is cjwatson.
[15:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:05] <cjwatson> [TOPIC] Adjusting team membership applications for delegated upload teams
[15:05] <MootBot> New Topic:  Adjusting team membership applications for delegated upload teams
[15:06] <kees> cjwatson: hi
[15:06] <cjwatson> Mark's proposal near the end of the thread was as follows:
[15:06] <pitti> Q: are we still keeping the process of "core-dev" for folks who can upload anywhere? should we treat this separately?
[15:06] <cjwatson>  - set up devel-permissions@ list
[15:06] <cjwatson>  - invitations/requests go there as well as to relevant team list
[15:06] <cjwatson>  - all approvals go to ubuntu-devel@ and devel-permissions@
[15:07] <cjwatson> [and I think maybe also to the team list]
[15:07] <pitti> (was about to ask)
[15:07] <cjwatson> dholbach +1ed that; it sounds to me as if it meets all our requirements to date, too
[15:07] <Keybuk> I think it's a bit of a silly mailing list
[15:07] <Keybuk> will anyone subscribe to it?
[15:07] <cjwatson> pitti: core-dev comes to DMB, but otherwise should be basically the same requirements, I think
[15:07] <Keybuk> well, dholbach obviously ;)
[15:08] <pitti> cjwatson: it would certainly be nice to have the same process indeed
[15:08] <dholbach> Keybuk: we have a bunch of people who subscribed to the motu-council list and are active there
[15:08] <Keybuk> DMB is intended to be a delegated team for core-dev in much the same way that kubuntu-dev is for kubuntu
[15:08] <cjwatson> Keybuk: I think it's a bit silly, but I don't mind it existing if people like it that way
[15:08] <Keybuk> right, for me it's a +0 - I don't hate it or love it
[15:08] <pitti> d-perms@ seems a bit bureaucratic to me as well, but it surely is a nice central place for looking up old applications/approvals
[15:09] <dholbach> Keybuk: as I said in the mail discussion: I don't know if we should have a new list for it, but I think it should be public
[15:09] <cjwatson> there's an advantage to that, true
[15:10] <cjwatson> is there any point in significant further discussion on this, or should we just vote on Mark's proposal?
[15:10] <kees> I'm +1 -- if it becomes a problem or is ignored, we can adjust it at a later time.
[15:10] <Keybuk> I think we can just vote
[15:10] <cjwatson> [VOTE] ratify Mark's proposal for developer membership announcements
[15:11] <MootBot> Please vote on:  ratify Mark's proposal for developer membership announcements.
[15:11] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[15:11] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:11] <pitti> so do I; seems on the ML we had good consensus already anyway
[15:11] <Keybuk> +0
[15:11] <MootBot> Abstention received from Keybuk. 0 for, 0 against. 1 have abstained. Count is now 0
[15:11] <pitti> +1
[15:11] <MootBot> +1 received from pitti. 1 for, 0 against. 1 have abstained. Count is now 1
[15:11] <cjwatson> +1
[15:11] <MootBot> +1 received from cjwatson. 2 for, 0 against. 1 have abstained. Count is now 2
[15:11] <kees> +1
[15:11] <MootBot> +1 received from kees. 3 for, 0 against. 1 have abstained. Count is now 3
[15:11] <cjwatson> I haven't seen mdz active here yet, beyond his client joining
[15:11] <cjwatson> #endvote
[15:12] <cjwatson> [ENDVOTE]
[15:12] <MootBot> Final result is 3 for, 0 against. 1 abstained. Total: 3
[15:12] <cjwatson> !"£% NO CARRIER
[15:12] <kees> heh
[15:12] <cjwatson> I think we can consider that passed, given that we have quorum
[15:12] <cjwatson> right, is there anything else we need to agree upon about the DMB's basic ground rules?
[15:13] <cjwatson> developer-membership-board@ vs. developer-membership-board-private@ lists perhaps?
[15:13] <pitti> who would be on the private list?
[15:13] <Keybuk> sure, if you can find a way to phrase the vote that's not "Do you disagree with the opinion against the EU constitution" :p
[15:13] <cjwatson> the six of us
[15:14] <cjwatson> Keybuk: hmm? :)
[15:14] <cjwatson> six> plus whomever else is incorporated in the future obviously, e.g. motu-council
[15:15] <pitti> I asked because e. g. if someone applies to kubuntu-dev, and other kubuntu devs have some reservations, should or  shouldn't that be discussed on d-m-b-private@?
[15:16] <cjwatson> oh, I see
[15:16] <cjwatson> err. I think I was imagining it as a list for whatever private discussion is needed for core-dev applicants?
[15:16] <pitti> I mean, I wouldn't exactly propose to have one huge list with all team "leaders" on it
[15:17] <cjwatson> since kubuntu-(whatever) can approve new kubuntu-dev members on their own, they don't need to go to the DMB to do it
[15:17] <cjwatson> that being the point of delegating
[15:17] <kees> pitti: right, I was wondering the same, but realized the DMB has delegated that stuff
[15:17] <pitti> ok, so this is exclusively meant for new core-devs then (the bits that aren't delegated)
[15:17] <kees> so our -private is our solution to that problem for our own discussions.
[15:17] <pitti> makes more sense to me now
[15:17] <Keybuk> cjwatson: right, I was thinking about that the other day
[15:18] <Keybuk> given that I don't want to impose procedures on other teams
[15:18] <Keybuk> that means I don't want to impose privateness on thsoe teams either
[15:18] <dholbach> so applicants will send something like "I'll be at the XYZ Board's meeting next week?" and people will get in touch with them, if they should really have private remarks to make?
[15:19] <cjwatson> Keybuk: also, core-devs can do more damage
[15:19] <cjwatson> nobody knows the whole archive well enough for natural talent alone to carry them along :)
[15:19] <cjwatson> there tends to be more complicated cooperation involved
[15:19] <Keybuk> right
[15:20] <Keybuk> I was thinking that too
[15:20] <Keybuk> so, after "appearing to ignore all the arguments while really listening and reforming my own opinion" </cjwatson> I'm going to say I think the DMB list should be public :p
[15:21] <pitti> it should be public either way; I thought the question was to have an additional -private@
[15:21] <kees> right
[15:21] <cjwatson> Keybuk: ;-)
[15:22] <pitti> I hope that we won't actually need it that often
[15:22] <pitti> but we can have it just in case
[15:22]  * kees nods
[15:23] <Keybuk> I'm not sure we need it
[15:24] <Keybuk> the case where someone applies for core-dev access, but we have serious reservations, can probably be dealt with by private e-mail rather than a ML ?
[15:24] <kees> Keybuk: the point is to have a single place for people to email with reservations.  if not a list, then at least an exploder alias.
[15:25] <cjwatson> I was just thinking of saying the same; my original reason for being in favour of a list is that I think we should actively invite criticism (as long as it's not just character-assassination)
[15:25] <cjwatson> and I suppose we could do that by saying "if you have an objection you don't want to raise in public, please e-mail all the DMB members" but it seems a bit cumbersome and I don't think that would actually happen if phrased that way
[15:26] <kees> that would just further discourage that sort of communication.
[15:27] <dholbach> as long as there's any kind of option to pass on feedback or have some kind of discussion, I think it's OK
[15:27] <Keybuk> yeah that's true
[15:27] <pitti> dholbach: /query or private mail are available any time
[15:28] <kees> I don't see why -private is a problem if we've accepted the need for a place for private discussion.
[15:28] <cjwatson> nor I
[15:28] <dholbach> I know, but the documentation or process should invite that some how or invite feedback
[15:28] <Keybuk> I don't think it's a problem either FWIW :)
[15:29] <dholbach> if you have a developer applying you don't know that has 4 cheerleaders, you'll be happy if somebody lets you know "I sponsored 3-4 uploads where I wasn't quite so sure about the quality, maybe that developer should wait a few more weeks or something"
[15:29] <Keybuk> indeed
[15:29] <kees> Keybuk: so you don't think it's a problem, but you don't think it's needed?
[15:30] <Keybuk> I don't think it's a problem to have it, I think we should agree that it's needed, but there seems to be a good argument for that
[15:30] <persia> I'd suggest that a list is better than personal email, simply because personal email may well go to a smaller subset of people, or someone may be asked to proxy opinions based on perception of personal relationships.
[15:31] <dholbach> how that's implemented by the board is a matter of taste, I'd say, but you surely want other developers to notice there's going to be some decision about upload rights some time soon :)
[15:32] <cjwatson> how about we create -private, and if nobody uses it over (say) the next year, we delete it?
[15:32] <cjwatson> I'd like to move past this ...
[15:32] <Keybuk> I'd +1 that
[15:32] <kees> I don't think its disuse proves it isn't a useful channel to have available.
[15:33] <kees> but I'd like to get past this.  how about "re-evaluate its utility" in a year instead of "delete" if it's idle?
[15:33] <Keybuk> actually, let's just create it ;)
[15:33] <Keybuk> if we don't use it, we don't use it
[15:33] <pitti> it's just a ML *shrug*, nothing that needs serious attention or maintenance
[15:34]  * kees nods
[15:34] <cjwatson> ok
[15:34] <cjwatson> sounds good, let's do it
[15:34] <cjwatson> anything else before we look at Cody's application?
[15:36] <cjwatson> [TOPIC] Cody Somerville -> ubuntu-core-dev
[15:36] <MootBot> New Topic:  Cody Somerville -> ubuntu-core-dev
[15:36] <cjwatson> cody-somerville: are you here?
[15:36] <Keybuk> I have little to say here other than "is he not already? +1"
[15:36] <Keybuk> :)
[15:36] <kees> yeah, same from me.
[15:37] <Keybuk> I have a feeling cody applied to the TB before?  Is my feeling right or wrong?
[15:37] <cjwatson> cody-somerville: thanks for being patient while we worked through our teething difficulties with our new arrangements
[15:38] <cjwatson> I was sort of hoping to be able to talk with Cody about how Xubuntu is going, and about the issues he raised regarding SRUs
[15:38] <cjwatson> he did say he'd be able to show up to this meeting
[15:39] <Keybuk> cjwatson: are those blockers for his application?
[15:39] <cjwatson> Keybuk: before> I have a similar feeling but can't remember and can't quickly verify
[15:40] <Keybuk> no, me neither
[15:41] <Keybuk> and I have the entire TB ML archive
[15:41] <Keybuk> so I must be mistaken ;)
[15:41] <cody-somerville> cjwatson, I'm here :)
[15:41] <cjwatson> aha
[15:41] <cjwatson> excellent
[15:42] <cjwatson> cody-somerville: ok, so how do you feel Xubuntu's going at the moment, as a project?
[15:44] <cody-somerville> cjwatson, I'm very excited with the direction Xubuntu is moving in. Each release I feel we have a stronger, more vibrant team eager to tackle the challenges of planning and developing a derivative of Ubuntu.
[15:46] <cody-somerville> Karmic in particular has seen substantial improvements in terms of engaging our Ubuntu counterparts and contributing patches to improve integration of desktop components shared between Xubuntu and Ubuntu.
[15:46] <cjwatson> cody-somerville: I've seen some comments to the effect that Xubuntu is getting less lightweight due to moving closer to GNOME in various ways; is this a direction you're happy with, or do you feel that it indicates problems that need to be addressed?
[15:47] <pitti> (gdm *cough*)
[15:48] <cjwatson> I saw a memory use analysis showing a Xubuntu desktop taking more memory than Ubuntu, but I didn't verify it so it may be scurrilous rumour :-)
[15:48] <cody-somerville> We make a conscious decision to balance usability, integration, and performance.
[15:49] <cody-somerville> We've made a number of changes in Karmic to reduce memory usage including using ld's --as-needed option and re-evaluating the default desktop configuration.
[15:49] <cjwatson> right, I think the report I saw was on 9.04
[15:49] <cody-somerville> Although much of the work was preliminary, I feel we have a stronger working knowledge of the area to move forward with more dramatic efforts to reduce our memory usage in karmic+1
[15:50] <cody-somerville> Furthermore, some of the reports I conferred with Keybuk on (particular boot time) which Keybuk indicated to me that the journalist misinterpreted the bootcharts.
[15:50] <cjwatson> surely not, journalists never misinterpret things ;-)
[15:51] <cjwatson> cody-somerville: I'd also like to ask about the OEM Services team; you indicated that one thing you were interested in was helping to get OEM changes integrated into Ubuntu proper, and I agree that there's a need for improving that process. What sort of review would you apply to such changes?
[15:51] <cjwatson> and is there anything you definitely wouldn't integrate? :)
[15:51] <cody-somerville> Excellent question.
[15:55] <cjwatson> cody-somerville: ... :-)
[15:55] <cody-somerville> The OEM Services Team produces a lot of good work. A lot of work to produce bugs fixes, usability enhancements, etc. occur within that team but unfortunately some of it never makes it to Ubuntu proper. I think as a member of the OEM Services team, I'd be able to expedite the merging of low hanging fruit as well as facilitate the necessary connections between the Upstream, Ubuntu, and OEM counterparts to have the more complex
[15:55] <cody-somerville>  and involved changes receive the necessary discussions and more thorough reviews.
[15:55] <cjwatson> aha
[15:56] <cody-somerville> There are naturally some changes that are unfit to be uploaded as is to Ubuntu. Changes that are specific to a vendor or a narrow use case.
[15:57] <cjwatson> ok, I'm satisfied with that; any more questions before we move to a vote?
[15:58] <Keybuk> none from me
[15:58] <pitti> I'm good
[15:58] <cjwatson> [VOTE] Approve Cody Somerville for ubuntu-core-dev
[15:58] <MootBot> Please vote on:  Approve Cody Somerville for ubuntu-core-dev.
[15:58] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[15:58] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:58] <cjwatson> +1
[15:58] <MootBot> +1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 1
[15:58] <kees> +1
[15:58] <MootBot> +1 received from kees. 2 for, 0 against. 0 have abstained. Count is now 2
[15:58] <pitti> +1
[15:58] <MootBot> +1 received from pitti. 3 for, 0 against. 0 have abstained. Count is now 3
[16:00] <kees> Keybuk: ?
[16:00] <Keybuk> +1
[16:00] <MootBot> +1 received from Keybuk. 4 for, 0 against. 0 have abstained. Count is now 4
[16:00] <cjwatson> #endvote
[16:00] <Keybuk> focus issue there
[16:00] <cjwatson> argh
[16:00] <cjwatson> [ENDVOTE]
[16:00] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[16:01] <cjwatson> cody-somerville: welcome, and thanks again for your patience
[16:01] <kees> congrats cody-somerville :)
[16:01] <cody-somerville> Thanks! :)
[16:01] <pitti> cody-somerville: rock on!
[16:01] <cjwatson> I'll do the LP bits
[16:01] <mterry> cody-somerville: nice!
[16:01] <dholbach> congratulations cody-somerville!
[16:01] <cjwatson> and we're out of time. Did we miss any candidates we need to ensure to invite for next time?
[16:01] <cjwatson> #endmeeting
[16:01] <MootBot> Meeting finished at 10:01.
[16:02] <nijaba> o/
[16:03] <ttx> o/
[16:03] <Daviey> \o
[16:03] <nurmi> o/
[16:03] <sommer> o//
[16:03] <Keybuk> o|_|/
[16:03] <zul> heylo
[16:04]  * mathiaz waves
[16:04] <alexm> o/
[16:04] <zul> mathiaz: always have to be different dont you? ;)
[16:04] <smoser> o/
[16:04] <kirkland> o/
[16:05]  * ttx waits one minute to see if mdz will join us
[16:05] <mathiaz> ttx: are you running the meeting?
[16:05] <ttx> mathiaz: I am, if he isn't
[16:05] <ttx> ok, let's start, I'll defer to him in case of need
[16:06] <ttx> #startmeeting
[16:06] <MootBot> Meeting started at 10:06. The chair is ttx.
[16:06] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:06] <ttx> Welcome to the server team meeting -- Agenda: https://wiki.ubuntu.com/ServerTeam/Meeting
[16:06] <ivoks> (hi)
[16:07] <ttx> [TOPIC] Review ACTION points from previous meeting
[16:07] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:07] <ttx> See https://wiki.ubuntu.com/MeetingLogs/Server/20091006
[16:07] <ttx> ACTION: ttx to review test plans and ensure they are aligned with 9.10
[16:07] <ttx> Done, pending some alignment by ara and the QA team
[16:07] <ttx> ACTION: kirkland to confirm that his test rig is fully operational
[16:08] <kirkland> ttx: confirmed
[16:08] <ttx> ACTION: kirkland to adapt help.ubuntu.com VM recipe(s?) to use libvirt
[16:08] <kirkland> ttx: we used the heck out of it last week here
[16:08] <kirkland> ttx: not done
[16:08] <ttx> kirkland: I agree that its lower prio
[16:08] <ttx> reporting it...
[16:08] <ttx> [ACTION] kirkland to adapt help.ubuntu.com VM recipe(s?) to use libvirt
[16:08] <MootBot> ACTION received:  kirkland to adapt help.ubuntu.com VM recipe(s?) to use libvirt
[16:09] <ttx> ACTION: mathiaz to work with the QA team on a server bug day for Karmic
[16:09] <mathiaz> ttx: done - running tomorrow
[16:09] <mathiaz> pedro_: ^^ - thanks!
[16:09] <ttx> cool, we'll talk about that later in the show
[16:09] <ttx> (after the first ad break)
[16:09] <ttx> ACTION: mdz to follow up with marjo regarding general QA support in Karmic
[16:09] <pedro_> you're welcome, i always enjoy to work with you folks :-)
[16:09] <ttx> That was done
[16:10] <ttx> ACTION: smoser to follow up with mdz regarding UEC image testing capability
[16:10] <smoser> i'm not sure what that was...
[16:10] <ttx> I guess it was about getting what it takes to be able to test images yourself
[16:10] <ttx> hw need, whatever
[16:11] <smoser> yeah, wlell i think then that its done. i got a newegg delivery. but not yet installed.
[16:11] <ttx> who has a working UEC test setup as of today ?
[16:11] <ttx> o/
[16:11] <ttx> kirkland said yes
[16:11] <nurmi> o/
[16:11] <nijaba> o/
[16:11] <ttx> nurmi: :)
[16:11] <ttx> mathiaz: ?
[16:11] <ivoks> haven't tried it :/
[16:11] <mathiaz> ttx: hm - nope.
[16:11] <ttx> ivoks: you're soo 20th century, man
[16:11] <kirkland> ttx: jsalisbury has been testing and providing feedback on the mailing list
[16:12] <jsalisbury> correct
[16:12] <mathiaz> ttx: I had to give hardware back
[16:12] <kirkland> ttx: he responded to jono 's call for testing
[16:12] <ivoks> ttx: i'm working on pacemaker... 30th century :D
[16:12] <ttx> davmor2 has been setting it up as well.
[16:12] <mathiaz> ttx: I should have access to more hw later today and plan to setup a cloud there as weel
[16:12] <alexm> ttx: i'd like to but no hardware available ATM
[16:12] <ttx> ok
[16:12] <ttx> ACTION: zul to fix m2crypto test suite and ensure that MIR is processed
[16:12] <davmor2> \o/ works here
[16:12] <zul> id like to but busy with other things like m2crypto
[16:13] <ttx> zul: how is it going ?
[16:13] <zul> testsuite is running but it fails right now because it needs network access to work so its running but it doesnt fail if there is no access
[16:13] <zul> should be done today
[16:13] <ttx> [ACTION] zul to fix m2crypto test suite and ensure that MIR is processed
[16:13] <MootBot> ACTION received:  zul to fix m2crypto test suite and ensure that MIR is processed
[16:14] <ttx> ACTION: soren/niemeyer to arrange a meeting to discuss reference appliance plan of action
[16:14] <ttx> They discussed it, that's sure
[16:14] <ttx> I'm not sure if any of them are around, though
[16:14] <ttx> ACTION: mathiaz to document test plan for image store
[16:15] <mathiaz> ttx: hm - niemeyer wrote most of the intstructions
[16:15] <mathiaz> ttx: available in a README text file
[16:15] <ttx> in image-store-proxy ?
[16:15] <mathiaz> ttx: should I add them to the testcases wiki page as well?
[16:15] <mathiaz> ttx: yes - in image-store-proxy
[16:15] <niemeyer> ttx: I'm here, but I don't have much else to comment about this ATM
[16:16] <ttx> mathiaz: yes, that would be good
[16:16] <mathiaz> ttx: http://bazaar.launchpad.net/~image-store/image-store-proxy/trunk/annotate/head%3A/README
[16:16] <mathiaz> ttx: ok - I can write up a new test cases
[16:16] <ttx> mathiaz: not sure we would make a delivery test from it, but documenting the tseet doesn't hurt
[16:17] <mathiaz> ttx: ok - the test cases should *not* be added to the ISO tracker?
[16:17] <ttx> [ACTION] mathiaz to add test case for image store in testcases wiki
[16:17] <MootBot> ACTION received:  mathiaz to add test case for image store in testcases wiki
[16:17] <ttx> mathiaz: I'd say it would need some discussion, based on the testcases contents
[16:17]  * mathiaz nods
[16:18] <ttx> ACTION: zul to triage his assigned bugs
[16:18] <zul> done
[16:18]  * kirkland high fives zul
[16:18] <zul> thanks kirkland
[16:18] <ttx> [TOPIC] Eucalyptus status
[16:18] <kirkland> ;-)
[16:18] <MootBot> New Topic:  Eucalyptus status
[16:18] <ttx> https://bugs.launchpad.net/ubuntu/+source/eucalyptus
[16:19] <ttx> so we currently have a 1.6~bzr919-0ubuntu3
[16:19] <ttx> which includes the r920 fix
[16:19] <ttx> I've a r925 merge pending
[16:19] <ttx> nurmi: should we move to that one ?
[16:19] <nurmi> that revno should help a lot with multi-cluster/component, and some single cluster installations
[16:20] <ttx> nurmi: nothing else in the pipe ?
[16:20] <nurmi> ttx: there are two more important fixes that we have in testing right now (important for multi-cluster)
[16:20] <ttx> nurmi: when are they expected out of testing ? end of today ?
[16:21] <ttx> (of /your/ today) ?
[16:21] <nurmi> ttx: 430266, 449944
[16:21] <nurmi> ttx: yes, before 5pm PST, today
[16:22] <ttx> hmm, kirkland: do you think there is valud in committing r925, then ?
[16:22] <kirkland> ttx: not if we have another merge comming
[16:22] <kirkland> ttx: if it is the caboose, then sure, let's upload
[16:22] <kirkland> ttx: but if there's more in the pipeline, let's wait
[16:22] <ttx> there is, according to Dan
[16:23] <kirkland> ttx: right. i'll wait
[16:23] <ttx> kirkland: and no urgent fxies in r925 either
[16:23] <kirkland> ttx: i'll take care of the upload in my locale then
[16:23] <kirkland> ttx: so that you can go to bed :-)
[16:23] <ttx> i committed what was urgent in the 919-0ubuntuµ3
[16:23] <ttx> ok.
[16:24] <ttx> kirkland: how is bug 432154 doing ?
[16:24] <kirkland> ttx: i'm working on that now
[16:24] <kirkland> ttx: i got a patch from aligouri
[16:24] <kirkland> ttx: that might help nurmi out, on the scsi front
[16:24] <ttx> kirkland: is there a light at the end of the tunnel ?
[16:24] <kirkland> ttx: well, let's say that i'm holding a lottery ticket
[16:24] <nurmi> kirkland: is this for virtio or scsi attach?
[16:25] <kirkland> nurmi: his patch is for scsi
[16:25] <nurmi> kirkland: nod
[16:25] <smoser> ttx, are we still wanting 'acpi_php' loaded at boot in uec-images ?
[16:25] <kirkland> nurmi: it's a long shot
[16:25] <kirkland> smoser: yes, and it's acpiphp
[16:25] <smoser> right
[16:25] <ttx> kirkland: ok, lets play the lottery.
[16:25] <smoser> ok.. there is no bug for that i think
[16:25] <smoser> right ?
[16:25] <kirkland> ttx: this is a deep, complex bug
[16:25] <kirkland> ttx: i'm doubtful a single patch is going to fix everything
[16:25] <ttx> kirkland, cjwatson: status for bug 446023 ?
[16:26] <niemeyer> nurmi, kirkland: Btw, mathiaz found an issue trying to install an image which was installed through the image store
[16:26] <kirkland> ttx: as it involves eucalyptus invocation of a libvirt function that uses qemu-kvm functionality that's been modified from upstream qemu
[16:26] <ttx> kirkland: from release meeting it sounded like cjwatson deferred 446023 to you ?
[16:26] <ttx> iirc
[16:26] <niemeyer> I can't see it being related to the store specifically, so it'd be great to have some help from the Euca developers
[16:26] <mathiaz> niemeyer: right - I'll ask about it later
[16:26] <niemeyer> mathiaz: Awesome, thank you
[16:26] <kirkland> ttx: yeah, my plate is very, very, very incredible full
[16:26] <kirkland> ttx: any help would be hot
[16:27] <ttx> kirkland: feel fre to leave the > rev925 merge out of your plate
[16:27] <ttx> kirkland: I can handle it tomorrow morning
[16:27] <ttx> ok, lets move on
[16:28] <ttx> [TOPIC] UEC/EC2 images
[16:28] <MootBot> New Topic:  UEC/EC2 images
[16:28] <mathiaz> ttx: hm - wait
[16:28] <mathiaz> ttx: for eucalyptus
[16:28] <ttx> mathiaz: yes
[16:28] <mathiaz> nurmi: did you get a change to look at bug 446841?
[16:29] <nurmi> mathiaz: i havn't been able to test image store proxy, yet, but it is on my list for today's testing
[16:29] <mathiaz> nurmi: ok - basically niemeyer and I have no clue what's wrong in there
[16:29] <ttx> nurmi: please comment on the bug when done, and do not hesitate to sync with mathiaz for reproduction
[16:29] <mathiaz> nurmi: so any help in debugging this is welcome
[16:30] <mathiaz> ttx: that was it
[16:30] <ttx> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=uec-images
[16:30] <nurmi> mathiaz: niemeyer: great, just quick question
[16:30] <ttx> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=ec2-images
[16:30] <ttx> smoser: ^
[16:30] <nurmi> mathiaz: are you running as 'admin' or regular user for commands listed in that bug?
[16:30] <mathiaz> nurmi: admin
[16:30] <nurmi> mathiaz: thanks
[16:30] <smoser> we're  no different than last week as far as bugs for those. there is nothing open that is serious.
[16:30] <mathiaz> nurmi: I've tried regulart as well - same outcome
[16:30] <nurmi> mathiaz: nod
[16:31] <ttx> smoser: bug 440757 is targeted to release, what's the status ?
[16:31] <smoser> bug 439868 and bug 444598 are done. those were most of my work last week. but they're heavily improved now.
[16:32] <smoser> i was just looking at 440757 now. i will try to knock that off today.
[16:32] <ttx> smoser: ETA for bug 444605 ?
[16:32] <smoser> and i'm going to open one for putting acpiphp into /etc/modules
[16:32] <smoser> i will mark 444605 as done.
[16:32] <ttx> ok, cool.
[16:33] <ttx> anything else on the EC2/UEC topic ?
[16:33] <smoser> slangasek, agreed that with the -kernel-info.txt file and even just the manifest we have what we need.
[16:33] <ttx> [TOPIC] Virtual appliance
[16:33] <MootBot> New Topic:  Virtual appliance
[16:33] <ttx> the biggest issue is the one mathiaz already mentioned
[16:34] <ttx> niemeyer: anything else you wanted to report ?
[16:35] <ttx> moving on...
[16:35] <ttx> [TOPIC] Other specs from the Roadmap
[16:35] <MootBot> New Topic:  Other specs from the Roadmap
[16:35] <ttx> https://wiki.ubuntu.com/ServerTeam/Roadmap
[16:35] <ttx> anything else / anyone ?
[16:36] <ttx> [TOPIC] Server Team bugmail
[16:36] <ttx> zul ^
[16:36] <MootBot> New Topic:  Server Team bugmail
[16:37] <zul> yeah so I went through the server-ship seeds to make sure that the server team is subscribed to the bugmail for the stuff in the seeds and this is the list I came up with
[16:37] <zul> http://pastebin.ubuntu.com/292428/
[16:37] <MootBot> LINK received:  http://pastebin.ubuntu.com/292428/
[16:37] <zul> some like freenet6 are no longer in the archive and should be removed from the seeds as well
[16:38] <Daviey> zul: What is the ($team/perosn) after the package name?
[16:38] <zul> Daviey: these are the people subscribed to the bugs
[16:38] <Daviey> ah
[16:38] <zul> I was going to propose that I would go through the list today and make sure that the server team is subscribed to the package in launchpad and triaged any new bugs
[16:39] <ttx> postgresql is quite obvious, methink
[16:39] <ivoks> does it need to be surbscribed to parts that are covered by, for example, ubuntu-ha?
[16:39] <zul> ttx: obviously yes
[16:39] <Daviey> if it's in the server seed, surely we should be subscribed to the packages bugs?  As in, shouldn't we just action them all?
[16:39] <zul> ivoks: no I dont think so
[16:39] <ivoks> i'd agree
[16:40] <mathiaz> ivoks: both teams can be subscribed to the bugs
[16:40] <zul> ivoks: but it would be nice to have a backup
[16:40] <ivoks> mathiaz: meaning ubuntu-ha members would recieve double email
[16:41] <Daviey> it *concerns* the server team as it's in the seed.. but inversely we already get lots of bugmail..
[16:41] <Daviey> ivoks: they need to filter their mail better :)
[16:41] <ttx> ivoks: I'd recommend not subscribing to ubuntu-server bugmail anyway
[16:41] <mathiaz> ivoks: oh well. This is why treading emails clients are useful ;)
[16:41] <ivoks> :)
[16:41] <ttx> package subscription is more about getting the package to show in our buglists
[16:42] <ttx> mathiaz: any objection to adding all of them, since they are in server-ship ?
[16:42] <mathiaz> ttx: nop
[16:42] <mathiaz> ttx: E
[16:42] <ttx> zul: please clean up and proceed
[16:43] <zul> ttx: ok
[16:43] <mathiaz> ttx: I'm trying to reach the 2000 emails /day bar - adding more packages should help achieving that goal
[16:43] <ttx> [ACTION] zul to add missing server-ship packages to ubuntu-server
[16:43] <MootBot> ACTION received:  zul to add missing server-ship packages to ubuntu-server
[16:43] <ttx> [TOPIC] RC - FinalFreeze ahead
[16:43] <MootBot> New Topic:  RC - FinalFreeze ahead
[16:43] <ttx> so FinalFreeze is this thursday
[16:44] <ivoks> cr@p
[16:44] <ttx> which means most fixes should be in by... tomorrow
[16:44] <ttx> only release-critical fixes will be granted an exception after that date
[16:44] <nijaba> or ask for an exception?
[16:45] <ivoks> how do we look on workarounds for upstream bugs?
[16:45] <ivoks> i'm facing one bug that's very bad, bad a workaround 'fixes' it
[16:45] <smoser> soren, are you planning on refreshing vmbuilder ? there have been changes since the last karmic release.
[16:45] <ivoks> i was waiting for a fix, but i guess we can't wait any longer
[16:46] <ttx> if its a very bad bug it could get an exception
[16:46] <ivoks> upstream is working on it, but problably won't be here in next week
[16:46] <ttx> ivoks: make sure its on the release team radar though
[16:46] <ttx> ivoks: nominated for karmic and targeted to release
[16:46] <ivoks> ttx: but i'd push workaround, just in case... is that ok?
[16:46] <ttx> ivoks: sure, workarounds are... good
[16:47] <ttx> as already mentioned, we'll have a server bug day tomorrow
[16:47] <ttx> to identify the missing bugs that should be targeted to release
[16:47] <ttx> everyone is welcome to participate, this is a great way of ensuring a better quality release
[16:48] <ttx> Any other question on this topic ?
[16:48] <nijaba> Where can one find more information about this?
[16:48] <ttx> pedro_: ^
[16:48] <ttx> https://wiki.ubuntu.com/UbuntuBugDay/20091014
[16:48] <nijaba> thanks
[16:49] <ttx> and Pedro should send a mail about it, if not done already
[16:49] <ttx> Bloggers can annouce it too :)
[16:49] <ttx> [TOPIC] Assigned and to-be-assigned bugs
[16:49] <MootBot> New Topic:  Assigned and to-be-assigned bugs
[16:49] <ttx> http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html
[16:49] <MootBot> LINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html
[16:50] <ttx> still slightly outdated, can't keep up with our hasty pace
[16:50] <ttx> team: any bug that you don't feel confident about, please talk
[16:50] <ttx> Anything needing reassignment, please talk as well
[16:51] <nijaba> I would like to submit bug #328550 to a review. I think it is pretty bad that we do not support HBA out of the box
[16:51] <ttx> Looking...
[16:52] <nijaba> it has been verified on Karmic too
[16:52] <ttx> I'll have a look, but it looks like Foundations territory
[16:53] <ttx> [TOPIC] Weekly SRU review
[16:53] <MootBot> New Topic:  Weekly SRU review
[16:53] <ttx> this week we have some time for it, mathiaz ^
[16:53]  * mathiaz cheers
[16:53] <ttx> mathiaz: 5 minutes, nominations lists are empty, fwiw
[16:53] <mathiaz> http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[16:53] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[16:53] <zul> i have three on my radar 343870 304437 425407
[16:54] <mathiaz> ^^ any bugs worth SRU?
[16:54] <zul> 425407
[16:54] <zul> 304437
[16:54] <zul> 343870
[16:54] <mathiaz> bug 425407
[16:54] <zul> damn no bot
[16:54] <mathiaz> bug 304437
[16:54] <mathiaz> bug 343870
[16:54] <ttx> zul: yes, just talk to them :)
[16:55] <zul> heh
[16:55] <ttx> zul: ok, nominate them. Though at this moment working on SRU is prio -1
[16:55] <zul> ttx: okies
[16:56] <mathiaz> ok - all the nominated lists are emtpy
[16:56] <mathiaz> http://qa.ubuntu.com/reports/ubuntu-server-team/acceptedbugs.ubuntu-server.latest.html
[16:56] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/acceptedbugs.ubuntu-server.latest.html
[16:56] <mathiaz> zul: how are things moving on these?
[16:56] <zul> slowly as usual
[16:57] <ttx> zul: you should assign yourself to those you intend to fix in a reasonable timeframe, so that others can have a shot at them
[16:57] <zul> ttx: they are all uploaded to proposed its just getting people to test them
[16:57] <zul> or getting feedback for them
[16:57] <ttx> oO
[16:57] <ttx> impressive
[16:57] <mathiaz> ok
[16:58] <mathiaz> zul: did you start to use bzr branches?
[16:58] <mathiaz> https://code.launchpad.net/~ubuntu-server/+activereviews
[16:58] <mathiaz> ^^ there are a couple of them here
[16:58] <zul> mathiaz: I did!
[16:58] <mathiaz> zul: has the ipsec-tools SRU branch been reviewed?
[16:58] <zul> mathiaz: none have been reviewed
[16:59] <mathiaz> zul: sbeattie should have a look at them
[16:59] <zul> mathiaz: ill bug him about it
[16:59] <ttx> [TOPIC] Open Discussion
[16:59] <MootBot> New Topic:  Open Discussion
[16:59] <mathiaz> zul: you can just add him a reviewer
[16:59] <ttx> 1 minute of open discussion ...
[16:59] <zul> mathiaz: sure
[17:00] <ttx> anything on anyone's mind ?
[17:00] <ttx> [TOPIC] Agree on next meeting date and time
[17:00] <MootBot> New Topic:  Agree on next meeting date and time
[17:01] <ttx> Our rescheduling effort is a total failure, so next week, same time same place :)
[17:01] <mathiaz> ttx: total ??
[17:01] <nijaba> yep...
[17:01] <mathiaz> ttx: I'd say - it's under way
[17:01] <ttx> mathiaz: its because you have some optimism left in you ;)
[17:01] <mathiaz> ttx: :)
[17:02] <smoser> i think mathiaz needs to write a replacement for that scheduler that recognizes daylight savings time.
[17:02] <ttx> btw, look at waht the wonderful Desktop team does: https://wiki.ubuntu.com/DesktopTeam/MeetingTime
[17:02] <mathiaz> smoser: sure ... done - it's called...
[17:02] <mathiaz> smoser: ... pen and paper
[17:02] <zul> i would say ongoing
[17:03] <smoser> mathiaz, i'll mail you my schedule today
[17:03] <ttx> mathiaz: could we use something like that ?
[17:03] <mathiaz> ttx: seems like a good plan
[17:03] <mathiaz> ttx: if that improves the current situation - the doc team was using something similar
[17:04] <ttx> mathiaz: they are so great.
[17:04] <mathiaz> ttx: it won't solve the DST time issue so
[17:04] <mathiaz> ttx: it won't solve the DST time issue *though*
[17:04] <ttx> mathiaz: but you can wiki-edit it when that time comes
[17:04] <mathiaz> ttx: agreed - I'll create a similar wiki page for the server tema
[17:04] <zul> damn farmers
[17:04] <ttx> #endmeeting
[17:05] <MootBot> Meeting finished at 11:04.
[17:05] <mathiaz> ttx: and we'll see if that becomes *a* *total* *failure* as well
[17:05] <ttx> thanks everyone
[17:05]  * nurmi waves and thanks all 
[17:05] <ttx> nurmi: I have a question for you, -> #ubuntu-server
[17:58]  * cking shuffles in
[17:58] <lieb> It's raining cats&dogs here so I guess I'm wading in
[17:59]  * amitk waddles in
[17:59]  * apw zones out
[17:59]  * jjohansen here
[17:59] <bjf-afk> Roll Call
[17:59]  * manjo in
[18:00]  * cking here
[18:00] <apw> here
[18:00]  * amitk here
[18:00]  * rtg waves
[18:00]  * lieb here
[18:00]  * sconklin waves
[18:00] <bjf> #startmeeting
[18:00]  * pgraner \o/
[18:00] <MootBot> Meeting started at 12:00. The chair is bjf.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:00]  * smb is late
[18:01] <bjf> [TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs
[18:01] <MootBot> New Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs
[18:01] <ogasawara> just a sec
[18:01] <bjf> :-)
[18:01] <ogasawara> Release Meeting Bugs (13 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:01] <ogasawara> [18:01] <ogasawara> RC Milestoned Bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs?field.milestone%3Alist=12698
[18:01] <ogasawara>  * 3 linux kernel bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux/+bugs?field.milestone%3Alist=12698
[18:01] <ogasawara>  * 5 linux-fsl-imx51 bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux-fsl-imx51/+bugs?field.milestone%3Alist=12698
[18:01] <ogasawara>  * 1 linux-ec2 bug - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux-ec2/+bugs?field.milestone%3Alist=12698
[18:01] <rtg> bjf, just uploaded 2.6.31-14.46. If the bug fixes aren't in there, then they likely won't make it.
[18:01] <ogasawara>  * 2 linux-mvl-dove bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux-mvl-dove/+bugs?field.milestone%3Alist=12698
[18:01] <ogasawara> [18:01] <ogasawara> * Release Targeted Bugs (17 bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:01] <ogasawara>  * 14 linux kernel bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:02] <ogasawara>  * 7 linux-fsl-imx51 bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux-fsl-imx51
[18:02] <ogasawara>  * 1 linux-ec2 bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux-ec2
[18:02] <ogasawara>  * 2 linux-mvl-dove bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux-mvl-dove
[18:02] <ogasawara> Milestoned Features - https://edge.launchpad.net/ubuntu/+milestone/ubuntu-9.10
[18:02] <bjf> anyone want to comment on any of that?
[18:02] <pgraner> Yea
[18:03] <pgraner> Keeping with what rtg said just a sec ago
[18:03] <rtg> If the bug fixes aren't in there, then they likely won't make it.
[18:03] <rtg> that one?
[18:03] <pgraner> We need to touch every one of these bugs and retarget for post release
[18:03] <pgraner> rtg: yep
[18:03] <bjf> we got a FSL patch about 45 minutes ago that fix two imx51 bugs
[18:03] <amitk> can we get an upload for arm?
[18:03] <apw> lets hope some of them close as it releases
[18:03] <pgraner> or make a decision if they will every get fixed
[18:03] <apw> the arm uploads are waiting on you
[18:04] <pgraner> s/every/ever/
[18:04] <rtg> still have to upload EC2 yet today
[18:04] <apw> i am rebaseing them to the latest upload now, then i'll touch you for the patches
[18:05] <bjf> apw, its a single, trivial patch
[18:05] <pgraner> Ok, let talk ARM & EC2 at the proper agenda items
[18:05] <bjf> pgraner, can we move on?
[18:05] <pgraner> The bottom line is we need to have a disposition on all the bugs that ogasawara listed ASAP
[18:05] <pgraner> I'd like to see it prior to freeze if possible
[18:06] <rtg> certainly before steve builds his release meeting agenda
[18:06] <pgraner> rtg: exactly
[18:06] <amitk> what day is that?
[18:06] <rtg> Friday
[18:06] <bjf> pgraner, we (amit and I) were asked to report arm bug status in this meeting (we have 4 bugs to discuss)
[18:06] <pgraner> amitk: usually Thurs night
[18:06] <amitk> pgraner: ack
[18:06] <pgraner> bjf: understood
[18:07] <pgraner> bjf: this was more about the overall targeting of the stragglers
[18:07] <bjf> pgraner, ack
[18:07] <pgraner> bjf: lets keep it moving
[18:07] <bjf> [TOPIC] Karmic Release Status: ARM Bugs
[18:07] <MootBot> New Topic:  Karmic Release Status: ARM Bugs
[18:07] <bjf> bug 427289 bug 446140 bug 431963 bug 450363
[18:08] <bjf> Just before the meeting I received a patch from Nguyen Dinh, a fsl engineer, that seems to fix both the regulator and RTC bugs.
[18:08] <bjf> I've not looked at the io/fs errors with sata bug.
[18:08] <bjf> I'll get onto 450363 today and do another, general, review of the config options for dove.
[18:08] <bjf> that's all from me, Amit?
[18:08] <amitk> i suspect the sata issues could be related to the regulator issues but since it shows up for only a single user, it is awaiting his testing
[18:09] <bjf> [TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:09] <MootBot> New Topic:  Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:09] <rtg> bjf, uh, weren't we gonna drop this item for now?
[18:10] <bjf> [ACTION] bjf to drop from agenda
[18:10] <MootBot> ACTION received:  bjf to drop from agenda
[18:10] <bjf> [TOPIC] Blueprints: kernel-karmic-suspend-resume (manjo)
[18:10] <MootBot> New Topic:  Blueprints: kernel-karmic-suspend-resume (manjo)
[18:10] <manjo> nothing to report there
[18:10] <bjf> [TOPIC] Other Release Tasks: AppArmor (jjohansen)
[18:10] <MootBot> New Topic:  Other Release Tasks: AppArmor (jjohansen)
[18:10] <jjohansen> closed out 415632
[18:10] <apw> bug 415632
[18:11] <jjohansen> still looking at  40f71028
[18:11] <apw> whats that then?
[18:11] <jjohansen> and 446524, with kees
[18:11] <rtg> jjohansen, thats an odd number, 40f71028
[18:11] <jjohansen> sorry 4071028
[18:12] <apw> bug
[18:12] <apw> bug 4071028
[18:12] <apw> bug 446524
[18:12] <jjohansen> oops, paste is not working so well just a sec
[18:12] <jjohansen> bug 446118
[18:13] <jjohansen> I need to also finishing doing some updates to AA, and repost to LKML this week
[18:14] <bjf> [TOPIC] Other Release Tasks: ARM-Freescale/Marvell (amitk, bjf)
[18:14] <MootBot> New Topic:  Other Release Tasks: ARM-Freescale/Marvell (amitk, bjf)
[18:14] <bjf> dove is stable, no new updates from MVL
[18:14] <apw> we have one patch pending yes?
[18:14] <apw> a config change?
[18:14] <bjf> apw, working on it, a config change
[18:14] <rtg> bjf, Freescale is a different story I hear?
[18:15] <amitk> on vacation last week so only looked at imx51 status since yesterday.
[18:15] <bjf> rtg, yes, other than the fix that just came in, there are a few bugs
[18:15] <amitk> a sound bug and ethernet driver bug were fixed by bjf (FSL patches) and jeremy
[18:15] <bjf> it looks like the patch we just got didn't fix all the regulator issues, but maybe enough for now
[18:15] <amitk> and two more will likely get fixed with the patch that bjf mentioned
[18:16] <bjf> [TOPIC] Other Release Tasks: EC2 Karmic Kernel Status (jjohansen)
[18:16] <MootBot> New Topic:  Other Release Tasks: EC2 Karmic Kernel Status (jjohansen)
[18:17] <jjohansen> The rebased kernels passed smoke testing
[18:17] <rtg> jjohansen, another rebase coming today.
[18:17] <jjohansen> and I haven't received any feedback on the virtual config kernels I built
[18:17] <jjohansen> rtg: yep, I will test as soon as it hits
[18:18] <rtg> I'll git 'er done right after the meeting
[18:18] <bjf> [TOPIC] Status: Karmic (rtg, apw)
[18:18] <MootBot> New Topic:  Status: Karmic (rtg, apw)
[18:18] <rtg> bjf, it compiles, ship it.
[18:18] <apw> karmic just got some more stable updates
[18:19] <bjf> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:19] <MootBot> New Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:19] <smb> * Dapper:   2.6.15-54.79 (security)
[18:19] <smb> * Hardy:    2.6.24-24.61 (updates)
[18:19] <smb> * Intrepid: 2.6.27-14.41 (updates)
[18:19] <smb> * Jaunty    2.6.28-15.52 (updates)
[18:19] <smb> (yes its exactly the same as last week)
[18:19] <smb> There is a new security release in the works which ogasawara was handling this
[18:19] <smb> time. Thanks!
[18:19] <bjf> [TOPIC] Incoming Bugs: Regressions (ogasawara)
[18:19] <MootBot> New Topic:  Incoming Bugs: Regressions (ogasawara)
[18:19] <ogasawara> Current regression stats:
[18:19] <ogasawara>  * regression-potential bugs: 36 (down 3) https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-potential
[18:19] <ogasawara>  * regression-release bugs: 42 (up 1)  https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-release
[18:19] <ogasawara>  * regression-update bugs: 9 (down 1)  https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-update
[18:19] <ogasawara>  * regression-proposed: 0 (no change) https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-proposed
[18:20] <bjf> any discussion?
[18:20] <apw> ogasawara, do these stats
[18:20] <apw> give you the real closed stats in down, or a week on week delta
[18:20] <ogasawara> apw: week on week delta
[18:20] <apw> any way we can get the former perhaps?
[18:20] <ogasawara> apw: yup, should be easy enough
[18:21] <bjf> [TOPIC] Incoming Bugs: Bug day report (ogasawara)
[18:21] <MootBot> New Topic:  Incoming Bugs: Bug day report (ogasawara)
[18:21] <ogasawara> http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090929.html
[18:21] <ogasawara> Off to a good start, 35% (88 bugs) have already been worked on
[18:21] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090929.html
[18:21] <apw> with it being kernel-in-the-can day i think we've been distracted
[18:22] <ogasawara> apw: I was actually surprised to see that many worked on
[18:22] <bjf> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:22] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:22] <bjf> once
[18:23] <bjf> twice
[18:23] <cking> ogasawara, was that an old link?
[18:23] <ogasawara> cking: oops, indeed.  should be http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20091013.html
[18:23] <apw> [link] http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20091013.html
[18:23] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20091013.html
[18:24] <bjf> that sound like that's all
[18:24] <bjf> #endmeeting
[18:24] <MootBot> Meeting finished at 12:24.
[18:24] <smb> \o
[18:24] <lieb> bye'
[18:24] <cking> ttfn
[18:24] <amitk> thanks
[21:05] <lifeless> persia: doh; jetlagged last night
[21:05] <lifeless> elky: ^
[21:06] <lifeless> please feel free to SMS me if I'm not around for a meeting
[21:06] <lifeless> I may be reachable and just failing at memory
[23:36] <elky> lifeless: email me your mobile number at your next convenient moment. i don't seem to have it any more.
[23:52] <lifeless> elky: pst'd. its also on facebook :P
[23:52] <elky> i dont think i've touched facebook in weeks, heh