/srv/irclogs.ubuntu.com/2009/08/25/#ubuntu-meeting.txt

=== bdrung_ is now known as bdrung
=== maco_ is now known as MsMaco
=== mdz_ is now known as mdz
=== dholbach_ is now known as dholbach
=== fader|away is now known as fader
=== cjwatson_ is now known as cjwatson
=== freeflyi2g is now known as freeflying
InDuShi i hope iam not gatecrashing13:50
InDuSwho can tell me how i can become an ubuntu member13:50
czajkowskihttp://www.ubuntu.com/community/processes/newmember   https://wiki.ubuntu.com/Membership13:50
czajkowskiInDuS: either of those links should help you out13:51
InDuSok i did all that13:51
InDuSso i was told to come here after those13:51
InDuSi created my page etc13:51
InDuSalso, i promote foss in my country etc13:52
InDuSthat membership page says to apply in there ,but i cant find any links to do so13:53
GrueMasterThere is an ubuntu-mobile meeting scheduled to start in 6 minutes.  You can bring it up during that meeting, when it is time for new business.13:54
InDuSubuntu-mobile meeting? hmm whats that about?13:54
GrueMasterStick around and find out.13:55
InDuSok13:55
czajkowskiInDuS: please see pm or come into #ubuntu-locoteams13:55
loolHey all13:59
loolNCommander: Around?14:00
NCommander#startmeeting14:00
MootBotMeeting started at 08:00. The chair is NCommander.14:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:00
NCommanderlool, yes, I'm just kinda noe feeling very good14:00
looldyfet, persia, paulliu, ogra, plars: ping14:00
plarsGrueMaster: I think he's talking general membership, not just mobile14:00
* plars is here14:00
ograpoop14:00
loolpoop yourself!14:00
ogra:)14:00
paulliulool, hi14:00
* GrueMaster props eyes open with toothpicks.14:01
* NCommander snores loadly14:01
NCommanderok14:01
GrueMasterloadly?14:01
StevenKApparently NCommander is loaded14:01
ograbetter than yodely14:01
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090811?action=edit&editor=text14:02
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090811?action=edit&editor=text14:02
loolNCommander: I added a couple of entries to the roadmap which I'll explain when we get there14:02
lool[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/2009081114:02
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/2009081114:02
NCommanderoh14:02
NCommanderthanks14:02
plarsbetter14:02
plars:)14:02
NCommander[topic] Action Item Review14:02
MootBotNew Topic:  Action Item Review14:02
NCommander[topic] NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co)14:02
MootBotNew Topic:  NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co)14:02
ubottuLaunchpad bug 338148 in vnc4 "Needs new version from Debian: fails to build with removal of mesa-swx11-source" [High,Triaged]14:02
NCommanderc/o yet again, this bug is up for grabs if anyone wants it14:03
loolNCommander: What needs to happen so that you can make progress on it?14:03
loolI think it's basically calling for a merge14:03
NCommanderlool, time, its not a trivial merge14:03
loolOk14:04
NCommanderlool, it requires sucking in the X11 headers, and it isn;'t very clear how it comes together14:04
NCommander[topic] !GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/33780914:04
MootBotNew Topic:  !GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/33780914:04
ubottuLaunchpad bug 337809 in linux "APIC error on CPU 0" [Medium,Triaged]14:04
GrueMasterThis requires me setting up my CrownBeach again.  Very low priority (unless someone says otherwise).14:04
* NCommander wonders if we should just remove it from the list14:05
NCommander[topic] Specification Review14:05
MootBotNew Topic:  Specification Review14:05
lool[link] http://people.canonical.com/~lool/mobile-status.html14:05
MootBotLINK received:  http://people.canonical.com/~lool/mobile-status.html14:05
NCommanderThank you lool14:06
ograoutdated !14:06
NCommanderthat too14:06
loologra: Is it really?14:06
loologra: Which spec?14:06
* NCommander had status changes last night ...14:06
ograboth of mine i updated status this morning14:07
ograyou should really run the update before the meeting14:07
NCommander[topic] lool's status14:07
MootBotNew Topic:  lool's status14:07
ograoutdated :P14:08
loologra: Oh right, I'm still running the generation daily and pushing more frequently14:08
loolPushing an updated one14:08
looldone14:08
ograthanks14:08
loolNCommander: I think we wanted to ultimately drop per people status14:08
loolOk now we have this page with the status of each spec as reported by each owner14:09
ograhmm, it doesnt respect linewraps in the Status entry14:09
loolThe idea is that everybody opens it, takes a look and asks any question14:09
* ogra needs to take that into account14:09
* NCommander much perfered us just giving a quick status line each meeting but ok ...14:09
plarsI have a question about https://blueprints.launchpad.net/ubuntu/+spec/mobile-karmic-arm-cloud-builds14:10
loolI actually started writing real code to my cloud builder, but it's not dong anything useful yet14:10
loolOh good timing14:10
plarshaha14:10
loolplars: So I kept deferring work on it, but I really believe it's useful and I started architecting the source code and playing with boto code samples14:11
plarslool: cool, so that answers my first question of "is this expected to happen this cycle?"14:11
loolBut it doesn't advance the spec significantly14:11
loolI'll update it when I have a first pass to push14:11
loolI expect the first thing will be creating a couple of vms and tracking their status in a local sqlite14:11
plarslool: the spec says approved, but there are not valid work items on the whiteboard, so I was kinda confused by what kind of shape it was in14:11
loolAnd start/stop basically14:11
loolplars: Hmm good point I need to add valid work items to that one; I forgot about it when it got off the list of specs in error14:12
loolplars: Thanks for pointing it out, I'll document them14:12
loolHmm nobody told me but the counts in the second column are wrong too14:12
loolI need to fix my SQL14:12
ograi have one about softbootloader: i had a task to review the softbootloader spec, lool nicely reminded me of that today, i looked at it but the UDS discussion was never merged or taken into account it seems, there are external and team internal action items listed in the BOF discussion, what happens to them ?14:13
loologra: I guess we list them all as work items and the spec owner is in charge of proding the other people to make progress on them14:13
ograquite late for that imho14:13
NCommanderogra, the way we discussed at UDS, and what happened in reality went in two very separate directions. I need to rewrite the spec to match reality (or change reality to match UDS)14:13
ograright, thats clear, what wasnt clear to me were the four action items that even have personal assignments at the bottom of the BOF discussion14:14
loologra: I hate the fact that this spec got deferred from jaunty and we actually would have benefited from it in a couple of cases already14:14
ograyes, indeed14:15
ograand i'm happy to research my action item, but it showed never up on my todo list14:15
loologra: That said during the sprint I sat down with NCommander to document actual work items in the wb14:15
loolI'm not sure you have one in that list14:16
NCommander[action] NCommander to redraft softbootloader spec to make it match reality and clear up action item list14:16
MootBotACTION received:  NCommander to redraft softbootloader spec to make it match reality and clear up action item list14:16
loolNCommander: Thanks14:16
ogralool, because the spec was never updated with the discussion notes from last UDS14:16
loolAre there other questions on the status of specs?  Everybody done digesting?14:16
NCommanderlool, are you going to be around in say an hour to help merge the d-cd code and stuff?14:17
GrueMasterwhat's the scoop on mobile-karmic-moblin-remix?14:17
loolNCommander: I have meetings all afternoon14:17
NCommanderlool, bugger14:17
loolNCommander: I accepted the task on monday and will do it sometime this week14:17
NCommanderogra, how about you?14:17
ogralool, did you talk to tbm ?14:17
loolBut I cant be bothered to do it right now14:17
loologra: No14:17
NCommanderlool, right, I understand, I'd just like to nip this in the bud14:17
ograNCommander, thats only adding the two new files, right ?14:17
loolPeople might remember me calling them the whole of yesterday too?   :)14:18
ografine to merge that if it doesnt touch other code14:18
NCommanderogra, two new files, and then a modification to make-web-indices to add the dove14:18
loolMe being davidm's fallback means my number of meetings basically doubled14:18
ograwasnt that already there ?14:18
ograi'll look at it14:18
loologra: The idea was of course to review the actual image creation script14:18
ogralool, indeed14:19
NCommanderogra, very cool. I am expecting dove squashfs's to build (they almost built yesterday so ...)14:19
ograi took a glance on the weekend already14:19
ograbuild is in progress14:19
loolNCommander: You actually pasted a meeting URL from Aug 11th at the beginning of the meeting instead of today's14:19
NCommanderI need to poke the kernel team though on the dove .config; I think initramfs support fell off14:19
lool[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090825 is the proper one14:19
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090825 is the proper one14:19
NCommanderlool, >.<;14:19
NCommanderlool, sorry, I'm suffering from a massive migrane at the moment and the world kinda fuzzy14:20
loolI'm removing the crap in the wiki page too14:20
loolNCommander: Hmm why is there no entry to review roadmap stuff?14:20
lool[link] https://wiki.ubuntu.com/MobileTeam/Roadmap14:21
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap14:21
loolI dumped a couple of things on this page, it looks ugly -- I know14:21
NCommanderlool, I thought we stopped using that14:21
loolWhat I'd like us to do is to periodically check we didn't miss any desktop seeds updates14:21
loolor aren't missing any UNR upstream release14:21
StevenKI have been14:21
StevenKI also do that14:21
loolStevenK: Ok, so status is that we're all up-to-date and can close this topic?14:22
StevenKlool: When my u-n-r-d-s gets uploaded, yes14:22
loolStevenK: (I added these entries due to critics on missing desktop features in UNR; I expect it will disappear once we move this to the integration meeting)14:22
loolStevenK: Ok, so just pending an u-n-r-d-s upload; thanks14:22
GrueMasterHas gwibber been added to the seed yet?  How about removing xscreensaver-gl?14:22
StevenKYes, but it won't appear14:23
loolGrueMaster: We're waiting for a new gwibber, 2.0, so that we can promote the new one to main14:23
StevenKgwibber is in universe14:23
GrueMasterah14:23
GrueMasterETA?14:23
loolStevenK: I'm fearing this might not make it before FF  :-/14:23
loolGrueMaster: It's in the hands of Ken van Dine14:23
ograwell, thats what we have an exception process for14:24
loolI'd like us to take a glance at high importance bugs14:24
loolStarting with UNR14:24
lool[link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr14:24
MootBotLINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr14:24
loolStevenK: 417001 is the one you're about to upload, right?14:24
StevenKlool: Right14:24
StevenKlool: I wasn't going to close it until FUSA is sorted out14:25
loolStevenK: Isn't LP #410655 fixed with new clutk?14:25
ubottuLaunchpad bug 410655 in netbook-launcher "netbook-launcher crashed with SIGSEGV in IA__g_type_check_instance_is_a()" [High,Triaged] https://launchpad.net/bugs/41065514:25
ogranew FUSA landed today btw14:25
loolStevenK: Ok fair enough14:25
ogra"indicator-session"14:25
StevenKlool: Not sure, it looks like a different stacktrace14:25
loolStevenK: Ok; can you make sure you track this with njpatel before A5?14:25
StevenKRight14:26
loolarmel bugs next I guess14:26
lool[link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel14:26
MootBotLINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel14:26
loologra: How goes with 417009?14:26
looloo.o14:26
ograi didnt contact mterry yet ... we only discussed it last night14:26
loolOk14:26
ograwill do so after them meeting assuming he is up now14:26
njpatellool: StevenK: I'm working on that...it's a bit strange14:27
loologra: tomboy?  39112414:27
=== imlad|away is now known as imlad
StevenKnjpatel: Ah, nice14:27
loolnjpatel: Thanks for the update; can you assign yourself to the bug?14:27
njpatelwill do14:27
ograwell, seems like its deeper down in the mono stack and i'd really like to know what dyfet found14:27
ograsince he said he dug deep into mono and found issues during his banshee research14:27
loologra: It looks like dyfet isnt around though (probably sick); if you have spare cycles to chase this it might be clever to start on it14:28
lool391588 I'll skip since it's both non-critical and assignde to dyget14:28
lool*dyfet14:28
ograwell, someone from the mono team asked for another debug output today14:28
ograi added that14:28
lool383240 is mine; I suck, it's been assigned to me for weeks but I didn't find a large enough slot to just do it14:28
lool385325 is blocked on clarifying the plan with asac14:29
ograthere is a plan for karmic ?14:29
GrueMasterI'm surprised Bug #418265 didn't show up on the list.14:29
ubottuLaunchpad bug 418265 in linux "Warning in ehci-hcd.c:911 on kernel 2.6.31-5-imx51" [Medium,Triaged] https://launchpad.net/bugs/41826514:29
ograi thought we'd just update to new upstream14:29
ogra2.6.31-5-imx51"14:29
ogra?14:29
ograthats totally not buggable14:29
StevenKGrueMaster: Is ubuntu-armel subscribed to the bug?14:30
ograclose it as invalid and wait for a proper kernel14:30
GrueMasteryes14:30
StevenKGrueMaster: If the team isn't, thqat14:30
* StevenK sighs at this keyboard14:30
loolGrueMaster: Only karmic targetted bugs show up there14:30
GrueMasterah14:30
ograwell, but please ignore imx51 kernels that dont have a 100 in the ABI14:30
GrueMasterThis was on Friday's image.14:31
loolGrueMaster: source package is linux-fsl-imx51, not linux14:31
ograeverything before that is missing about 130 patches14:31
looltargeted at karmic now14:31
ogralool, not for 2.6.31-5-imx51 ...14:31
loolSure enough it shows up on the list now14:31
ograthere linux is right14:31
loolGrueMaster: Can you please retest with latest kernel from linux-fsl-imx51?14:31
loolShould have a >100 ABI14:31
ogramarked as invalid14:32
GrueMasterIf it is in the latest image, sure.14:32
loolGrueMaster: It is14:32
ograthere are *no fsl patches at all* in 2.6.31-5-imx51 only one that enables the basics14:32
loologra: I'd rather call it incomplete14:32
loolanyway14:32
ograno14:32
looldoesn't matter, needs retesting and can be reopened14:33
ograright14:33
loolNext week is A514:33
lool[link] https://launchpad.net/ubuntu/+milestone/karmic-alpha-514:33
MootBotLINK received:  https://launchpad.net/ubuntu/+milestone/karmic-alpha-514:33
loolSpecs targetted there are the toolchain one (will change just after A5)14:33
loolSupport for Ubuntu Desktop on Freescale SoCs ; should be ok14:34
loolSupport for Ubuntu Desktop on Marvell SoCs ; pending a debian-cd merge and I'd expect final fixes14:34
loolNCommander: Do we have instructions in testing the marvell images?14:34
NCommanderlool, our kernel lacks initramfs support ATM (found that out last night), so even when we get images, they are unbootable out of the box14:35
loolNCommander: Which bug is that?14:35
NCommanderlool, I'm filing one now, since I just confirmed that was the issue about 10 minutes ago14:35
loolNCommander: This is critical to A5; please file + milestone + ping rtg + amitk + bjf14:35
loolNCommander: Action on you to document testing instructions?14:36
loolSince we dont have a custom uboot on the boards14:36
loolGrueMaster: Determine if any default applications should be changed in UNR14:36
loolGrueMaster: It looks like it's not going to make A5 given the number of open actions14:36
NCommander[action] Document livecd bringup for the dove boards14:36
MootBotACTION received:  Document livecd bringup for the dove boards14:36
NCommander[action] NCommander to ocument livecd bringup for the dove boards14:36
MootBotACTION received:  NCommander to ocument livecd bringup for the dove boards14:36
loolGrueMaster: The only item there for you is the CD image size work14:36
loolGrueMaster: But I think it would be good if you'd personally chase people to implement the actions14:37
loolaka nag  :)14:37
StevenKWhich I'm still waiting on14:37
GrueMasterI can't really do that until the other two items are done.14:37
loolGrueMaster: We all know you're good at nagging us  :)14:37
GrueMasterOk then.  StevenK, NAG - get on removing the xscreensaver-gl and other items on your TODO list.14:38
ograrss-glx too14:38
loolStevenK: You have action to drop xscreensaver stuff from the seed and to add gwibber to maximus blacklist; do you think you could do that this week?14:38
GrueMasterIs there any reason not to seed gwibber before 2.0?14:38
ograthats way bigger iirc14:38
StevenKIt is seeded!14:38
loolGrueMaster: Yes, that requires main promotion of stuff which we're not going to need14:38
loolso useless work  :-/14:39
StevenKIt's in the seed list, but germinate won't check universe14:39
StevenKSo there's no point asking me twice to seed it14:39
loolWell ok, it's in the seed text but not in the task14:39
loolWhat we need is promoting it to main when 2.0 comes out14:39
loolStevenK: Do we want a new action to do that in the work items?14:39
StevenKYeah14:40
StevenKI'd like a pointer to the spec, too14:40
loolStevenK: added14:40
NCommanderhttps://bugs.edge.launchpad.net/ubuntu/+source/linux-mvl-dove/+bug/41861814:40
ubottuLaunchpad bug 418618 in linux-mvl-dove "dove kernel lacks support for initramfs" [Critical,New]14:40
loolStevenK: https://blueprints.launchpad.net/ubuntu/+spec/mobile-unr-karmic-applications14:40
GrueMasterSince the size reduction work won't involve desktop application removal, but mostly back-end stuff, it can wait until gwibber 2.0 is on board.14:40
lool[link] https://blueprints.launchpad.net/ubuntu/+spec/mobile-unr-karmic-applications even14:41
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/mobile-unr-karmic-applications even14:41
loolGrueMaster: I dont understand why it should wait?14:41
loolGrueMaster: we want to start getting the ISO size down before we add more stuff to it IMO14:41
loolIt's already too large and we plan adding gwibber14:41
loolThat calls for making room now for the oversize + gwibber's size14:42
GrueMasterSo that I know what my goal for size reduction is.  Otherwise I may need to do that work twice.14:42
StevenKSize reduction may be ongoing14:42
StevenKIt certainly is for the desktop14:42
loolGrueMaster: You want to get below 700 MB to start with and preferably way more; all space saved allows for more langpacks14:42
GrueMasterok14:42
StevenKSo don't count on only doing it once, things change14:42
loolGrueMaster: If you dont know where to start, slangasek has been taking care of ISO size of the desktop14:43
looland others14:43
GrueMasterok14:43
loolGrueMaster: So it might have good advice on where to start looking14:43
lools/it/he14:43
GrueMasterI figure I'd start by diffing the manifests.14:44
ograheh14:44
ogracalling slangasek an "it" is rude :P14:44
loolOk any other things to discuss on A5 tasks?14:44
loolblueprints or bugs14:44
loologra: Yes; typoi  :-(14:44
ograindeed14:44
loolI guess we're done14:45
loolNCommander: Any other topic for today?14:45
NCommander[topic] Any other business14:45
MootBotNew Topic:  Any other business14:45
NCommandergoing once14:45
NCommandertwice14:45
NCommanderthree times14:45
loolI'd like to ask for feedback14:45
loolAre people okay with the meeting changes?14:45
loolAs experienced today14:46
StevenKMy internal jury is still out14:46
ograand i'd like everyone who finds some spare time to regularyx look at http://qa.ubuntuwire.com/ftbfs/14:46
NCommanderI personally perfer going around individually and asking status, then have the open discussion14:46
GrueMasterWell, we're done quicker.14:46
NCommanderGrueMaster, not really14:46
loologra: We could review this if there was an associated timestamp with the FTBFSes14:46
plarswell, we didn't go over, and we're not close to it14:46
ograthere is still a lot armel stuff that can be fixed ...14:46
loologra: Currently the list doesn't show the recent versus old ones14:47
ogralool, well, its always the latest upload14:47
ograonly pointing to the FTBFS logs14:47
NCommanderogra, it doesn't show packages that FTBFS in jaunty that haven't had a karmic upload14:47
loologra: No, I mean we want to look at the recent FTBFS, not all of them, during weekly meetings14:47
loolNCommander: I think it was quicker to do things the way we did and carries the same information14:48
ograwell, that would require to intersect -changes with the versions showing up there14:48
loolExcept people can a) do it before the meeting and b) people can do it async14:48
NCommanderlool, *shrug*14:48
NCommanderAnyone got anything else?14:48
NCommanderI'd like to close the meeting14:48
* ogra likes the new meeting form btw14:48
loologra: No; just keeping track of when the FTBFS was added to this page14:48
ograthough it requires that you prepare indeed14:48
NCommanderIf there's nothing else14:49
NCommanderGoing once14:49
loolI guess we're done14:49
StevenKAnd re-run the generation script :-P14:49
NCommandertwice14:49
ograStevenK, ++14:49
loolStevenK: I switched to @hourly already now14:49
NCommanderthree times14:49
NCommanderStevenK, ++ :-)14:49
NCommanderOk14:49
NCommandereveryone have a good $TIME14:49
NCommander#endmeeting14:49
MootBotMeeting finished at 08:49.14:49
paulliuGrueMaster: Just as same as the Juanty Moblin.14:51
GrueMaster?14:51
=== bdrung_ is now known as bdrung
cjwatsonmdz,Keybuk: TB now?15:02
=== ivoks_ is now known as ivoks
Keybukcjwatson: if you like ;)15:02
Keybukyou're the chair I believe15:02
mdzcjwatson: hi15:03
cjwatsonI do hope not, I chaired last time15:03
cjwatsonwe said we'd decide the chair by e-mail and then I think forgot to do so15:04
cjwatsonby rotation I make it Keybuk's turn15:04
Keybukok15:04
Keybuk#startmeeting15:04
MootBotMeeting started at 09:04. The chair is Keybuk.15:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:04
Keybuk[TOPIC] Per-package uploader application: Yulia Novozhilova (MC mail)15:05
MootBotNew Topic:  Per-package uploader application: Yulia Novozhilova (MC mail)15:05
Keybuk[LINK] https://lists.ubuntu.com/archives/motu-council/2009-August/002183.html15:05
MootBotLINK received:  https://lists.ubuntu.com/archives/motu-council/2009-August/002183.html15:05
mdzany actions to review from last time?15:05
cjwatsonthere were several15:05
cjwatsonKeybuk: do you have them conveniently available?15:05
cjwatson(I do, I think)15:05
Keybukcjwatson: err, I don't think so15:06
mdzoh, dholbach said t hat Yulia had to leave early, so we should do that first15:06
cjwatsonoh, ok15:06
mdzignore me15:06
cjwatson/ignore mdz15:06
juli_hi, I'm Yulia:)15:06
cjwatson(maybe not)15:06
Keybukcjwatson: really? I have to unignore him for these meetings <g>15:06
Keybukjuli_: hi!  was just trying to find your IRC nickname15:06
Keybukwelcome15:06
juli_I do really have to leave early15:06
=== bjf-afk is now known as bjf
mdzthe packages involved are:15:06
mdz# netbeans15:06
mdz# libnb-platform-java15:06
mdz# libnb-javaparser-java15:06
mdz# libnb-svnclientadapter-java15:06
mdzall of these packages are in universe, and the MOTU Council approves15:07
Keybukjuli_: it looks like you've been the defacto maintainer of these packages for a while now15:07
juli_Keybuk, yes.. i'm working on them more than a year15:07
Keybukin fact, I believe you created a couple of these?15:08
juli_hmm... no. I updated them. but I created another:)15:08
Keybukjuli_: who've you been working with to upload these packages?15:09
Keybukjuli_: has anybody else been helping you out with them?15:09
juli_parsia helped a lot15:09
mdz(persia?)15:09
juli_the other sponsored my updates15:10
juli_Emmet Hikory15:10
cjwatsonjuli_: various people, including you, commented on the small number of people involved in Java packaging, and this has been a problem for some time. How do you think we could improve this? For example, are there ways that the "grunt work" of the packaging could be simplified to make it easier for people to focus on more significant improvements?15:10
cjwatsonor is it just a fundamental mindset difference, that most of the people who develop in Java don't do so by way of system-provided packages?15:11
juli_for me the biggest problem was to find sponsors and to read and remember a huge amount of information about packaging and ubuntu processes15:12
cjwatson(FWIW I don't see any problem with this application but figured you might have some thoughts on this while you're here; we could take the discussion to a different forum later if you're really rushed)15:12
juli_so I believe if we have more java-experienced MOTUs everything will be ok with java-team15:13
cjwatsonmm, it doesn't help when people have to load state about a whole different environment into their heads in order to sponsor15:13
Keybukmdz: any questions ?15:14
mdzKeybuk: none15:14
Keybukcjwatson: any further questions?15:15
juli_cjwatson, ok, lets talk later about java-team... another problem is my slow typing, so I believe we'll talk later if you don't mind15:15
Keybuk-ETIMEOUT ;)15:16
Keybuk[VOTE] Per-package uploader application: Yulia Novozhilova15:16
MootBotPlease vote on:  Per-package uploader application: Yulia Novozhilova.15:16
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:16
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:16
Keybuk+1 from me15:17
MootBot+1 received from Keybuk. 1 for, 0 against. 0 have abstained. Count is now 115:17
mdz+1 MOTU council approval for universe is plenty for me15:17
MootBot+1 received from mdz. 2 for, 0 against. 0 have abstained. Count is now 215:17
Keybukcjwatson: ?15:17
Keybuksabdfl: ?15:17
cjwatson+115:17
MootBot+1 received from cjwatson. 3 for, 0 against. 0 have abstained. Count is now 315:17
sabdfl+115:17
MootBot+1 received from sabdfl. 4 for, 0 against. 0 have abstained. Count is now 415:17
Keybuk#endvote15:17
mdz[ENDVOTE]15:17
Keybuk[ENDVOTE]15:17
MootBotFinal result is 4 for, 0 against. 0 abstained. Total: 415:17
cjwatsonsorry, was in another window, my browser crashed at an inopportune time15:17
Keybuk#hatemootbot15:17
cjwatsonjuli_: yes, no problem :)15:17
dholbachcongratulations juli_!15:18
Keybukjuli_: congratulations15:18
cjwatsonI'll implement the changes15:18
Keybukmdz, cjwatson: which one of you wants to do the necessary LP twiddle?15:18
sabdflcongrats juli_15:18
mdzjuli_: thanks for your work, and congratulations15:18
Keybukok great15:18
mdzKeybuk: cjwatson will15:18
juli_cjwatson, I'll find you on ubuntu-motu15:18
Keybuk[ACTION] cjwatson to add per-package upload rights for juli_15:18
MootBotACTION received:  cjwatson to add per-package upload rights for juli_15:18
juli_thanks all!15:18
cjwatsonjuli_: ay15:18
cjwatsonaye15:18
Keybuk[TOPIC] Per-package uploader application: Andy Whitcroft15:18
MootBotNew Topic:  Per-package uploader application: Andy Whitcroft15:18
Keybuk[LINK] https://lists.ubuntu.com/archives/motu-council/2009-August/002184.html15:18
MootBotLINK received:  https://lists.ubuntu.com/archives/motu-council/2009-August/002184.html15:18
Keybukapw warned me that he might not be able to make it today15:18
Keybukdoes anybody have any questions they'd like to ask, or would TB members be happy to approve in his absence based on the MC mail?15:19
dholbachyeah, he's on holidays - sorry for that15:19
mdzreading15:19
KeybukI'd obviously like to talk to rtg, to make sure he's not being suspiciously stalked by buses15:20
mdzI think apw has more experience with packaging at this point than rtg does15:20
Keybukbut from my POV, the kernel team members and lead have fully endorsed him, and post-reorg it would be their decision anyway, so I'm happy to simply ACK it15:20
Keybukplus, hell, it's apw!  He makes kernel images for me with random patches I chuck him!15:21
cjwatsonI'm obviously content since I put my rubber stamp on his proposal page already; in particular I'm pleased to see that, while he may not be a pre-existing packaging expert, he's really got his teeth into that in addition to the normal kernel work he does15:22
sabdflare we drawing a line between "folks who commit to the kernel branches" and "folks who upload"?15:22
cjwatsonthe automatic daily builds are another cool thing15:22
sabdflafaik apw has no other packaging experience15:22
cjwatsonsabdfl: he already commits15:22
mdzI'm a bit concerned because I think there is a shortage of packaging expertise in the kernel team, so I'm glad to see Andy stepping up and doing the work that he has done15:22
sabdflsure, all the kernel team do15:22
cjwatsonhe doesn't, but I've reviewed the packaging changes he's made and they have been very good15:22
sabdfli'm asking if we want to separate between branch commit and upload15:22
Keybuksabdfl: yes, there's a large number of other people who commit - but in apw's cases, he's the guy who's largely doing the packaging anyway15:22
sabdflcjwatson: and you're referring to the packaging pieces specifically?15:23
sabdflok15:23
cjwatsonyes15:23
cjwatsonthey're the only bits of his kernel work I'm qualified to review :)15:23
Keybuksounds like we're happy to vote in his absence15:23
Keybukso15:23
cjwatsonI think we *do* want to separate between branch commit and upload, yes15:23
Keybuk[VOTE] Per-package uploader application: Andy Whitcroft15:23
MootBotPlease vote on:  Per-package uploader application: Andy Whitcroft.15:23
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:23
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:23
cjwatsonI think that Andy should be on the RHS of that separation15:23
Keybuk(putting aside the archive-reorg issue of distinguishing between branch commit and upload for a bit)15:23
Keybuk+1 from me15:24
MootBot+1 received from Keybuk. 1 for, 0 against. 0 have abstained. Count is now 115:24
sabdflok. i'm happier if we can show that not all kernel committers have upload, and more importantly, employment on the canonical kernel team doesn't == kernel package upload15:24
mdzyes, reading the changes, apw has been doing a substantial amount of proper packaging work on the kernel package15:24
sabdfl+115:24
MootBot+1 received from sabdfl. 2 for, 0 against. 0 have abstained. Count is now 215:24
mdz+115:24
MootBot+1 received from mdz. 3 for, 0 against. 0 have abstained. Count is now 315:24
cjwatsonsabdfl: right, it most certainly doesn't - we can see that because it's taken quite a bit of work for each new Canonical kernel team member to get as far as upload privileges for the kernel15:24
cjwatson+115:24
MootBot+1 received from cjwatson. 4 for, 0 against. 0 have abstained. Count is now 415:24
Keybuk[ENDVOTE]15:24
MootBotFinal result is 4 for, 0 against. 0 abstained. Total: 415:24
Keybukapw: congratulations15:24
Keybuk[ACTION] cjwatson to add upload privilege for apw15:25
MootBotACTION received:  cjwatson to add upload privilege for apw15:25
cjwatsonunderway15:25
Keybuk[TOPIC] Outstanding actions15:25
MootBotNew Topic:  Outstanding actions15:25
cjwatson(will migrate this over to a kernel package set as soon as I can, it's a little unwieldy ...)15:25
Keybukjono has outstanding actions but is on holiday15:25
Keybukcjwatson: you were to update http://www.ubuntu.com/community/processes/techboard15:25
Keybukis that done?15:25
cjwatsonit has received basic updates to at least correct falsehoods15:25
cjwatsonit still needs more work, I'm quite sure15:26
Keybukok15:26
mdzjono proposed a paragraph to add15:26
mdzwhich I sent feedback on15:26
Keybukmdz: he did, we'll carry those over though since he's away15:26
mdzI didn't see any other responses, though; it probably needs a general ack from the team15:26
Keybukcjwatson: any progress with the Debian TC?15:27
cjwatsonhang on a second, sorry15:27
cjwatsonI also sent mail to technical-board@ with a proposal for new text for that page as a whole15:27
cjwatsonmdz made a brief comment on that15:27
cjwatsonI am going to assume consent otherwise and post it15:28
cjwatsonshout if you disagree :)15:28
sabdfl+1 from me15:28
mdzI'm happy15:28
Keybukgo for it15:28
Keybuk[ACTION] cjwatson to apply further updates to http://www.ubuntu.com/community/processes/techboard based on his draft new text15:29
MootBotACTION received:  cjwatson to apply further updates to http://www.ubuntu.com/community/processes/techboard based on his draft new text15:29
cjwatsonDebian TC is awaiting response from somebody on the TC15:29
cjwatsonmy last mail was 11 Aug15:29
mdzworth a ping15:29
cjwatsonI'll send a poke15:29
Keybuk[ACTION] TB to respond to Jono's draft text on key topics review15:29
MootBotACTION received:  TB to respond to Jono's draft text on key topics review15:29
Keybuk[ACTION] cjwatson to continue discussions with Debian TC15:29
MootBotACTION received:  cjwatson to continue discussions with Debian TC15:29
Keybuksabdfl has created and announced the TB vote, which is currently in process15:30
Keybuksabdfl: do we have any kind of figures of the portion of the developer community who have taken part so far? (just out of noseyness)15:30
sabdfl78 votes cast so far, only 2 in the past few days15:30
cjwatsonhas everyone on this board voted? :-)15:30
sabdfli can't see results yet though ;-)15:30
sabdfli have15:30
Keybuksabdfl: that's about a third of our developer base, right?15:31
Keybukoh, no15:31
sabdflout of 13015:31
KeybukLP was confusing me15:31
Keybukthat's almost two thirds; which isn't bad turnout for any election15:31
sabdflno, it's pretty good. only one person complained that the email they received wasn't gpg signed!15:31
mdzI voted; have the rest of you?15:31
KeybukI've voted15:32
cjwatsonI have15:32
cjwatson(I'm one of the 2 in the past few days)15:32
mdzshould we send out a reminder  before we close it up?15:32
cjwatsonif it's possible to send a reminder to those electors who have not voted, that would be good15:33
KeybukI guess we can't tell that15:33
Keybuksabdfl: ?15:33
cjwatsonI was hoping that civs might have that facility built in15:35
sabdfli don't believe so15:35
sabdflthere's only one button on the admin form, to end the poll15:35
Keybuksounds like more effort than it's worth ;)15:35
mdzlet's not spam everyone then15:35
sabdfli could re-add all the same email addresses, but would prefer not to experiment with it in real time15:35
sabdfl78 is a good result15:35
Keybukwe could always mail civs to see if it's a feature they could add in future if we plan to use it again15:36
sabdfli'll stop the poll Monday15:36
Keybuk[ACTION] jdstrand to add a reference to the previously-approved mDNS policy (https://wiki.ubuntu.com/ZeroConfPolicySpec)15:36
MootBotACTION received:  jdstrand to add a reference to the previously-approved mDNS policy (https://wiki.ubuntu.com/ZeroConfPolicySpec)15:36
Keybukjdstrand: that's not been done yet15:36
cjwatson[upload privilege changes done]15:36
jdstrandKeybuk: I added it somewhere...15:37
* jdstrand goes to check15:37
Keybukoh, you're quite right15:37
Keybukapparently I had a cached version of that page - logging in gave me a different one15:37
Keybukok15:38
Keybukend of last meeting's actions15:38
Keybuk[TOPIC]15:38
MootBotNew Topic:15:38
Keybuk[TOPIC] Developer membership board (ScottJamesRemnant)15:38
MootBotNew Topic:  Developer membership board (ScottJamesRemnant)15:38
KeybukI've created the Launchpad team, with the appropriate membership15:38
Keybukand I've adjusted the ubuntu-core-dev and ubuntu-dev teams15:38
Keybukthis is currently waiting on IS for creation of a new mailing list, and adjustment of the TB list15:38
Keybukas a technical aside, the TB list will actually be renamed and a new TB list created15:38
Keybuk(to keep the current archives private while opening up the new ones)15:39
Keybukthen there are documentation updates outstanding15:39
KeybukI'm confident that this board will be "ready to go" by the next TB meeting15:39
mdzdo you have the RT ticket numbers handy?15:39
mdzcjwatson can nudge them in the next IS review15:39
Keybuk#35428 TB ML15:39
Keybuk#35429 DMB ML15:39
KeybukJames has already responded to the TB one15:39
Keybuk[ACTION] Keybuk to complete implementation of Developer Membership Board15:40
MootBotACTION received:  Keybuk to complete implementation of Developer Membership Board15:40
Keybuk[TOPIC] Archive reorganisation (ColinWatson)15:40
MootBotNew Topic:  Archive reorganisation (ColinWatson)15:40
cjwatsonthe majority of MOTUs have responded to the initial feelers we sent out now15:41
cjwatsonI had a private bet with myself that most people would want to be generalists, and this seems to have turned out to be fairly accurate15:42
cjwatsonso the developer membership board will have a good deal of work to do :-)15:42
Keybukwhat's the next step?15:42
mdzcjwatson: ?15:44
mdzdholbach: ?15:45
cjwatsonI'll do a final check with the Soyuz team on the details, and start pushing initial sets into LP; on the community side the next step is to start talking with the -release teams about unifying processes there15:45
=== maco_ is now known as MsMaco
mdzcjwatson: can we set a milestone to achieve by the next TB meeting?15:45
KeybukI'm going to have to time this out15:46
Keybukwe still have several items to get through15:46
mdzagreed15:46
cjwatsonlet's shoot for the set of uploads that have already been approved being processed by Soyuz according to package set rules15:46
Keybuk[TOPIC] Check up on community bugs (standing item)15:46
MootBotNew Topic:  Check up on community bugs (standing item)15:47
KeybukThere are currently no open bugs.15:47
cjwatson(sorry, was having an internal phrasing failure)15:47
mdzzarro boogs found15:47
Keybuk[LINK] https://bugs.edge.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard15:47
MootBotLINK received:  https://bugs.edge.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard15:47
mdzmoving on15:47
Keybukindeed15:47
mdzor...are we interested in filing bugs here to keep track of anything for ourselves?15:47
mdzI think using the agenda is working reasonably well15:47
Keybukgoing to swap the next two items since one is short the other isn't15:47
cjwatsonI have enough bugs15:47
Keybuk[TOPIC] Drivers for Ubuntu (MattZimmerman, Curtis Hovey)15:47
MootBotNew Topic:  Drivers for Ubuntu (MattZimmerman, Curtis Hovey)15:47
* Keybuk can't even view his LP bugs page without a timeout error15:48
Keybukmdz: what's the progress of that?15:48
sabdflcurtis?15:48
mdzso, we now have what I hope is an authoritative explanation from the LP team about what drivers can currently do15:48
sabdflah15:48
mdzthey are now looking for us to tell them what drivers *should* be able to do15:48
mdzthere is a driver slot at the distro level and at the series level15:48
KeybukI guess we should find out from our various teams (QA, Release, etc.) what functions they think should be sacred?15:49
mdzin <20090625132529.GY7135@alcor.net> I explained who (in Ubuntu) is responsible for the various actions drivers currently can do15:49
Keybukwe could make some up, but it might not match what they want15:49
mdzand would like to separate some of those out15:49
Keybukmdz: what do you think the next step is?15:50
mdze.g. sprint stuff is done by the event organizers, blueprint stuff is done by tech leads and the like15:50
mdzbug nominations are a problem all to themselves15:50
mdzKeybuk: to get consensus on how the permissions for these various things should work in Ubuntu15:50
Keybukmdz: consensus amongst whom?15:50
mdz>  * Bug nominations15:51
mdz>  * Blueprint approvals15:51
mdz>  * Can edit all aspects of a specification15:51
mdz>  * Accepting blueprints for sprints15:51
mdz>  * Control the agenda of a sprint15:51
mdz>  * The ability to set package bug guidelines.15:51
mdz>  * The ability to set official bug tags.15:51
mdz>  * Can view and edit announcements before they are public15:51
cjwatsonto be perfectly honest, splitting out blueprint permissions and then letting people with upload privileges for the relevant packages (or core developers for the whole distro) do everything else would basically work fine most of the time15:51
mdzand the ability to change arbitrary bug contacts on behalf of other people/teams15:51
Keybukit seems that that consensus should be amongst the teams who would be given those powers15:51
Keybuknot amongst the TB members?15:51
cjwatsonblueprint permissions are the main sore thumb here15:51
sabdflthe drivers idea was to have a simple model that would work for upstreams and ubuntu15:52
sabdflbut it didn't ;-)15:52
mdzKeybuk: I think we should take a view, and then make sure it's OK with everyone else15:52
sabdflif you can think of a better, general approach that LP can take, that will be well received15:52
Keybukmdz: ok, would you be happy to draft that view as a mail, and take this to the list15:52
cjwatsonit worked for Ubuntu early on, but the project is just too complex now15:52
mdzOK15:52
sabdfli don't think it will be well received to describe something that's *only* relevant to the distro15:52
Keybukwe have 8 minutes left and a community member waiting to discuss their topic15:52
mdzin the interest of time15:52
sabdflexcept as a datapoint15:52
mdzKeybuk: I'll take the action15:53
cjwatsoncan I suggest, then, simply splitting up feature planning and everything else?15:53
Keybuk[ACTION] mdz to draft proposed ubuntu drivers scheme for consensus15:53
MootBotACTION received:  mdz to draft proposed ubuntu drivers scheme for consensus15:53
mdzcjwatson: do you want to draft it instead? ;-)15:53
cjwatsonif you like15:53
Keybuk[ACTION] cjwatson to draft proposed ubuntu drivers scheme for consensus15:53
Keybuk;-)15:53
MootBotACTION received:  cjwatson to draft proposed ubuntu drivers scheme for consensus15:53
Keybuk[TOPIC] Base-2 prefix names (BenjaminDrung)15:53
MootBotNew Topic:  Base-2 prefix names (BenjaminDrung)15:53
Keybukbdrung: go15:53
cjwatsoncjwatson to be plastic mdz substitute15:53
mdzcjwatson: I'll dig up the old mail and add my comments as a starting point15:54
mdzcjwatson: thank you15:54
cjwatsonI have the thread, at least15:54
Keybukcjwatson: "Emergency Holographic...", err, wait, wasn't _his_ name Zimmerman? :p15:54
bdrungstarting point: http://paste.ubuntu.com/259296/15:54
Keybukfor those without the background, this is the long-running discussion about the use of units in Ubuntu15:54
Keybukwhether 1KB (kilobyte) is 1,024 bytes or 1,000 bytes, or whether it should be 1KiB (kebibyte)15:55
Keybukwe should first probably agree whether it is something we would like to have a policy on15:55
mdz(kibibyte, no?)15:55
Keybukand if we agree that we should, what that policy would be15:55
Keybukmdz: err, perhaps ;)15:55
bdrungthe problem is how to fix the missusage of the SI standard for base-2 units ( 1 MB != 1024 KiB)15:55
cjwatsonwhile personally I have aesthetic objections to the IEC abbreviation, it's been gaining considerable acceptance and I can't say I feel like swimming upstream against it15:56
cjwatsonso better that than a total mess15:56
sabdflif there's a standard and it's gaining momentum, let's use it15:56
cjwatsonI think it's an issue of interoperability of user presentation, and thus worth having a policy on15:56
Keybuksabdfl: the problem is that the standard isn't gaining momentum where it matters15:56
sabdflespecially if google will tell people what it means, accurately, quickly15:56
mdzI think there is real value in having the abbreviation mean something consistent15:56
Keybukie. in the devices people actually buy15:56
cjwatsonsabdfl: right, but that's not the whole proposal :)15:56
Keybukand, more to the point15:57
Keybukthere are *two* standards ;-)15:57
cjwatsonwe already know we can't use IEC abbreviations everywhere15:57
bdrungin some cases it would useful that the user could decide, if he wants IEC or SI15:57
Keybuk(in fact, there's arguably three if you could the O'Reilly Style Guide)15:57
Keybukbdrung: ugh.  configuration.15:58
Keybuk;)15:58
cjwatsonfile sizes (in the proposal) are an interesting point I really hadn't thought much about before, and it could easily go either way depending on the use case, so I do not think that the time is ripe for us to have a policy on it15:58
mdzone of the key questions, I think, is *where* we try to standardize15:58
cjwatsonlet's standardise where the general drift is already towards something standard15:58
bdrungi do not think, that all people agree on one basis for file sizes15:58
mdzsome of the friction seems to be around established UNIXy tools, which double as end user tools and APIs15:58
mdzI think that change there may be more trouble than it's worth15:59
cjwatsonand not try to standardise where there is total chaos and (perhaps more relevantly) where it isn't really of immediate importance15:59
mdzuser-visible applications are a different story perhaps15:59
sabdflthis is much simpler if we say "we use that standard", propose Debian do the same, and file bugs accordingly15:59
sabdflinevitably, those bugs will get fixed faster in the areas cjwatson describes15:59
Keybuksabdfl: the problem is that if we, for example, say we'll always use the IEC standard15:59
cjwatsonit is wrong to apply the same standard to everything, here15:59
cjwatsontotally wrong15:59
Keybukthen we end up in the strange situation where we report different values for a user's DSL line speed than the ISP15:59
Keybuk(who use the SI standard)15:59
cjwatsonwe can apply one standard to RAM, and one standard to disk sizes15:59
Keybukcjwatson: but then swap partitions? :p16:00
mdzsabdfl: except it's not simple, because a blanket policy runs into all sorts of places where I think there's no tangible benefit in doing so, and a lot of potential pain16:00
cjwatsonbut if we apply the same standard to both then we will create confusion, not address is16:00
cjwatsonit16:00
sabdflbut then we have to decide in each of those cases, which takes time, and communicate changes in those decisions over time, which is a nightmare16:00
cjwatsonyes, we do, and yes it's a nightmare. the alternative is even worse.16:00
mdz(we're running over into the server team's hour now)16:00
sabdflthe KB nomenclature is non-specific, fuzzy. The IEC stuff, while ugly, is at least accurate16:00
Keybukindeed16:00
cjwatsonfortunately there aren't actually that many general cases at hand16:00
sabdflaiui16:00
cjwatsonthe IEC stuff is *wrong* for disks.16:00
sabdflso, if people google it, they will be told "this is what it..". oh.16:00
cjwatsonuntil such time as disk manufacturers get a clue :-)16:00
Keybuksabdfl: KB isn't correct anyway - SI is kB (just a random observation)16:00
KeybukKB for 1,024 bytes *is* O'Reilly Style Guide compliant though16:01
Keybuk(which says KB=1,024, kB=1,000)16:01
sabdflsigh. i was not born for this discussion. i abstain.16:01
Keybuk:D16:01
Keybukok, it sounds like we agree that this is a mess :-)16:01
sabdflwell. actually, i vote for IEC everywhere16:01
sabdflbut i won't argue the point, just vote16:01
ballK has been 1,024 at least since the 1960s16:01
ball...probably the 1950s16:01
ball(see old DEC manuals for instance)16:02
bdrungbut KB for 1,024 bytes is not SI16:02
cjwatsongparted does that for disks and people are confused that it gives a different number than what it says on the box they got their disk drive in16:02
mdzKB and KiB are both valid and mean different (increasingly standard) things16:02
ballbdrung: no, but it's not incompatible with SI.16:02
mdzthere are circumstances where each is valid16:02
mdzs/valid/appropriate/16:02
ballk = 1000, K = 102416:02
balljob done.16:02
ball(unless Kelvin, but obviously not applicable to disk drives, RAM etc.)16:03
cjwatsonperhaps unfortunately, that is not the way the rest of the world is going16:03
ewookagreed.16:03
KeybukI suggest that the appropriate way to deal with this is to first agree whether we *should* have a policy on this16:03
mdzthis is the umpteenth time it has come up, so I think we do need one16:03
Keybukand if we agree we should, we should follow cjwatson's debate suggestion of having people draft competing policies and arguments16:03
Keybukok, let's vote on that16:03
cjwatsonwe should have a policy, but it should be nuanced16:03
mdzcjwatson++16:03
Keybuk[VOTE] SHOULD we have a policy on use of unit multiples?16:03
MootBotPlease vote on:  SHOULD we have a policy on use of unit multiples?.16:03
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot16:03
MootBotE.g. /msg MootBot +1 #ubuntu-meeting16:03
mdz+116:03
MootBot+1 received from mdz. 1 for, 0 against. 0 have abstained. Count is now 116:03
cjwatson+116:03
MootBot+1 received from cjwatson. 2 for, 0 against. 0 have abstained. Count is now 216:03
Keybuk+1 we should have a policy16:03
MootBot+1 received from Keybuk. 3 for, 0 against. 0 have abstained. Count is now 316:03
Keybuksabdfl ?16:04
gnuyoga+116:04
MootBot+1 received from gnuyoga. 4 for, 0 against. 0 have abstained. Count is now 416:04
sabdfl+116:04
MootBot+1 received from sabdfl. 5 for, 0 against. 0 have abstained. Count is now 516:04
Keybuk[ENDVOTE]16:04
MootBotFinal result is 5 for, 0 against. 0 abstained. Total: 516:04
Keybukok16:04
* ball doesn't even know what meeting he's in ;-)16:04
mdzball: Ubuntu Technical Board16:04
bdrungwhere to put the policy draft?16:04
Keybukthen I suggest the initiative should be bdrung's as the proposer16:04
mdzbdrung: wiki16:04
sabdflhas debian made a serious effort to standardise or set a policy?16:04
Keybukbdrung would you be happy to draft a policy (in wording similar to patent policy, etc.) and propose it to the TB16:04
cjwatsonultimately a ratified draft could go into the Ubuntu policy manual16:04
cjwatsonsabdfl: I think it's been bikeshedded, but I don't recall a serious effort to standardise16:04
Keybukand then if anybody else has a proposed alternate policy, we can discuss from there?16:04
bdrungmdz: which location directly?16:04
mdzbdrung: your choice16:05
bdrungsuggestions?16:05
bdrungnames which avoids bikeshedds?16:05
cjwatsonthere have been some discussions related to it, e.g. http://bugs.debian.org/53440816:05
Keybukbdrung: wiki.ubuntu.com/DraftUnitsPolicy ?16:05
Keybukor /UnitsPolicy16:05
bdrungsounds good16:05
ballmdz: thanks.  I wouldn't have interrupted but that's a pet peeve of mine.16:05
Keybuk[ACTION] bdrung to draft initial units policy for discussion16:05
MootBotACTION received:  bdrung to draft initial units policy for discussion16:05
Keybuk[TOPIC] chair for next meeting16:06
MootBotNew Topic:  chair for next meeting16:06
Keybukwe can't decide a chair without knowing who's in the TB for the next meeting16:06
Keybukunless it's cjwatson?16:06
Keybuk#endmeeting16:06
MootBotMeeting finished at 10:06.16:06
Keybuktimeout again16:06
sabdflthanks all16:06
cjwatson(FWIW I can find no other relevant discussion on debian-policy that includes the word "kibibyte", so I think #534408 is the only thing close)16:06
Keybuksorry server team16:06
Daviey:)16:07
jmdault=)16:07
mathiazallright - let's get the server team meeting started16:07
Sam-I-Ammorning16:07
mathiaz#startmeeting16:07
MootBotMeeting started at 10:07. The chair is mathiaz.16:07
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:07
mdzmathiaz: I have a couple of agenda items if there is time16:07
mathiazToday's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting16:08
soreno/16:08
mathiazmdz: I'll try to leave some time for an open discussions16:08
mathiazlast week's minutes: https://wiki.ubuntu.com/MeetingLogs/Server/2009081816:08
ttxo/16:09
Daviey\o16:09
mathiaz[TOPIC] Asterisk16:09
MootBotNew Topic:  Asterisk16:09
ivokso/16:09
mathiazjmdault: what's the state of the stack?16:09
jmdaultmathiaz: pwlib and openh323 have the right versions in karmic since friday16:09
mathiazjmdault: next in line are dahdi and astreisk* ?16:10
Davieysuprisingly, openh323 has been in a build dep wait since April, and was satisified with pwlib upload therefore automagically building.16:10
jmdaultmathiaz: the Debian Asterisk package has been imported in karmic16:10
jmdaultI've built packages in my PPA16:10
mathiazjmdault: great - what's left then?16:10
jmdaultNow all that's left is for someone to review my packages and upload them16:11
DavieyHmm16:11
DavieyThere is the dahdi-dkms issue.16:11
jmdaultI sent the dkms patch to debian-voip maintainers16:11
DavieyDebian isn't carrying dkms for dahdi.. so if we upload that now, it's a ubuntu specific change16:12
Davieyjmdault: great, they were waiting for it.  Would be great to hear of their feedback, was it on the ML?16:12
Davieythier*16:12
mathiazjmdault: ok - do you have sponsors?16:12
jmdaulthopefully someone will have a look at it between all the spam that's on the list =(16:12
mathiazjmdault: where are the packages that needs to be reviewed?16:12
Davieyjmdault: hah, just seen the email arrive in my Inbox :)16:12
jmdaultmathiaz: https://launchpad.net/~jmdault/+archive/ppa16:13
jmdaultI also put everything in bzr for easy diffs16:13
jmdaulthttps://code.launchpad.net/~ubuntu-voip/+junk/asterisk-1.616:13
mathiazjmdault: ok - thanks for working on that16:13
jmdaultI was expecting stgraber to sponsor me, unfortunately he's overloaded this week16:14
mathiazjmdault: next step is to find sponsors for the remaining packages in https://launchpad.net/~jmdault/+archive/ppa16:14
mathiazanything else to add?16:14
jmdaultI updated the wiki page16:14
mathiazjmdault: which one?16:15
jmdaulthttps://wiki.ubuntu.com/AsteriskIntegration16:15
Davieyhttps://wiki.ubuntu.com/AsteriskIntegration16:15
jmdault=)16:15
jmdaultNow, how can I find a sponsor?16:15
mathiazjmdault: send an email to ubuntu-motu@16:16
mathiazjmdault: ask in #ubuntu-motu16:16
mathiazjmdault: blog about it16:16
jmdaultok16:16
mathiazjmdault: however we're before FF so everyone is very busy16:17
jmdaultyes, I know =(16:17
mathiazanything else before we move on?16:17
jmdaultnope16:17
mathiazgreat16:17
mathiaz[TOPIC] Update Ebox to 1.316:17
MootBotNew Topic:  Update Ebox to 1.316:17
mathiazfoolano: ^^?16:17
ttxzul says: "Ebox 1.3 in universe is done"16:18
mathiazgreat. let's move on.16:18
mathiazThat's all I had from last week minutes.16:18
mathiaz[TOPIC] SRU weekly review16:18
MootBotNew Topic:  SRU weekly review16:18
ttxyay16:18
mathiazReview nominated list and last week fix released bugs to either accept them or mark them won't fix16:18
Davieyquite an easy review :)16:19
mathiazhttp://people.canonical.com/~mathiaz/fixedbugs.ubuntu-server.latest.html16:19
MootBotLINK received:  http://people.canonical.com/~mathiaz/fixedbugs.ubuntu-server.latest.html16:19
mathiazanything SRU worthy on this list^^ ?16:19
ttxI don't have any favorite there.16:20
ivokswell, if apache segfaults with mod_deflate...16:20
Davieybug 409987 needs watching16:21
ubottuLaunchpad bug 409987 in apache2 "apache2 segfault using mod_deflate" [Medium,Fix released] https://launchpad.net/bugs/40998716:21
ivoksi'm using mod_deflate and haven't seen segfault in hardy16:21
jmdault+1 for 40998716:21
ttxdoesn't http://www.ubuntu.com/usn/USN-802-2 cover those ?16:22
DavieyBug #40630316:22
ubottuLaunchpad bug 406303 in php5 "Compiled zip support in PHP 5.2.4 64bit can't open archives with large number of files." [Undecided,Fix released] https://launchpad.net/bugs/40630316:22
Daviey ^^ seems to be in hand already16:22
mathiazright - its seems that it's a security related regression so the security team should be following up16:22
Davieyttx: The comments suggest no.16:22
ivoksttx: it should16:22
ttxDaviey: at this point the bug is considered fixed... and in every release16:24
ivoksshould be tested16:24
ivokssince we have a user that claims it's not fixed16:24
ttxI'm pretty sure security tested it16:24
mathiazI think mdeslaur is on it.16:24
ivoksright16:24
ttxanyway, either the bug is fixed or not fixed. If it's not fixed yet, then it's not a SRU candidate anyway16:24
Davieyi'm not sure we can have additional influence at this stage.16:24
mathiazhow about bug 406303?16:25
ubottuLaunchpad bug 406303 in php5 "Compiled zip support in PHP 5.2.4 64bit can't open archives with large number of files." [Undecided,Fix released] https://launchpad.net/bugs/40630316:25
Davieymathiaz: seems to be in hand with Chuck Short.16:25
ttxmathiaz: accepted already16:25
mathiazoh ok.16:25
mathiazanything else from the list?16:25
ttxno.16:26
Davieynot here.16:26
mathiazok - let's move on to the next list:16:26
mathiazhttp://us-dappernominated.notlong.com/16:26
MootBotLINK received:  http://us-dappernominated.notlong.com/16:26
mathiazanything worth accepting?16:26
ttxmost of them are nominated by someone named "Mathias Gug".16:27
mdzsounds suspicious16:27
ttxI'd accept all of them. Except maybe 164007 which shoudl be handled (or is handled) by security16:27
mathiazttx: sounds good. are you doing it?16:28
mathiazttx: net-snmp seems security related16:28
mathiazbug 16400716:28
ubottuLaunchpad bug 164007 in net-snmp "[net-snmp] remote Denial of Service vulnerability" [Undecided,Fix released] https://launchpad.net/bugs/16400716:28
ttxyes, I don't really know what we should do with those. Leave them alone ?16:28
jdstrandthat should be fixed in http://www.ubuntu.com/usn/usn-564-116:29
ttxjamie to the rescue16:29
mathiazjdstrand: for all previous releases?16:29
jdstranddapper through gutsy16:29
Daviey\o/16:29
jdstrandlook at that, I even prepared it :)16:29
mathiazjdstrand: so not relevant for hardy+?16:29
ttxok, accepting them and fix-releasing the security one16:30
jdstrand5.4.1 has the fix16:30
jdstrand5.4.1~dfsg-4ubuntu4 has released in hardy (not affected)16:30
mathiazgreat - nothing left from dapper16:30
mathiazlet's move on to hardy16:30
jdstrands/has/was/16:31
mathiazhttp://us-hardynominated.notlong.com/16:31
MootBotLINK received:  http://us-hardynominated.notlong.com/16:31
ttxI'm unsure about those two hardy ones. Are those features, or bugs ?16:31
ttxIf PHP doesn't count correctly, I wouldn't "fix" it in a SRU.16:31
mathiazright - decline16:32
ttxthe DDNS thing is a feature, but counts as a bug if "doing as in Windows" is the right behavior16:32
mathiazas the potential for regression in existing code is high16:32
mathiazdoes thing badly break if DDNS is not done?16:33
jdstrandttx: I'll take care of the net-snmp bug. I didn't notice it before now and should have closed it with the USN16:33
ttxjdstrand: ok16:33
mathiazttx: does thing badly break if DDNS is not done?16:33
ttxmathiaz: no. It's just that the newly-joined workstation needs to be manually added into Windows DNS16:34
ttxwhile Windows workstations do that automatically16:34
mathiazttx: ok - I'd decline16:34
ttxok16:35
ttxdeclining both, next16:35
mathiaznothing left for hardy - let's move on to intrepid16:35
mathiazhttp://us-intrepidnominated.notlong.com/16:35
MootBotLINK received:  http://us-intrepidnominated.notlong.com/16:35
ttxAll those are valid. Though I wouldn't spend too much time fixing Intrepid now.16:35
ttxBut since we should accept them if they are valid, rather than if we want to do them...16:36
mathiazttx: right.16:36
mathiazjust a reminder that accepting bugs doesn't mean they'll get fixed16:36
mathiaznext step is for someone to prepare the SRU report and a bzr branch for sponsoring16:37
mathiazttx: anything else for intrepid?16:37
ttxno, accepting them16:38
mathiazgreat - let's move on to jaunty16:38
mathiazhttp://us-jauntynominated.notlong.com/16:38
MootBotLINK received:  http://us-jauntynominated.notlong.com/16:38
ttxshould be declined. not in Jaunty16:38
=== nxvl_ is now known as nxvl
ttxregression if any should be handled in a separate bug16:39
ttxas jamie commented.16:39
mathiazttx: agreed.16:39
mathiazso nothing left in these lists.16:39
mathiazso next phase:16:40
mathiazReview accepted list16:40
mathiazwell - I've looked at LP and wasn't able to come up with a query that would have this list16:40
mathiazFYI I'm following https://wiki.ubuntu.com/ServerTeam/KnowledgeBase in the SRU weekly review section from the IRC meeting section16:41
ttxzul has been cherrypicking SRU candidates, but a list would definitely be useful.16:41
mathiazttx: right - I'll work on my scripts to try to produce such a list16:41
ttxgreat !16:42
mathiaz[ACTION] mathiaz to produce a list of accepted bugs for packages related to the ubuntu-server team16:42
MootBotACTION received:  mathiaz to produce a list of accepted bugs for packages related to the ubuntu-server team16:42
mathiazanything else to add to the SRU review?16:42
ttxnope16:42
mathiazThings should be faster now that we have gone through the first round16:42
mathiazand purged all the backlog.16:43
ttxyes.16:43
mathiaz[TOPIC] FFE for bacula16:43
MootBotNew Topic:  FFE for bacula16:43
mathiazso zul was supposed to talk about that16:43
mathiazbut he isn't here.16:43
ivokseh...16:43
mathiazanyone wants to add something ?16:44
mathiazivoks: ^^?16:44
ivoksi'll ask him if there's anything special to keep in mind16:44
ttxI guess he expects to request a FFe to get Bacula to 3.0.216:44
ivoksbut it shouldn't be a problem to do a merge16:44
ivoksso, i could work on that16:44
ttxI'm not sure whay 3.0.2 is required though.16:44
ttxwhy, even16:44
ivokssecurity probably16:45
mathiazttx: seems to be a new upstream version16:45
ivoksVersion 3.0.2 is primarily a important bug fix update to version 3.0.116:45
mathiazit's been in experimental for a few months16:45
mathiazivoks: right - however 2.4 is in karmic16:46
ivokswe should move to 3.0.x16:46
mathiazivoks: why should we move to 3.0.X now in karmic?16:46
ivoksso, there should be an upgrade16:46
ivoksit's probably to late now...16:46
mathiaz3.0 went in unstable 5 days ago16:47
Sam-I-Amis 9.10 going to be lts? i forget...16:47
mathiazSam-I-Am: nope16:47
DavieySam-I-Am: no16:47
Sam-I-Amah, then it can probably wait until 10.0416:47
mathiazok16:47
Sam-I-Amif it was lts i'd say its a bigger deal16:47
* mathiaz agrees16:47
mathiaz[ACTION] bacula FFe rejected - 3.0.X deferred to the next release cycle.16:48
MootBotACTION received:  bacula FFe rejected - 3.0.X deferred to the next release cycle.16:48
dendrobatesmathiaz: although, it would be nice to test it in karmic before we put it in an lts16:48
ivokswe might open ppa inside bacula-team16:48
Sam-I-Amthat'd work16:49
dendrobatesivoks: that works16:49
mathiazivoks: seems like a good plan.16:49
Davieydendrobates: Whilst i agree, is it a good idea if we get in the habbit of a non-LTS being an 'almost' unstable server release?16:49
mathiaz[ACTION] bacula 3.0.X to be made available from a PPA from the bacula team.16:50
MootBotACTION received:  bacula 3.0.X to be made available from a PPA from the bacula team.16:50
ivoksi always consider non-LTS as 'technology preview' - this is something you'll get in next LTS16:50
dendrobatesDaviey: yes, that is what it is.16:50
mathiazanything else to add on the topic of bacula 3.0.x in karmic?16:50
mathiaznope - let's move on.16:51
mathiaz[TOPIC] Open Discussion16:51
MootBotNew Topic:  Open Discussion16:51
mathiazmdz: ^^?16:51
mdzmathiaz: thanks16:51
mdzI'd like to check in on a few 9.10 projects if that's OK16:51
mdzjust to make sure I know where we stand for feature freeze16:51
mdzI'll try to be quick, if I can get quick answers ;-)16:52
mdzfirst, the UEC/EC2 images16:52
mdzI see that they're building daily now, and they were included in alpha 4. that looks good16:52
mdzI'm a bit concerned about the following bugs:16:52
mdzhttps://bugs.edge.launchpad.net/bugs/41813016:52
ubottuLaunchpad bug 418130 in ubuntu-on-ec2 "Karmic EC2 kernel tracking bug" [Undecided,New]16:52
mdzhttps://bugs.edge.launchpad.net/ubuntu-on-ec2/+bug/37674016:52
ubottuLaunchpad bug 376740 in ubuntu-on-ec2 "user-data script: "public key is not available" for PPA" [Critical,Confirmed]16:52
mdz418130 is said to be the major blocker, but it's Undecided/New and not targeted. seems in need of triage?16:53
sorenmdz: The latter was fixed today.16:53
mdzsoren: that's great news. launchpad still thinks it's open and critical. can we close it? ;-)16:53
ttxmdz: 418130 was just created as a tracker. I asked jjohansen to update the status on it16:53
sorenmdz: It was closed 7 minutes ago :) I just haven't done the paperwork yet.16:53
ttxmdz: I think he is on vacation.16:54
mdzttx: why is it "just a tracker"? are we not sure if there is a bug or not?16:54
sorenWe're sure there's a bug.16:54
sorenThe bug /report/ was opened to have a place to track the work being done on the subject.16:55
ttxnot "just a tracker". A tracker. there might be multiple issues, all resulting in not being able to use a karmic kernel on karmic images.16:55
mdzI was pointed to this bug as the authoritative bug report for the issue which is preventing us from releasing 9.04 EC2 images16:55
mdziirc the problem was that the instances sometimes didn't boot16:55
sorenThat's correct.16:55
mdzthere's nothing in that bug report about that, though16:55
mdzis there a separate bug report which actually describes the problem, filed on the kernel perhaps?16:55
sorenThere is. Just a moment.16:56
ttxsoren: ah ? couldn't find it.16:56
mdzttx: part of what confused me is that the bug only referred to Karmic (just as you did just now).  but do we not have the same issue on 9.04?16:56
sorenI've decided this is the one: https://bugs.edge.launchpad.net/ubuntu-on-ec2/+bug/39856816:57
ubottuLaunchpad bug 398568 in ubuntu-on-ec2 "ami-bbf514d2: Sometimes does not start booting (empty console output, no network)" [Undecided,Confirmed]16:57
ttxsoren:  since jj couldn't update the status and zul is away, could you update status on that "tracker" bug ?16:57
mdzttx: since there is already a proper bug open, I don't see why we need this "tracker" one16:57
sorenI'm assuming the failure in us-east-1a is a different problem.16:57
mdzsoren: thank you16:57
sorenttx: I know I said differently yesterday. Sorry.16:57
mdzthat one is set to importance Undecided, and is not assigned to anyone16:57
mdzwho is working on the issue?16:58
sorenzul and jjohansen.16:58
ttxmdz: I acted based on soren's feedback :)16:58
sorenYeah, my bad entirely. I read too much into the us-east-1a failure in Eric's report.16:58
mdzok, so it needs to be triaged and assigned16:58
mdzwhat's the status of the Ubuntu package archive server(s) inside EC2?16:58
ttxmdz: yes. I thought jjohansen would do that, unfortunately he is away16:58
ttxmdz: will make sure it is.16:59
sorenmdz: I was under the impression that they were live.16:59
sorenI cannot say so authoritatively, though.16:59
sorenThey're run by IS.16:59
smoseri'm under that same impression, but can verify quickly if need be16:59
mdzmy assumption is that the official jaunty and karmic images use those repositories by default in sources.list16:59
mdzis that correct?16:59
sorenIn a sense, yes.17:00
sorenThe instances, yes.17:00
mdzso it dynamically sets it up at boot?17:00
sorenthe images... Less so. We do some configuration at boot-up to adjust things like this.17:00
sorenYes.17:00
mdzok, sounds good17:00
sorenThat way we can use the same images all over the place.17:00
mdzif someone could confirm that they actually work and are being kept up to date, I would appreciate it17:00
ttxWe're running out of time, though we can continue this status update in #ubuntu-server (or #ubuntu-cloud)17:00
mdzsure, happy to17:01
mdz->#ubuntu-server17:01
ttxmathiaz: close ?17:01
mathiazttx: sure.17:01
=== marjomercado is now known as marjo
mathiaz[TOPIC] Agree on next meeting date and time17:01
MootBotNew Topic:  Agree on next meeting date and time17:01
mathiaznext week, same time, same place?17:01
ivoksyes17:01
* Daviey wonders if it is worth moving the time, as it clearly adds pressure on the TB every week.17:02
Sam-I-Amyup17:02
mathiazDaviey: TB runs every other week17:02
ivoksDaviey: or move it to ubuntu-server17:02
mathiazAlso there isn't always a meeting afterwards17:03
mathiazanyway - same place, same time, next week17:03
mathiazthanks for attending17:04
Sam-I-Amsounds good17:04
ttxsound good17:04
mathiaz#stopmeeting17:04
ttxthanks mathiaz17:04
Daviey+117:04
sommerthanks mathiaz17:04
Davieyo/17:04
mathiaz#endmeeting17:04
MootBotMeeting finished at 11:04.17:04
=== vorian is now known as OldSchool
manjoroll call17:57
liebhere17:57
manjo#startmeeting17:57
MootBotMeeting started at 11:57. The chair is manjo.17:57
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:57
bjfYO!17:57
manjo[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:57
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting17:57
* rtg is here17:57
* smb comes in17:58
rtgmanjo, you're a bit ahead of schedule17:58
* amitk is here17:58
* manjo waiting 1minute 17:58
* ogasawara waves17:58
manjoWe have several topics for discussion today, total meeting time is one hour, a little over 3 minutes per topic.17:59
* jjohansen waves17:59
manjo[TOPIC] Open Action Items: check up on drbd status in dkms package and kernel (apw)18:00
MootBotNew Topic:  Open Action Items: check up on drbd status in dkms package and kernel (apw)18:00
bjfmoving on...18:00
manjo[TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)18:00
MootBotNew Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)18:00
ogasawaraRelease Meeting Bugs (5 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic18:00
ogasawaraRC Milestoned Bugs Alpha 5 (0 kernel bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs?field.milestone%3Alist=1271318:00
ogasawaraRelease Targeted Bugs (9 bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux18:00
manjoogasawara, anything else ?18:01
ogasawaramanjo: nope18:01
manjoTOPIC] Karmic Release Status: Milestoned Features18:01
ogasawaraMilestoned Features - https://launchpad.net/ubuntu/+milestone/karmic-alpha-518:01
ogasawaramanjo: nothing kernel specific there either18:01
manjo[TOPIC] Karmic Release Status: Blueprints: hwdb workshop (ogasawara)18:01
MootBotNew Topic:  Karmic Release Status: Blueprints: hwdb workshop (ogasawara)18:01
ogasawaraThere is now a bzr branch of code for removing the HAL dependency from the hwdb and checkbox and using udev instead.18:02
ogasawaraThis will hopefully be merged before feature freeze (which is in 2 days).18:02
manjo[TOPIC] Karmic Release Status: Blueprints: kms (apw)18:02
MootBotNew Topic:  Karmic Release Status: Blueprints: kms (apw)18:02
manjo[TOPIC] Karmic Release Status: Blueprints: new kernel on lts (rtg)18:02
MootBotNew Topic:  Karmic Release Status: Blueprints: new kernel on lts (rtg)18:02
rtgmanjo, about to be uploaded, probably later today.18:03
manjook thanks rtg18:03
manjo[TOPIC] Karmic Release Status: Blueprints: review of non upstreamed code (smb)18:03
MootBotNew Topic:  Karmic Release Status: Blueprints: review of non upstreamed code (smb)18:03
smbI went over the list a few minutes ago. Most things are complete, a few disabled but not yet dropped and one driver (lenovo-sl) I have to check with Ike.18:03
manjook thanks smb18:03
manjo[TOPIC] Karmic Release Status: Blueprints: android (coolony)18:03
MootBotNew Topic:  Karmic Release Status: Blueprints: android (coolony)18:03
rtgI suspect there is no change there.18:04
bjfthat is supposed to be removed from the agenda18:04
bjf[ACTION] remove android blueprint from agenda18:04
manjo[ACTION] remove android blueprint from agenda (bjf)18:05
MootBotACTION received:  remove android blueprint from agenda (bjf)18:05
manjo[TOPIC] Karmic Release Status: Blueprints: suspend resume (manjo)18:05
MootBotNew Topic:  Karmic Release Status: Blueprints: suspend resume (manjo)18:05
manjoWorking on putting together the USB test kit, target ALF.18:05
manjotest KMS & suspend resume18:05
manjodisable blutooth before suspend resume testing coz of known failures18:06
manjo[TOPIC] Karmic Release Status: Other Release Tasks: AppArmour (jjohansen)18:06
MootBotNew Topic:  Karmic Release Status: Other Release Tasks: AppArmour (jjohansen)18:06
jjohansenlp #359338 started testing on it friday18:06
ubottuLaunchpad bug 359338 in linux "apparmor paths are broken when using ecryptfs on jaunty" [High,In progress] https://launchpad.net/bugs/35933818:07
jjohansenut didn't get to far18:07
jjohansenI have a request pull with about 10 commits I need to send out18:07
jjohansenI just need to go back and add lp bug numbers to some of the commit18:07
jjohansens18:07
rtgjjohansen, how important is this bug to get fixed?18:08
jjohansenother than that there are some known bugs in user space18:08
jjohansenrtg: you mean lp #35933818:08
ubottuLaunchpad bug 359338 in linux "apparmor paths are broken when using ecryptfs on jaunty" [High,In progress] https://launchpad.net/bugs/35933818:08
rtgyes18:08
jjohansenfairly, but it isn't a regression as it exists in jaunty18:08
jjohansenbut with ecryptfs becoming an install option ...18:09
rtgjjohansen, on a diffetrent topic, how is EC2 coming (which has higher priority) ?18:09
jjohansenI refreshed the EC2 patches against latest on friday18:09
rtgyou have a kernel that boot reliably?18:10
jjohansenI can build a kernel but it doesn't package for EC2, and its editing configs18:10
jjohansenthat is as far as I got with it18:10
jjohansenI have currently kicked off a build of the pv ops kernel to stick in for karmic18:11
jjohansenuntil the xen patch kernel is running18:11
rtgk18:11
jjohansenrtg: no18:11
jjohansenit doesn't boot reliably, but with suffice for alpha18:11
rtgstill the same availability zone issue?18:11
jjohansenyeah the pv ops has the zone issue18:12
jjohansenthe xen patch kernel has other config issues18:12
jjohansenit should just be a matter of working through the config18:12
jjohansenthe friday update fix a couple problems18:12
rtgmanjo, on to ARM status...18:13
manjo[TOPIC] Karmic Release Status: Other Release Tasks: ARM-Freescale (amitk,bjf)18:13
MootBotNew Topic:  Karmic Release Status: Other Release Tasks: ARM-Freescale (amitk,bjf)18:13
bjfJaunty got it's FSL update. All ER8-SP patches applied and available in official Jaunty tree.18:13
bjfCurrently updating the dove configuration in Karmic. Dove, karmic pacakges are being published.18:13
amitknothing new to report (still stuck with the ethernet driver and perhaps some gpio misconfiguration)18:14
manjo[TOPIC] Karmic General Status (rtg)18:14
MootBotNew Topic:  Karmic General Status (rtg)18:14
rtguploaded a -rc7 based kernel, expect final perhaps next week.18:14
manjo[TOPIC] Security & bugfix kernels: Jaunty/Intrepid/Hardy/Others (smb)18:15
MootBotNew Topic:  Security & bugfix kernels: Jaunty/Intrepid/Hardy/Others (smb)18:15
rtgafter that I'' start to get real fussy about what goes into master.18:15
smb_tp* Dapper:   2.6.15-54.79 (security)18:15
smb_tp* Hardy:    2.6.24-24.59 (security)18:15
smb_tp            2.6.24-24.60 (proposed)[3] 0/2 verifications18:15
smb_tp* Intrepid: 2.6.27-14.39 (security)18:15
smb_tp            2.6.27-14.40 (proposed+security/pending)18:15
smb_tp* Jaunty    2.6.28-15.49 (security)18:15
smb_tp            2.6.28-15.50 (proposed/pending)18:15
smb_tpIntrepid is just a new upload for the previous proposed. Both Intrepid and18:15
smb_tpJaunty are not yet accepted into proposed. Hopefully this happens this week.18:15
ogasawarartg: if there are some upstream patches which have not been merged upstream should I go ahead and submit patches or wait till 2.6.31 finalizes?18:16
rtgsubmit18:16
manjo[TOPIC] Netbook Trees: status (sconklin, apw)18:16
MootBotNew Topic:  Netbook Trees: status (sconklin, apw)18:16
sconklin1rtg just rebased the karmic netbook tree, I will test as soon as I can.18:17
sconklin1All distro trees should now have the new debian directory structure in place18:17
sconklin1that's all18:17
manjo[TOPIC] Incoming Bugs: Regressions (ogasawara)18:17
MootBotNew Topic:  Incoming Bugs: Regressions (ogasawara)18:17
rtgsconklin1, I pushed the rebase earlier today18:17
ogasawaraThere were 4 regressions added to the list this week which smb and I reviewed yesterday and are currently investigating.18:17
manjo[TOPIC] Incoming Bugs: Bug day report (ogasawara)18:18
MootBotNew Topic:  Incoming Bugs: Bug day report (ogasawara)18:18
smb_tpFor bug 417732 it seem I found the source18:18
ubottuLaunchpad bug 417732 in linux "connecting gigaset USB device causes null pointer error" [Medium,In progress] https://launchpad.net/bugs/41773218:18
ogasawaraBug day stats can be seen at:18:18
ogasawarahttp://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090818.html18:18
MootBotLINK received:  http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090818.html18:18
ogasawaraI'd specifically like to point out that *all* 50 bugs in the community section were triaged!18:18
ogasawaraEveryone please give a big big thank you to Andres Mujica for his help!18:18
ogasawaraI'd also like to note that Andres is helping write a symptom based suspend/resume apport hook to help with bug reporting.18:18
* amitk ^5s Andres18:19
* smb_tp Thanks Andres18:19
manjo[TOPIC] Open Discussion: Anyone have any questions ?18:19
MootBotNew Topic:  Open Discussion: Anyone have any questions ?18:19
manjogoing 1s18:20
manjogoing 2s18:20
amitknext chair?18:20
manjogoing 3s18:20
manjo[TOPIC] Next Meeting Chair: lieb18:20
MootBotNew Topic:  Next Meeting Chair: lieb18:20
manjo#endmeeting18:21
MootBotMeeting finished at 12:21.18:21
liebmanjo, send me the materials etc18:21
=== fader is now known as fader|lunch
=== OldSchool is now known as they
=== fader|lunch is now known as fader
=== imlad is now known as imlad|away
=== imlad|away is now known as imlad
=== imlad is now known as imlad|away
=== imlad|away is now known as imlad
=== ember_ is now known as ember
=== they is now known as vorian
=== fader is now known as fader|away
=== imlad is now known as imlad|away

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