[15:57]  * skaet waves
[15:57] <bjf> o/
[15:58]  * charlie-tca waves
[15:58] <skaet> hi bjf,  charlie-tca
[15:58] <charlie-tca> Good morning, skaet
[16:00] <skaet> looks like its about that time
[16:00] <skaet> not sure if we have quorum or not
[16:00] <hggdh> morning all
[16:01] <skaet> morning hggdh :)
[16:01] <skaet> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is skaet.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <skaet> SRU/LTS bi-weekly synch meeting.
[16:01] <skaet> Reminder, please follow the convention  of using ".." on a separate line when you've finished typing.    Also, If someone wants to comment on the last point, please "o/", so we know to wait.
[16:01] <brendand> morning everyone
[16:02] <skaet> Karmic Koala (9.10) final announce is pending last kernel being published.
[16:02] <skaet> Hardy Heron Desktop (8.04) is waiting for signal as well.
[16:02] <skaet> Dapper Drake (6.06) Server will end of life in June 2011.
[16:02] <skaet> [LINK] https://wiki.ubuntu.com/Releases
[16:02] <MootBot> LINK received:  https://wiki.ubuntu.com/Releases
[16:02] <skaet> 10.04.3 - July 14-> July 21 - moving it out a week to balance better around Alpha 2.
[16:03] <skaet> ..
[16:03] <skaet> bjf, sconklin when will the last kernel's be ready for publishing for Karmic and Hardy?
[16:04] <sconklin> As soon as they are tested and cert and qa and the archive admins sign off. The stable kernel team is finished with them
[16:04] <skaet> sconklin,  thanks.
[16:05] <bjf> skaet, as per the email thread on this, this is not the last hardy kernel
[16:05] <skaet> bjf,  ok,  will go back through my inbox carefully,  catching up right now after a week off.
[16:06] <skaet> [TOPIC] Kernel SRU status - sconklin, bjf
[16:06] <MootBot> New Topic:  Kernel SRU status - sconklin, bjf
[16:06] <sconklin> pretty much already been covered. everything is done for the last cycle
[16:06] <sconklin> We're about to start another one.
[16:07] <sconklin> The dates we're working toward are in the canonical kernel team calendar. When the master calender has dates, we'll work to them
[16:08] <sconklin> sorry, ubuntu kernel calendar
[16:09] <sconklin> ..
[16:09] <brendand> o/
[16:09] <skaet> brendand, go ahead
[16:10] <brendand> does this commence the new 3 week cadence?
[16:10] <sconklin> yes
[16:10] <brendand> and is the new bug process going to be used?
[16:10] <sconklin> "new bug process" == what?
[16:10]  * JFo is curious
[16:11] <sconklin> oh, you mean workflow tools
[16:11] <sconklin> yes
[16:11] <brendand> sorry, maybe wrong words. i mean the new SRU workflow
[16:11] <sconklin> yes.
[16:11] <brendand> and lastly, where is the ubuntu kernel calendar, for future reference?
[16:12] <sconklin> looking for the url
[16:12] <bjf> i'll find it
[16:13] <skaet> sconklin, any concerns about 10.04.3 moving out a week?
[16:14] <sconklin> skaet: first I heard about it. Is it in a calendar? probably not a problem but I didn't know we had a master schedule for the next cycle yet
[16:15] <skaet> sconklin,  will be getting the master calendar up this week.  Just wanted to check with SRU kernel team before putting it up.
[16:15] <skaet> and let others here following this have a chance to flag issues too ;)
[16:15] <sconklin> I didn't know where it was scheduled originally even, so don;t know whether a week will make a difference
[16:16] <skaet> https://wiki.ubuntu.com/OneiricReleaseSchedule
[16:16] <sconklin> but I doubt it will be a problem
[16:16] <bjf> brendand, skaet, external url for the ubuntu kernel calendar: https://www.google.com/calendar/hosted/canonical.com/embed?src=50d02kfdekgcjdcpc970hh83f0@group.calendar.google.com&ctz=America/Los_Angeles&gsessionid=cp7W8N-DOwo48j_37lbwjg
[16:16] <skaet> thanks bjf
[16:16] <skaet> any other questions for the Kernel team?
[16:16] <brendand> bjf - thanks
[16:17] <skaet> [TOPIC] HW certification - ara
[16:17] <MootBot> New Topic:  HW certification - ara
[16:17] <ara> o/
[16:17] <ara> brendand will be presenting for the HW certification team from this meeting on
[16:17] <ara> brendand, ?
[16:17] <brendand> == Hardware Certification SRU Update ==
[16:17] <brendand> Certification testing completed for Lucid with 90/105 systems and tracking bug updated. Missing systems are due to lab issues.
[16:17] <brendand> http://people.canonical.com/~hwcert/sru-testing/current/lucid-proposed.html
[16:17] <brendand> Maverick testing in progress. 74/119 systems tested. No regressions found so far.
[16:17] <brendand> http://people.canonical.com/~hwcert/sru-testing/current/maverick-proposed.html
[16:17] <MootBot> LINK received:  http://people.canonical.com/~hwcert/sru-testing/current/lucid-proposed.html
[16:17] <MootBot> LINK received:  http://people.canonical.com/~hwcert/sru-testing/current/maverick-proposed.html
[16:17] <brendand> Natty testing in progress. 51/90 systems tested. No regressions found so far.
[16:17] <brendand> http://people.canonical.com/~hwcert/sru-testing/current/natty-proposed.html
[16:17] <MootBot> LINK received:  http://people.canonical.com/~hwcert/sru-testing/current/natty-proposed.html
[16:18] <brendand> ...
[16:18] <skaet> welcome brendand :)
[16:19] <skaet> what is the outlook on the final testing of Karmic and Hardy kernels?
[16:19] <brendand> skaet - we aren't testing Karmic or Hardy
[16:20] <skaet> brendand, we're at a bit of an impass then.
[16:20] <bjf> o/
[16:20] <skaet> final kernels have been published, and waiting for cert and qa to weigh in so we can announce EOL.
[16:20] <skaet> bjf go ahead
[16:21] <sconklin> o/
[16:21] <bjf> i think we need someone from the QA team, but I think they were going to test this week
[16:21] <sconklin> brad first
[16:21] <ara> o/
[16:21] <ara> :)
[16:21] <bjf> ..
[16:21] <sconklin> two things.
[16:21] <skaet> jibel, hggdh, ^^ ??
[16:21] <skaet> go ahead sconklin
[16:21] <sconklin> First, slipping .3 a week actually lines up nicely with our schedule
[16:22] <sconklin> second, this is not a final Lucid kernel. We need to stop writing that
[16:22] <sconklin> sorry, Hardy
[16:22] <sconklin> There is no final desktop kernel
[16:23] <sconklin> we continue to produce kernels until server goes out of support
[16:23] <sconklin> ..
[16:23] <skaet> sconklin, you had me worried about the lucid ;)   noted about hardy- I'll be a bit more careful.
[16:23] <sconklin> lucid's time will come ;-)
[16:24] <skaet> ara,  go ahead
[16:24] <ara> thanks
[16:24] <ara> in the hw cert team we are never testing karmic or hardy. so you guys should only wait on QA for those two
[16:25] <ara> ..
[16:25] <skaet> hmm...
[16:26] <skaet> I'm going to need to go do some homework then.
[16:26] <skaet> will follow up on email list if warranted.
[16:26] <skaet> anyone around from QA?
[16:27] <hggdh> yes
[16:27] <hggdh> skaet: ^
[16:27] <skaet> :)
[16:28] <hggdh> we will get it done
[16:28] <skaet> hggdh,  cool.  you ready to give a status today, or will jibel be doing it?
[16:29] <hggdh> skaet: I am not prepared for it, I would rather have jibel doing it (if you do not mind)
[16:29] <skaet> no worries.
[16:29] <skaet> any other questions for brendand ?
[16:29] <skaet> [TOPIC] QA status - jibel
[16:29] <MootBot> New Topic:  QA status - jibel
[16:30]  * skaet looks around for jibel?
[16:30] <skaet> [TOPIC] OEM priorities - vanhoof
[16:30] <MootBot> New Topic:  OEM priorities - vanhoof
[16:31] <vanhoof> skaet: nothing pressing for the next cycle
[16:31] <skaet> thanks vanhoof.
[16:31] <skaet> is martin s. around?
[16:32] <skaet> ok,
[16:32] <skaet> pitti has a conflict - but no red flags from him.
[16:32] <skaet> support has flagged two bugs to the individual teams
[16:33] <skaet> TOPIC] New business, last chance for general questions? - all
[16:33] <skaet> [TOPIC] New business, etc...
[16:33] <MootBot> New Topic:  New business, etc...
[16:34] <hggdh> skaet: for the record, hardy kernel was approved by QA last week
[16:34] <skaet> thanks hggdh,  appreciate the update.  :)
[16:34]  * skaet looks around
[16:34] <hggdh> and we will start with Maverick this week (oldest pending kernel)
[16:35]  * hggdh is done now ;-)
[16:35] <skaet> hggdh,  could you look at Karmic so we can formally EOL it?
[16:35] <hggdh> skaet: certainly
[16:35] <skaet> thanks!
[16:35] <skaet> #endmeeting
[16:35] <MootBot> Meeting finished at 10:35.
[16:36] <ara> thanks skaet
[16:36] <skaet> thanks sconklin, bjf, ara, brendand, hggdh
[16:36] <brendand> thanks skaet
[16:36] <hggdh> thank you, skaet
[16:37] <hggdh> skaet: I do not see any karmic kernel in http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html
[16:39] <skaet> hggdh,  lets take this up with sconklin and bjf in the #ubuntu-kernel channel.
[16:40] <hggdh> skaet: roger wilco
[16:40] <skaet> :)
[18:01] <jdstrand> o/
[18:02] <jjohansen> \o
[18:02] <jdstrand> shall we get started?
[18:03] <micahg> o/
[18:03] <kees> \o
[18:03] <sbeattie> o/
[18:03] <jdstrand> hi everyone! :)
[18:03] <jdstrand> #startmeeting
[18:03] <MootBot> Meeting started at 12:03. The chair is jdstrand.
[18:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:03] <jdstrand> The meeting agenda can be found at:
[18:03] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:03] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:03] <jdstrand> [TOPIC] Review of any previous action items
[18:03] <MootBot> New Topic:  Review of any previous action items
[18:03] <jdstrand> blueprints should be (mostly) together now and our release status page up to date: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Oneiric
[18:04] <jdstrand> our blueprints for this release of course fell out of our UDS discussions
[18:04] <kees> oh good, I see the workitem tracker has been reset
[18:04] <jdstrand> kees: yes! I had a feeling it would happen today :)
[18:04] <jdstrand> I think kees and I need to still do some light review, but by and large the work items should be all set
[18:05] <jdstrand> I don't think there is a lot to spec out, beyond dbus/apparmor
[18:05] <jdstrand> [TOPIC] Weekly stand-up report
[18:05] <MootBot> New Topic:  Weekly stand-up report
[18:05] <jdstrand> I'll go first
[18:05] <jdstrand> I'm in the happy place this week (yea)
[18:06] <jdstrand> I have a dbus-glib update I am getting back into. some my testing for that will help me define the test cases for the dbus/apparmor bp, which I hope to start looking at again this week. depending on what pops up, it is at least theoretically possible for me to pick up another update
[18:07] <jdstrand> other than a few administrative things that don't I don't need to waste time here with, I think that is it from me
[18:07] <jdstrand> kees: you're up
[18:07] <kees> okay, I'm on triage. I've at least got exim4 to do, and the hardy kernel announcement
[18:08] <kees> after that, I'm trying to grind out all the graph data work items, since those should fall quickly if I can just get u-c-t to behave.
[18:08] <jdstrand> \o/
[18:08] <kees> I've got some oneiric kernel work to do too (nx-emu rebase)
[18:08]  * jdstrand hugs kees
[18:08] <kees> :)
[18:08]  * kees hugs jdstrand
[18:09] <kees> I'll probably have some MIR work sprinkled around too. we'll see. :)
[18:09] <kees> that's it from me. mdeslaur is up.
[18:09] <jdstrand> mdeslaur: is on holiday today
[18:09] <jdstrand> s/:/
[18:09] <jdstrand> s://
[18:09] <jdstrand> hah
[18:09] <jdstrand> sbeattie: you're up. I can't get my regex right
[18:09] <kees> dur
[18:09] <kees> heh
[18:10]  * sbeattie waits for the regexs to finish.
[18:10] <jdstrand> s/://
[18:10] <jdstrand> :P
[18:10] <sbeattie> I'm on community this week, after triaging last week.
[18:10] <sbeattie> I have an apr update in the pipe, though I'm now trying to track down why the lucid arm build failed in a testcase.
[18:11] <sbeattie> (hooray for the vagaries of chroot builds)
[18:12] <sbeattie> after that, I want to start poking at my apparmor work items for this cycle.
[18:12] <sbeattie> I also have some post uds administrivia to complete.
[18:12] <jdstrand> interesting. I would guess that if it was armel, it wouldn't be chroot specific, but I've not looked at it at all
[18:12] <jdstrand> (just armel that is)
[18:13]  * jdstrand also has post uds administrivia
[18:13] <sbeattie> jdstrand: the testcase that failed had to do with mutexs, so I'm suspecting that its a difference between kernels
[18:13] <jdstrand> ah
[18:13] <jdstrand> fun
[18:14] <sbeattie> yeah. and by yeah, I mean no.
[18:14] <sbeattie> I think that's it for me.
[18:14] <jdstrand> hehe
[18:14] <jdstrand> micahg: you're up!
[18:14] <micahg> so, I have that thunderbird regression with the empty menubar to publish today
[18:15] <micahg> mozilla has announced some of there plans for release schedules
[18:15] <micahg> 3.5 is EOL (doesn't afffect us, just seamonkey will need to go to 2.1.x)
[18:15] <micahg> 3.6 will have updates for the moment
[18:15] <micahg> 4's security update will be 5, so we'll have to upgrade natty on june 21
[18:16] <nxvl> are we still talking about TB?
[18:16] <micahg> nxvl: no, sorry, Firefox
[18:16] <nxvl> i assumed :D
[18:16] <micahg> Thunderbird will stay on 3.1.x for the moment
[18:16] <micahg> natty will be our test migration case
[18:17] <micahg> I'll be drafting a page to track what we need to do before the upgrade
[18:17] <micahg> chrisccoulson has done some awesome work to make these transitions smoother WRT language updates
[18:18] <micahg> we'll review at the rally how the natty upgrade went and plan the other migrations (firefox for lucid/maverick and thunderbird in stable)
[18:19] <micahg> so, after drafting the initial plan, I want to try to get the pending webkit updates out
[18:20] <micahg> and I'm expecting a chromium update either this week or early next week
[18:20] <micahg> that's it for me
[18:20] <jdstrand> micahg: sounds great. thanks!
[18:20] <jdstrand> [TOPIC] Miscellaneous and Questions
[18:20] <MootBot> New Topic:  Miscellaneous and Questions
[18:22] <jdstrand> jjohansen: I'll probably be talking to you later in the week re libapparmor for dbus (all I need is the api call and it to return something based on the env, like we discussed)
[18:22] <jdstrand> other than that, I don't have anything to add
[18:22] <jjohansen> jdstrand: okay, sounds good
[18:22] <jdstrand> does anyone have any other questions or items to discuss?
[18:23] <jdstrand> going once...
[18:24] <jdstrand> going twice...
[18:24] <jdstrand> thanks everyone! :)
[18:24] <jdstrand> #endmeeting
[18:24] <MootBot> Meeting finished at 12:24.
[18:24] <kees> thanks jdstrand!
[18:24] <sbeattie> jdstrand: thanks!
[18:25] <micahg> thanks jdstrand
[18:25] <jdstrand> you bet! :)
[20:01] <Laney> DMB?
[20:01]  * stgraber waves
[20:01]  * Laney rings a bell
[20:01]  * bdrung_ waves.
[20:01] <Laney> hiya
[20:02] <stgraber> I was just checking my calendar to make sure I didn't have timezone conversion issue again ;)
[20:02] <psusi> o/
[20:02] <Laney> google now reminds me via SMS :-)
[20:02] <Laney> persia: maco cody-somerville
[20:02] <persia> o/
[20:02] <maco> hello
[20:03] <stgraber> wow, we almost have everyone around this time!
[20:03] <Laney> who wants to chair?
[20:04] <Laney> (we should start deciding at the end of the meeting)
[20:04] <persia> #startmeeting
[20:04] <MootBot> Meeting started at 14:04. The chair is persia.
[20:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[20:04] <persia> [LINK] https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
[20:04] <MootBot> LINK received:  https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
[20:05] <persia> [TOPIC] Review progress of probationary period of Marco Rodrigues
[20:05] <MootBot> New Topic:  Review progress of probationary period of Marco Rodrigues
[20:05] <persia> cody-somerville, ?
[20:05] <Laney> don't think he is here, and this has been on the agenda for /months/ now
[20:05] <persia> We should have done it last time: he was there then.
[20:06] <persia> Right.
[20:06] <Laney> We're waiting for a report.
[20:06] <persia> [TOPIC] PerPackageUploader Application for John Rigby
[20:06] <MootBot> New Topic:  PerPackageUploader Application for John Rigby
[20:06] <persia> [LINK] https://wiki.ubuntu.com/JohnRigby/DeveloperApplication-LinaroLinuxAndUBoot
[20:06] <MootBot> LINK received:  https://wiki.ubuntu.com/JohnRigby/DeveloperApplication-LinaroLinuxAndUBoot
[20:06] <persia> jcrigby, How are you today?
[20:06] <jcrigby> yes for once:)
[20:06] <ScottK> On the kmos issue, I think it's a bit unfair to leave it there where people who are interested in the topic never know when it's going to come up.
[20:07] <ScottK> I wish you all would pick a meeting when you're going to deal with it and get it over with.
[20:07] <Laney> We should take it to mail and bring it back when it's ready.
[20:07] <Laney> I agree
[20:07] <cody-somerville> Apologies about the kmos situation. +1 for Laney and ScottK's suggestion.
[20:07] <persia> [AGREED] Remove Review progress of probationary period of Marco Rodrigues from the agenda until there is planned discussion
[20:07] <MootBot> AGREED received:  Remove Review progress of probationary period of Marco Rodrigues from the agenda until there is planned discussion
[20:07] <persia> jcrigby, Thanks for coming today.
[20:09] <jcrigby> glad to be here
[20:10] <persia> jcrigby, Are you involved in Ubuntu in any way beyond the packages you mention?
[20:10] <jcrigby> not really no
[20:10] <hrw> hi
[20:10] <hrw> do we have quorum today?
[20:10] <bdrung_> yes
[20:11] <maco> yes
[20:11] <persia> jcrigby, What do you find most difficult about packaging best practices?
[20:11] <jcrigby> remembering the incantations
[20:12] <Laney> jcrigby: (after persia's question[s]) Can you briefly explain the major freezes in the Ubuntu development cycle and how they affect your packages?
[20:12] <jcrigby> Laney, I am obviously unprepared for that one
[20:12] <bdrung_> jcrigby: why do we have special linaro packages in addition to the normal package (e.g. u-boot and u-boot-linaro)?
[20:12] <jcrigby> Linaro is on its own schedule
[20:13] <maco> oh, good to know
[20:13] <jcrigby> bdrung_, actually u-boot-linaro is the only u-boot now days
[20:13] <jcrigby> ubuntu uses u-boot-linaro
[20:13] <Laney> Are these packages not subject to the Ubuntu release schedule?
[20:13] <hrw> maco: we (Linaro) release ~month after Ubuntu
[20:14] <jcrigby> Laney, for this oneiric Linaro is releasing monthly
[20:14] <hrw> maco: but recently we switched most of teams to monthly releases
[20:14] <bdrung_> jcrigby: what does u-boot-linaro contain in comparison to upstream u-boot?
[20:14] <jcrigby> Laney, and for releases after ff we will release via a ppa to avoid sru issues
[20:14] <persia> I believe the packages *should* be subject to the release schedule, as there are images that depend upon them shipped as part of the release.
[20:15] <maco> jcrigby: was that ff = feature freeze or final freeze?
[20:15] <jcrigby> maco final
[20:15] <jcrigby> we can do ffe's for feature freeze
[20:16] <persia> jcrigby, What considerations do you make when requesting an FFe?
[20:16] <jcrigby> at that point I only allow bug fixes that are must haves for the release
[20:17] <jcrigby> no new "nice" features
[20:17] <persia> Do you maintain separate for-ubuntu and linaro-next trees for this?
[20:17]  * cody-somerville has to jet; will write e-mail to DMB when I get back.
[20:17] <Laney> see you
[20:17] <jcrigby> persia, I keep -next git trees but those do not have packaging bits in them
[20:18] <jcrigby> persia, they are for board enablement folks
[20:18] <persia> That makes sense.
[20:19] <jcrigby> on the kernel side I actually do keep a work in progress (wip) tree that does have the packaging in it
[20:19] <jcrigby> that is for people that are willing to build there own packaged kernel
[20:19] <jcrigby> and I have tried to help people that want to do that but lack the knowledge
[20:20] <jcrigby> I have also helped the linaro landing teams with their packagig
[20:20] <jcrigby> since they are usually enablement people not packaging people
[20:21] <persia> Anyone else with more questions?
[20:21] <Laney> nope
[20:21] <stgraber> nope
[20:21] <maco> nope
[20:22] <geser> nope
[20:22] <bdrung_> nope
[20:22] <persia> [VOTE] Approve John Rigby (jcrigby) for PerPackage Upload rights to u-boot-linaro and linux-linaro-*
[20:22] <MootBot> Please vote on:  Approve John Rigby (jcrigby) for PerPackage Upload rights to u-boot-linaro and linux-linaro-*.
[20:22] <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
[20:22] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[20:23] <Laney> +0
[20:23] <MootBot> Abstention received from Laney. 0 for, 0 against. 1 have abstained. Count is now 0
[20:23] <stgraber> +0
[20:23] <MootBot> Abstention received from stgraber. 0 for, 0 against. 2 have abstained. Count is now 0
[20:25] <geser> +1
[20:25] <MootBot> +1 received from geser. 1 for, 0 against. 2 have abstained. Count is now 1
[20:25] <maco> +1 given slangasek's testimonial and an understanding of FF, i'm ok with him
[20:25] <MootBot> +1 received from maco. 2 for, 0 against. 2 have abstained. Count is now 2
[20:25] <bdrung_> +1
[20:25] <MootBot> +1 received from bdrung_. 3 for, 0 against. 2 have abstained. Count is now 3
[20:25] <persia> +1
[20:25] <MootBot> +1 received from persia. 4 for, 0 against. 2 have abstained. Count is now 4
[20:25] <persia> [ENDVOTE]
[20:25] <MootBot> Final result is 4 for, 0 against. 2 abstained. Total: 4
[20:26] <persia> jcrigby, Congratulations.
[20:26] <stgraber> jcrigby: congrats!
[20:26] <jcrigby> thanks
[20:26] <Laney> :-)
[20:27] <persia> [TOPIC] Contributing Developer application for  Phillip Susi
[20:27] <MootBot> New Topic:  Contributing Developer application for  Phillip Susi
[20:27] <persia> [LINK] https://wiki.ubuntu.com/PhillipSusi/DeveloperApplication
[20:27] <MootBot> LINK received:  https://wiki.ubuntu.com/PhillipSusi/DeveloperApplication
[20:27] <persia> psusi, Thanks for coming today.
[20:29] <persia> Or,maybe next time.
[20:29] <maco> psusi: care to introduce?
[20:30] <maco> brad figg i guess?
[20:31] <persia> [TOPIC] PerPackage Uploader application for Brad Figg
[20:31] <MootBot> New Topic:  PerPackage Uploader application for Brad Figg
[20:31] <persia> [LINK] https://wiki.ubuntu.com/BradFigg/DeveloperApplication
[20:31] <MootBot> LINK received:  https://wiki.ubuntu.com/BradFigg/DeveloperApplication
[20:31] <JFo> yay bjf!
[20:31] <persia> bjf, Thanks for coming today
[20:31] <bjf> np
[20:32] <Laney> Isn't there a kernel package set?
[20:32] <stgraber> there's
[20:32] <persia> You ask for upload rights to the linux-* packages.  Do you want that, or did you mean to apply to be part of the kernel uploaders team?
[20:32] <maco> i think this was clarified on email as "kernel package set"
[20:33] <persia> I thought so, just wanted to be clear.
[20:33] <stgraber> http://paste.ubuntu.com/612008/
[20:33] <MootBot> LINK received:  http://paste.ubuntu.com/612008/
[20:33] <persia> [LINK] https://launchpad.net/~ubuntu-kernel-uploaders
[20:33] <MootBot> LINK received:  https://launchpad.net/~ubuntu-kernel-uploaders
[20:33] <bjf> I'm Brad Figg. I've been an Ubuntu contributor since joining Canonical two years ago. I am a member of the Kernel Team.
[20:33] <bjf> I've been a linux developer/user for many years.
[20:33] <maco> "I was just trying to be clear what I was asking for, if there is a kernel package set then that is what I'm going for."  <-- what brad said when Laney asked
[20:34] <bjf> I am currently working on the stable kernel maintenance.  I've been doing stable kernel maintenance for two dev cycles and am schedule to continue doing same for another two cycles.
[20:34] <bjf> I'm applying for upload rights for the linux kernel packages.
[20:34] <bjf> I'm proud of the stable work that I've done, we've made some significant changes to the
[20:34] <bjf> stable maintenance process.
[20:34] <bjf> ~
[20:34] <bjf> i'm good at cut/paste if that is a requirement :-)
[20:34] <sconklin> fwiw I've been signing Brad's packages (sponsoring his uploads) for six months, and he's fully capable
[20:35] <Laney> Can you explain how a stable kernel update is typically QAd?
[20:36] <Laney> Also, does the kernel team work with Debian's at all? ;-)
[20:36] <bjf> laney, it's a multi-step process, are you familiar with the kernel cadence that we've gone to?
[20:36] <Laney> somewhat
[20:36]  * bdrung_ isn't.
[20:36] <persia> Please share
[20:36] <bjf> laney, yes, we discuss things regularly with the debian kernel folks
[20:36] <bjf> persia, will do :-)
[20:37] <persia> (especially as ogasawara credits you with bringing order to it)
[20:37] <sconklin> https://wiki.ubuntu.com/Kernel/StableReleaseCadence
[20:37] <bjf> currently, we are moving to a three week cadence
[20:37] <sconklin> excuse me pasting links
[20:37] <bjf> week 1, we prepare kernels and upload packages (upload to the kernel team ppa)
[20:38] <bjf> week 2, we require verification of LP bugs that have been fixed via the uploaded kernel
[20:38] <bjf> any bugs that fail verification or are not verified, the corresponding commits are reverted and new packages are uploaded
[20:38] <bjf> week 3, the QA and Certification teams take over, and run their tests.
[20:39] <Laney> when does the upload to -proposed happen? what kind of interaction is there with the Ubuntu SRU team?
[20:39] <maco> bjf: ever had any problems where the reverts after week 2 caused regressions, maybe due to side-effects/interactions between patches & disappearing patches?
[20:39] <bjf> the QA tests are composed of: qbench, tbench tiobench, security tests (crafted by the security team) and some ltp lite tests
[20:40] <Laney> (and regular SRU verification)
[20:40] <bjf> laney, generally we just ping them to pocket-copy, we are changing this as well to use an LP bug for workflow, maybe sconklin can post a url for that as well :-)
[20:41] <sconklin> looking
[20:41] <persia> bjf, pocket-copy to where?
[20:41] <bjf> maco, yes, same proceedure, we revert the commit, roll a new package and upload
[20:41] <bjf> persia, from our ppa to -proposed
[20:41] <bjf> maco, once the new package has been uploaded, qa and cert testing starts again
[20:42] <bjf> maco, this could go on for some time, however, it hasn't in the last two dev cycles
[20:42]  * Laney is done with questions
[20:42] <bjf> laney, maco, bdrung_ persia the purpose of moving to this cadence is predictability
[20:43] <maco> bjf: thanks, thats the bit i was unsure about :)
[20:43] <bjf> it was very difficult in the past to be able to give some indication of when a patch was going to get out
[20:43]  * sconklin is unable to get launchpad qastaging to do anything other than time out
[20:43] <sconklin> that's where our example bug is
[20:43] <bjf> as it is now, worst case (baring reversions) is 6 weeks from when a patch is accepted until it hits -updates
[20:44] <bdrung_> bjf: some packagers feel that it's hard to get their changes into the kernel due to all the rules. are there plans to change that?
[20:44] <bjf> bdrung_, no changes to the rules, we are actually quite flexible (our opinion) and will discuss changes with anyone
[20:45] <bjf> bdrung_, however, stability is crucial
[20:45] <sconklin> here's one that doesn't have the team assignments made, but you can see how we track workflow tasks https://bugs.qastaging.launchpad.net/kernel-sru-workflow/verification-testing/+bug/718866
[20:45] <bjf> sconklin, thanks
[20:45] <persia> bjf: In your application, you seem to have skipped one of my favourite bits: What single thing in Ubuntu do you think should most be improved?
[20:46] <bdrung_> bjf: i was thinking about changes for the development version (currently oneiric).
[20:46] <bjf> persia, thinking about it
[20:47] <bjf> bdrung_, well, we certainly prefer that we get any changes from upstream or that the changes we take are heading upstream, we are not a test kernel for everyone's crack
[20:47] <bjf> bdrung_, the larger the community, the more conservative we need to be
[20:48] <bdrung_> bjf: i can remember that i once want to push a fix from lirc into the kernel. it took me ages to do that.
[20:48] <bjf> bdrung_, we are already put out the most recent upstream kernel of any distro (i mean we track the upstream kernel the closest)
[20:48] <bjf> bdrung_, were your changes going upstream?
[20:49] <bdrung_> bjf: it was a backported upstream patch
[20:49] <bjf> bdrung_, ok, i don't know the specifics, but that usually fits within our rules, it can depend on the complexity of the backport though
[20:50] <bdrung_> i found it: https://launchpad.net/ubuntu/+source/lirc/0.8.6-0ubuntu4.1
[20:50] <bjf> bdrung_, our rules are not much difference than those of upstream stable maint.
[20:50] <bdrung_> the process for the kernel felt very bureaucratic
[20:51] <bjf> bdrung_, it can be, but again, stability and no-regressions are what we are striving for
[20:52] <sconklin> This is team policy and not Brad's. If upstream won't take it, it's very unlikely we will.
[20:52] <bjf> persia, i still don't really know how to answer your question, there are specific parts of the distro that i'd like to see changed/influenced (like the switch to unity)
[20:53] <maco> persia: that's the part i always want to skip too
[20:53] <bjf> persia, i also think UDS could be better in certain ways
[20:54] <persia> bjf, Well, I'd encourage you to think about it.  We know we aren't perfect, but unless we can identify what is wrong, it's hard to improve.
[20:54] <bjf> persia, remember, i'm kind of an old fart, i like my desktop the way that it was, this new fangled stuff takes some getting used to :-)
[20:54] <persia> On a related note, what do you feel is your weakest skill in developing for Ubuntu?
[20:54] <bjf> and i'm resisting
[20:55] <bjf> my first thoughts would be in interaction with the community, but i've been told that i'm not as bad as i think
[20:55] <bdrung_> bjf, sconklin: ok
[20:56] <bjf> to me, this is mostly a job and not my life
[20:57] <bdrung_> bjf: re unity - all the gnome-panel lovers could unity and maintain gnome-panel. then a user can decide between unity, gnome3, and ubuntu classic (gnome-panel)
[20:58] <bjf> bdrung_, agreed
[20:58] <persia> geser, stgraber, any questions?
[20:58] <stgraber> nope
[20:59] <geser> nope
[20:59] <persia> [VOTE] Approve Brad Figg (bjf) as an Ubuntu Kernel Uploader
[20:59] <MootBot> Please vote on:  Approve Brad Figg (bjf) as an Ubuntu Kernel Uploader.
[20:59] <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
[20:59] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[20:59] <maco> +1
[20:59] <MootBot> +1 received from maco. 1 for, 0 against. 0 have abstained. Count is now 1
[20:59] <Laney> +1 // Strong testimonials, obviously good skills in designing the new cadence
[20:59] <MootBot> +1 received from Laney. 2 for, 0 against. 0 have abstained. Count is now 2
[20:59] <persia> +1
[20:59] <MootBot> +1 received from persia. 3 for, 0 against. 0 have abstained. Count is now 3
[20:59] <bdrung_> +1
[20:59] <MootBot> +1 received from bdrung_. 4 for, 0 against. 0 have abstained. Count is now 4
[20:59] <stgraber> +1
[20:59] <MootBot> +1 received from stgraber. 5 for, 0 against. 0 have abstained. Count is now 5
[21:00] <geser> +1
[21:00] <MootBot> +1 received from geser. 6 for, 0 against. 0 have abstained. Count is now 6
[21:00] <persia> [ENDVOTE]
[21:00] <MootBot> Final result is 6 for, 0 against. 0 abstained. Total: 6
[21:00] <bdrung_> can we extend this meeting one hour to reduce the backlog?
[21:00] <persia> bjf, Congratulations!
[21:00]  * persia can stay
[21:00] <ogasawara> \o/, congrats bjf
[21:00] <bjf> thanks!
[21:00] <sconklin> \o/
[21:00] <bdrung_> congrats
[21:00] <stgraber> not sure I can stay for another full hour, but at least for another ~30 minutes
[21:00]  * hrw can appear at 30-40 minutes from now. have to go now
[21:00] <sconklin> less work for me!
[21:01] <persia> We need one more to stay quorate.
[21:01] <maco> guess i can stick around a bit longer
[21:01] <Laney> I've got to be on the water in 30 minutes, I'm afraid
[21:01]  * hrw -> out for now
[21:02] <persia> No worries.  It's a one-hour meeting.  Extension is purely voluntary :)
[21:02] <persia> [TOPIC] PerPackageUploader application for  Rosen Diankov
[21:02] <MootBot> New Topic:  PerPackageUploader application for  Rosen Diankov
[21:02] <persia> [LINK] https://wiki.ubuntu.com/RosenDiankov/DeveloperApplication
[21:02] <MootBot> LINK received:  https://wiki.ubuntu.com/RosenDiankov/DeveloperApplication
[21:02]  * geser has time to process some more
[21:03] <stgraber> anyone knows his IRC nickname ? can't find it on either the wiki page or on LP
[21:03] <persia> Neither I.
[21:03] <persia> Rosen, are you here?
[21:04] <persia> OK.  Moving on.
[21:04] <persia> [TOPIC] Review of Bazaar Package Set
[21:05] <MootBot> New Topic:  Review of Bazaar Package Set
[21:05] <persia> poolie, jelmer, do you have time to discuss this?
[21:05] <psusi> shoot, I had to run home to meet the cable guy, did I miss it again?
[21:05] <persia> psusi, You did, but we extended, so you're next.
[21:06] <psusi> whew...
[21:06] <persia> Any DMB members have comments on the Bazaar Package set they want in minutes?
[21:07] <bdrung_> psusi: one question to think about: What do you like least in Ubuntu?
[21:07] <persia> [TOPIC] Contributing Developer application for Ricardo Salveti
[21:07] <MootBot> New Topic:  Contributing Developer application for Ricardo Salveti
[21:07] <persia> [LINK] https://wiki.ubuntu.com/RicardoSalveti/UniverseContributorApplication
[21:07] <MootBot> LINK received:  https://wiki.ubuntu.com/RicardoSalveti/UniverseContributorApplication
[21:07] <geser> persia: is there much to discuss about the bzr package set besides what packages belong there?
[21:07] <bdrung_> persia: a Bazaar package set sounds plausable
[21:07] <persia> Sorry.  I was too fast.
[21:08] <persia> [TOPIC] Review of Bazaar Package Set
[21:08] <MootBot> New Topic:  Review of Bazaar Package Set
[21:08] <persia> geser, I don't think so, really.
[21:08] <persia> bdrung_, Do you suggest we should just do it, as we have two PPUs who have the same set?
[21:08] <stgraber> IIRC the DMB was the one asking for the set when reviewing jelmer's application. List looks good to me (quite similar to an "apt-cache search bzr" and matches rights we've already given to these applying for bzr upload rights)
[21:08] <maco> persia: i'm in favour of it
[21:09] <stgraber> +1
[21:09] <persia> OK.
[21:09] <stgraber> they are quite likely to ask for the same packages to be added to their respective PPU lists, so it's best to create a package set for it
[21:09] <geser> +1 for a bzr package set based on the bzr ppu right from jelmer and poolie
[21:09] <persia> [VOTE] Create a Bazaar Package Set and migrate poolie and jelmer to membership in an associated group.
[21:09] <MootBot> Please vote on:  Create a Bazaar Package Set and migrate poolie and jelmer to membership in an associated group..
[21:09] <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
[21:09] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[21:09] <stgraber> +1
[21:09] <MootBot> +1 received from stgraber. 1 for, 0 against. 0 have abstained. Count is now 1
[21:09] <persia> +1 : makes our lives easier, really
[21:09] <MootBot> +1 received from persia. 2 for, 0 against. 0 have abstained. Count is now 2
[21:09] <geser> +1
[21:09] <MootBot> +1 received from geser. 3 for, 0 against. 0 have abstained. Count is now 3
[21:10] <bdrung_> +1
[21:10] <MootBot> +1 received from bdrung_. 4 for, 0 against. 0 have abstained. Count is now 4
[21:10] <maco> +1
[21:10] <MootBot> +1 received from maco. 5 for, 0 against. 0 have abstained. Count is now 5
[21:10] <persia> [ENDVOTE]
[21:10] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[21:10] <persia> That was easy :)
[21:10] <persia> [TOPIC] Contributing Developer application for Ricardo Salveti
[21:10] <MootBot> New Topic:  Contributing Developer application for Ricardo Salveti
[21:11] <persia> [LINK] https://wiki.ubuntu.com/RicardoSalveti/UniverseContributorApplication
[21:11] <MootBot> LINK received:  https://wiki.ubuntu.com/RicardoSalveti/UniverseContributorApplication
[21:11] <persia> rsalveti, Thanks for being here today
[21:11] <bdrung_> this seems to be a good way. let the people get PPU right and create a set if two people have the same package in their list
[21:11] <persia> Indeed.
[21:11] <stgraber> yep
[21:12] <geser> persia: can you please add the bzr packages to the minutes? to have them documented somewhere easy to find again later
[21:12] <persia> geser, The list? Sure.
[21:12] <persia> Well, maybe not.  We'll come back.
[21:12] <persia> [TOPIC] Contributing Developer application for Phillip Susi
[21:12] <geser> persia: or the wildcards (e.g. bzr-*)
[21:12] <MootBot> New Topic:  Contributing Developer application for Phillip Susi
[21:13] <persia> [LINK] https://wiki.ubuntu.com/PhillipSusi/DeveloperApplication
[21:13] <MootBot> LINK received:  https://wiki.ubuntu.com/PhillipSusi/DeveloperApplication
[21:13]  * hrw back in 3
[21:13] <maco> did psusi come back?
[21:13] <psusi> yes
[21:13] <persia> psusi, Glad you could make it (even a bit late).
[21:13] <stgraber> yeah! ;)
[21:13] <maco> oh hello
[21:14] <psusi> woohoo, finally ;)
[21:14] <persia> psusi, So, now that you've had some time to think, what do you like least in Ubuntu?
[21:14] <psusi> I've not really been able to come up with an answer to that really... I dislike bugs
[21:15] <persia> Do you think we could do a better job to squash bugs somehow?
[21:15] <psusi> other than more manpower?
[21:16] <bdrung_> psusi: how to get more manpower into this area and how to use the manpower more efficiently
[21:16] <bdrung_> ?
[21:16] <persia> If you think that's the solution, I'll ask how you think we can attract the necessary resources :)
[21:16] <persia> (if you have another solution, please share)
[21:17] <geser> psusi: picking up the question from your application page: did you think about maintaining e2defrag in Debian?
[21:17] <psusi> I think the system is pretty efficient
[21:18] <psusi> especially these days with UDS
[21:18] <bdrung_> psusi: are you happy about the sponsoring?
[21:18] <psusi> err, UDD
[21:18] <psusi> yea... UDD sponsorship has become very smooth lately, especially with the patch pilot program
[21:18] <bdrung_> great to hear that
[21:18] <maco> any parts of the bug triage/squash process that you think are particularly in need of change?
[21:19] <psusi> I'm not a debian user so that would make becoming a DD a bit tricky I think
[21:19] <maco> psusi: i'm not either, but i'm going through the DM process *duck*
[21:19] <bdrung_> psusi: you don't have to be a debian user. you don't even need to be a DD for maintaining a package in debian.
[21:20] <maco> (DM is like PPU)
[21:20] <psusi> I may end up doing that eventually, but I figured I'd start with motu
[21:20] <bdrung_> psusi: it's easier to start with DM if you really care about a specific package (especially if it's new)
[21:22] <persia> Anyone with further questions for psusi?
[21:22] <bdrung_> no
[21:22] <psusi> actually I guess one thing that bothers me is bugs that sit around for years and grow stale and ignored
[21:23] <stgraber> persia: I'm ready to vote
[21:24] <persia> [VOTE] Approve Phillip Susi (psusi) as a Contributing Developer
[21:24] <MootBot> Please vote on:  Approve Phillip Susi (psusi) as a Contributing Developer.
[21:24] <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
[21:24] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[21:24] <bdrung_> +1
[21:24] <MootBot> +1 received from bdrung_. 1 for, 0 against. 0 have abstained. Count is now 1
[21:24] <maco> +1
[21:24] <MootBot> +1 received from maco. 2 for, 0 against. 0 have abstained. Count is now 2
[21:24] <geser> +1
[21:24] <MootBot> +1 received from geser. 3 for, 0 against. 0 have abstained. Count is now 3
[21:24] <persia> +1 : Your work goes well beyond the usual measurement of significant and sustained
[21:24] <MootBot> +1 received from persia. 4 for, 0 against. 0 have abstained. Count is now 4
[21:24] <stgraber> +1
[21:24] <MootBot> +1 received from stgraber. 5 for, 0 against. 0 have abstained. Count is now 5
[21:24] <persia> [ENDVOTE]
[21:24] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[21:24] <persia> psusi, Congratulations !
[21:24] <psusi> woohoo!  finally ;)
[21:25] <stgraber> psusi: congrats!
[21:25] <bdrung_> persia: especially sustained
[21:25] <persia> stgraber, You said you might have to go?
[21:25] <stgraber> how many more do we have ?
[21:25] <persia> bdrung_, Yeah.  I remember psusi being around when I was still lurking.
[21:26] <persia> stgraber, 2 noshows and 2 outstanding.
[21:26] <hrw>  /me ?
[21:26]  * bdrung_ is still here.
[21:26] <stgraber> ok, I can still continue for a while
[21:27] <persia> [TOPIC] Contributing Developer Application for Marcin Juszkiewicz
[21:27] <MootBot> New Topic:  Contributing Developer Application for Marcin Juszkiewicz
[21:27] <persia> [LINK] https://wiki.ubuntu.com/MarcinJuszkiewicz/DeveloperApplication-PPU
[21:27] <MootBot> LINK received:  https://wiki.ubuntu.com/MarcinJuszkiewicz/DeveloperApplication-PPU
[21:27] <persia> hrw, Yes, you :)
[21:27] <hrw> persia: PPU finally
[21:28] <persia> [TOPIC] PerPackageUploader Application for Marcin Juszkiewicz
[21:28] <MootBot> New Topic:  PerPackageUploader Application for Marcin Juszkiewicz
[21:28] <persia> Apologies: it's just after sunrise here.
[21:28] <hrw> no problem
[21:28] <hrw> I got universe contributor last time
[21:28] <hrw> I maintain cross toolchain for armel and armhf architectures
[21:29] <bdrung_> hi hrw
[21:29] <hrw> armel is present in Debian and Ubuntu, armhf is on a way to Debian and also may be added into Ubuntu. At Linaro we want armhf to e present in both distributions
[21:29] <persia> I've seen a few complaints about our documentation in the past few days.  Anyone up for trying to dredge through it and submit a new draft?
[21:30] <geser> what "flavour" of ARM is armhf?
[21:30] <persia> OK.  I'll table that for later.
[21:30] <hrw> geser: armv7, hardfloat
[21:31] <hrw> geser: no neon by default due to tegra2
[21:31] <ScottK> How runtime Neon detection working for Qt currently?
[21:32] <hrw> ScottK: have to admit that I lost track on this - spent most time in toolchain
[21:32] <ScottK> OK.
[21:33] <bdrung_> hrw: the packages you request upload rights for doesn't seem to exist
[21:34] <hrw> bdrung_: armhf ones are same as armel ones - did not get yet uploaded
[21:34] <hrw> bdrung_: the only difference is s/armel/armhf/ in changelog and regenerataion of control file
[21:34]  * persia recommended this list to hrw in OOB discussions, as the other packages were expected to be uploaded fairly soon, and our board isn't so fast.
[21:34] <bdrung_> hrw: i fail to find the armel ones, e.g. https://launchpad.net/ubuntu/+source/gcc-4.6-armel-cross
[21:35] <hrw> bdrung_: 4.6 was not in natty - I have version working with sid and oneiric
[21:35] <hrw> bdrung_: let me give git url
[21:36] <geser> hrw: are the *-armel-* and *-armhf-* different source packages?
[21:36]  * ScottK would like to recommend hrw for his photography skills as he took the Kubuntu group photo at UDS. ;-)
[21:36] <hrw> http://git.linaro.org/gitweb?p=people/hrw/cross-toolchain-packaging.git;a=summary is linaro tree
[21:36] <MootBot> LINK received:  http://git.linaro.org/gitweb?p=people/hrw/cross-toolchain-packaging.git;a=summary is linaro tree
[21:36] <hrw> geser: yes, they are separate but share 100%
[21:37] <geser> hrw: isn't it possible to build both from the same source package or is there any reason for the duplication?
[21:37] <hrw> geser: I am in a middle of creating one source for armel/armhf of each component and merging gcc-4.[456]-*-cros into one source or source package
[21:37] <hrw> geser: during uds-n we decided to have cross toolchain source per arch
[21:38] <hrw> geser: as Debian ones would do 11 arch builds and what if 9th fail after 30h of building?
[21:38] <maco> ouch
[21:38] <bdrung_> build time is a strong argument for separate packages
[21:39] <hrw> in Ubuntu we handle 1 arch now (m,n) and now will have 2 (oneiric)
[21:39] <hrw> Debian can have more of them.
[21:39] <geser> hrw: Debian has 11 arm flavours?
[21:39] <bdrung_> hrw: you are talking a lot about debian. will you try to upload the packages into debian first?
[21:40] <hrw> geser: no, but emdebian team wants to replace their semi-auto built packages with mine
[21:40] <hrw> bdrung_: once will get all patches landed in Debian yes
[21:40] <hrw> bdrung_: merging all required changes into ubuntu took me half of maverick cycle
[21:41] <hrw> bdrung_: my source packages works no changes under debian and ubuntu
[21:41] <hrw> I have check on 'lsb_release -d' to take care of details
[21:42] <hrw> also handle linaro toolchain backport ppa with same sources but thats a bit other story
[21:42] <bdrung_> hrw: do you know dpkg-vendor?
[21:42] <hrw> bdrung_: no, but will check it
[21:42] <hrw> bdrung_: trick with lsb_release I took from gcc packaging
[21:43] <hrw> during maverick I did cleanup of gcc/binutils packaging which ended in few thousand of lines dropped
[21:43] <bdrung_> it's the preferred way to check the vendor (instead of lsb_release). advantage: no additional build dependency
[21:44] <hrw> bdrung_: ok, gcc packaging has to work under dapper so maybe thats why
[21:44] <bdrung_> hrw: yes, dpkg-vendor isn't that old
[21:45]  * micahg thought dpkg-dev was needed for dpkg-vendor
[21:45] <hrw> yep. 2009 according to manpage
[21:45] <hrw> micahg: I already bdepend on dpkg-dev
[21:45] <hrw> micahg: and you are right - dpkg-vendor is dpkg-dev
[21:46] <bdrung_> micahg: build-essential depends on dpkg-dev
[21:46] <bdrung_> so you get it for free (on compile time)
[21:47] <tumbleweed> a versioned dependancy on it may be needed
[21:47] <hrw>  dpkg-dev (>= 1.15.3.1) is what I need already
[21:47] <hrw> due to components needs (binutils, linux, gcc, eglibc)
[21:47] <persia> So, while it's interesting to discuss ways of aligning packages between distributions, are there more questions to prepare to vote on hrw's application?
[21:48] <hrw> ;)
[21:48] <micahg> bdrung_: ah, that's what it was, a higher versioned build-dep was necessary :()
[21:48] <hrw> dpkg-vendor is 1.15.1
[21:49] <hrw> and I already need 1.15.3.1 so yes - good thing to switch to
[21:49]  * bdrung_ is ready to vote
[21:49]  * geser too
[21:50]  * stgraber too
[21:50] <persia> [VOTE] Approve Marcin Juszkiewicz for PPU upload of armel-cross-toolchain-base gcc-4.4-armel-cross gcc-4.5-armel-cross gcc-defaults-armel-cross and recommend addition of armhf and 4.6 packages as they become available
[21:50] <MootBot> Please vote on:  Approve Marcin Juszkiewicz for PPU upload of armel-cross-toolchain-base gcc-4.4-armel-cross gcc-4.5-armel-cross gcc-defaults-armel-cross and recommend addition of armhf and 4.6 packages as they become available.
[21:50] <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
[21:50] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[21:51] <maco> +1
[21:51] <MootBot> +1 received from maco. 1 for, 0 against. 0 have abstained. Count is now 1
[21:51] <geser> +1
[21:51] <MootBot> +1 received from geser. 2 for, 0 against. 0 have abstained. Count is now 2
[21:51] <stgraber> +1
[21:51] <MootBot> +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3
[21:51] <bdrung_> +1
[21:51] <MootBot> +1 received from bdrung_. 4 for, 0 against. 0 have abstained. Count is now 4
[21:51] <persia> +1 : hrw is definitely the driving force behind these packages, and fixes many other things in his quest to make them better
[21:51] <MootBot> +1 received from persia. 5 for, 0 against. 0 have abstained. Count is now 5
[21:51] <persia> [ENDVOTE]
[21:51] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[21:51] <persia> hrw Congratulations
[21:51] <hrw> thanks guys
[21:51]  * persia is out of time
[21:51] <persia> Oh.
[21:51] <hrw> now I will give you a bit of time free from me and in some time will apply for motu
[21:52] <persia> [TOPIC] Chair for next meeting
[21:52] <MootBot> New Topic:  Chair for next meeting
[21:52]  * persia claims repeats should be avoided
[21:52] <hrw> to not interrupt ubuntu/arm (and others) with debdiffs fixing armel ftfbs'
[21:53] <bdrung_> i don't know if i can attend the next meeting. therefore i am not a good candidate for the chair.
[21:53] <stgraber> I can do it
[21:53] <persia> [AGREED} stgraber will chair the next meeting
[21:53] <MootBot> AGREED received: [AGREED} stgraber will chair the next meeting
[21:53] <hrw> have a nice rest of day - 22:53 here and I promised my daughter to read a book before sleep
[21:53] <persia> #nedmeeting
[21:54] <persia> #endmeeting
[21:54] <MootBot> Meeting finished at 15:54.
[21:54] <persia> Thanks everyone for staying the extra hour.