[08:42]  * persia peers about
[08:43] <persia> so, it's late, and we're disorganised.
[08:43] <persia> Are ember or imbrandon here?
[08:45] <geser> ember seems to not be online
[08:45] <persia> That's what I see too.
[08:45] <geser> imbrandon is online but let's if he's afk or not
[08:45] <persia> Well, if imbrandon stops by, we can hunt for the rest of MC.
[08:45] <geser> have we quorum anyways?
[08:45] <persia> Dunno.  Let's check :)
[08:46] <persia> jpds, nhandler nixternal dholbach soren ?
[08:47] <persia> Maybe not :(
[08:59] <vikashkoushik> Hi guys
[08:59] <vikashkoushik> I did do a Demo on Ubuntu in my school.
[08:59] <vikashkoushik> Will that be considered as a Contribution to Ubuntu while getting the email id?
[09:00] <persia> vikashkoushik, A practice of regularly presenting Ubuntu can be considered a contribution to advocacy.
[09:00] <persia> You'd want to combine it with other activities as part of your participation within Ubuntu.
[09:01] <vikashkoushik> I am also giving solutions to people's problem in Launch Pad Answer Tracker & I just started Transilating Ubuntu in Tamil
[09:01] <vikashkoushik> Is that enough?
[09:03] <persia> I can't give an authoritative answer to that.
[09:03] <persia> Your best guideline is really https://wiki.ubuntu.com/Membership
[09:04] <vikashkoushik> I've already gone through that and I am already an Ubuntero
[09:04] <persia> But the key things are that the contribution be recognised as significant to others in the community, and that it be sustained over a reasonable period of time (with an expectation of continuance)
[09:05] <vikashkoushik> I've been contributing to Launch Pad Answer Tracker for only 2 weeks as I just came to know about it But I gave the Demo on Jan
[09:05] <vikashkoushik> & during Feb I was burning CD's and distributing it
[09:06] <vikashkoushik> & I am still continuing to do so
[09:07] <vikashkoushik> Is this enough?
[09:07] <persia> Cool.  I'd recommend contacting your local Ubuntu group, and working with them, as part of building interaction with the community.
[09:08] <vikashkoushik> How do I contact the Local Ubuntu group? I live in Chennai,Tamil Nadu,India.
[09:09] <persia> #ubuntu-in is probably a good place to start.
[09:10] <vikashkoushik> thanks
[09:17] <jpds> persia: I'm here now.
[09:20] <persia> jpds, Well, imbrandon never showed, and we'd still not have quorum.
[09:50] <vikashkoushik> Shall Post on my wiki page about the demo I did in Jan?
[09:52] <persia> vikashkoushik, You will want to document everything on your wiki page before you apply.
[09:53] <vikashkoushik> Persia,Do you think the period I have been contributing is enough?
[09:53] <persia> vikashkoushik, The guideline is at least two months, but demonstration of activity that is considered sustained by your peers.  I haven't worked with you, so I don't have an opinion.
[09:54] <vikashkoushik> I didn't get you.
[09:58] <vikashkoushik> persia, i didn't get you clearly.
[09:59] <persia> Understood, which is why I /queried you, to preserve the clenliness of these logs.
[14:01]  * lool pokes slangasek 
[14:01] <lool> The release meeting shows up now on my google calendar agenda, was it moved?
[14:01] <lool> Crap, 14 UTC
[14:03] <davidbarth> lool: really? yes, i think it moved; i had it at 3pm CET initially
[14:04] <persia> My memory is that it used to be at 15 UTC.  I think it moved to follow BST.
[14:05] <lool> persia: It was supposed to happen in one hour, but I raised that it was conflicting with some call
[14:05] <lool> slangasek looked at moving it one hour earlier, but announced it for next hour
[14:06] <lool> So either it changed at the last minute again, or there was confusion
[14:06] <lool> I just updated the google cal entry though
[14:06] <dendrobates> this did seem unusually early for slangasek.
[14:06] <lool> dendrobates, mdz: apparently meeting is next hour
[14:06] <lool> Which might conflict with your call
[14:14] <mdz> lool: I had already asked randa to reschedule that call, but it looks like she forgot to do it before she left for the weekend
[14:14] <mdz> dendrobates: ^^
[14:15] <dendrobates> mdz: are you working today?  Or are you just showing up to the release meeting?
[14:16] <mdz> dendrobates: neither
[14:16] <mdz> I just happened to be on IRC, which I'm quickly realizing is a mistake if I expect to benefit from the bank holiday
[14:17] <lool> mdz: Eh quite certainly :)  enjoy your long WE
[14:58]  * slangasek waves
[14:58]  * nhandler waves back to slangasek 
[14:58]  * rickspencer3 waves
[14:59]  * rickspencer3 yawns
[15:00] <fader_> Hello
[15:00] <lool> Morning slangasek
[15:00] <nhandler> So it is time for the release team meeting, correct?
[15:00] <slangasek> nhandler: yes
[15:00] <lool> Yup
[15:01] <robbiew> hi
[15:01] <slangasek> 'lo
[15:01]  * pgraner o/
[15:02] <lool> slangasek: I'm afraid I milestoned a couple of bugs in the last hours; Bug 359049, Bug 358961
[15:02]  * tedg has coffee, therefore is ready to go!
[15:02] <lool> pgraner: May I ask immediately whether a last kernel upload is planned? :)
[15:02] <slangasek> sbeattie, Hobbsee, ScottK: ping?
[15:02] <slangasek> lool: wait till we start the meeting? :)
[15:02] <pgraner> lool: we are done
[15:02] <nhandler> slangasek: ScottK said he wouldn't be able to make the meeting
[15:03] <lool> slangasek: I was abusing this early minutes where everybody joins  ;)
[15:03] <lool> pgraner: Ok; that does influence things then, thanks
[15:03]  * sbeattie waves hello
[15:03] <rickspencer3> pgraner: sweet
[15:03] <rickspencer3> congrats kernel team!
[15:04] <lool> Yep, nice!
[15:04] <pgraner> rickspencer3: don't party just yet
[15:04] <slangasek> #startmeeting
[15:04] <MootBot> Meeting started at 09:04. The chair is slangasek.
[15:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:04] <lool> Albeit there are bugs :)
[15:04]  * rickspencer3 recorks champagne bottle
[15:04] <slangasek> I'm assuming anyone located in the UK or Germany is taking their well-deserved holiday, so let's get started :)
[15:05] <slangasek> [TOPIC] Outstanding actions
[15:05] <MootBot> New Topic:  Outstanding actions
[15:05] <ogra> there is no holiday in the US ?
[15:05] <nhandler> There is ogra
[15:05] <nhandler> It is Good Friday
[15:05] <tedg> ogra: Not a national bank holiday though.
[15:06] <ogra> ah
[15:06] <slangasek> pgraner: was the power cable issue for 340014 taken care of?  I have no idea if that's even still an issue, and it obviously wasn't recorded in the bug :)
[15:06] <fader_> slangasek: I got the machine in question back to manjo who had the power cord
[15:06] <fader_> He was running tests on it and I asked him to file any bugs he came across
[15:07] <slangasek> ok, so the power cord is no longer an issue, at least
[15:07] <fader_> Right
[15:07] <slangasek> fader_: how about sound input bugs on netbooks?  Everything filed that should be?
[15:07] <fader_> slangasek: Yes, all the bugs that cr3 and I encountered are filed and seem to have been assigned appropriately
[15:08] <fader_> I also updated the bug numbers in http://people.ubuntu.com/~fader/hw-testing/netbooks/
[15:08] <fader_> (Modulo the ones that manjo is filing; I need to get those numbers from him)
[15:08] <slangasek> ok; they don't appear to have shown up on the release team radar as targeted bugs, were they meant to?
[15:09] <fader_> I'm honestly not sure.  I know mdz looked at them and commented, but I don't know if anything further needs to happen to them
[15:09] <slangasek> fader_: could you email me a list of those bugs after, so I can have a look at what we've got?
[15:10] <fader_> slangasek: Absolutely... I'll email them to you
[15:10] <slangasek> [ACTION] fader_ to email slangasek the list of netbook sound input bugs
[15:10] <MootBot> ACTION received:  fader_ to email slangasek the list of netbook sound input bugs
[15:10] <slangasek> sbeattie: how are we with regression-release bug triaging?
[15:10] <sbeattie> slangasek: I sent off an email to the qa team about regression-release tagged bugs, but I think everyone's too busy dealing with newer bugs to go back to those at the moment.
[15:10] <slangasek> ok :(
[15:11] <slangasek> (action: have fewer bugs next week)
[15:11] <slangasek> [TOPIC] QA team
[15:11] <MootBot> New Topic:  QA team
[15:11] <slangasek> moving on, then
[15:12] <fader_> Hardware testing has nothing exciting to report... we are having checkbox issues that are preventing some machines from reporting results correctly, so I am in the process of backfilling by running checkbox manually
[15:12] <fader_> We've also hit bug 356518 on a couple of machines which prevents them from booting with grub when the serial console is being used, but they work fine without that option
[15:13] <fader_> So I'm not sure it's quite as high priority as it seemed when I first ran into it
[15:13] <fader_> Other than that everything is passing and we're not seeing any real issues
[15:14] <slangasek> I think we should still be tracking that bug, even if we may not be able to get it fixed (as opposed to release-noted)
[15:14] <fader_> slangasek: Yeah, it's definitely an annoying bug, but the fact that it only appears to happen on a small number of systems and under very specific conditions makes me feel less worried about it :)
[15:15]  * slangasek nods
[15:15] <slangasek> ok, cool; thanks for the update
[15:15] <slangasek> sbeattie: anything to add from your corner?
[15:16] <sbeattie> not particularly, I haven't seen anything significant come through in the regresisons department.
[15:16] <slangasek> great!
[15:17] <slangasek> [TOPIC] Desktop team
[15:17] <MootBot> New Topic:  Desktop team
[15:17] <rickspencer3> looks like we have quite a few bugs on release team radar
[15:17] <rickspencer3> generally, I divide them between "xorg" and "other"
[15:17] <slangasek> two or three :)
[15:18] <rickspencer3> https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:18] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:18] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:18] <rickspencer3> in the "other" category, none are very concerning to me, except bug #277589
[15:18] <rickspencer3> but that's only because it's new to me, and I haven't had a chance to follow up and see what's going on with it
[15:19] <slangasek> rickspencer3: your list has one more bug than mine, do you know which bug that is?
[15:19] <rickspencer3> slangasek: no
[15:19] <rickspencer3> it's probably a dupe
[15:19] <rickspencer3> I was copying and pasting between lists early this morning :)
[15:19] <slangasek> 349992
[15:19] <slangasek> which isn't targeted; does it need to be?
[15:20] <rickspencer3> no
[15:20] <rickspencer3> that is left over
[15:20] <slangasek> ah, it's been untargeted by bryce, ok
[15:20] <rickspencer3> sorry
[15:20] <rickspencer3> yeah
[15:20] <rickspencer3> in terms of xorg it's only intel that has any real issues right now
[15:20] <rickspencer3> the intel engineers have been helping bryce quite a bit
[15:21] <rickspencer3> as I noted on the release page, bryce suspects that there are one or two underling causes for all the "freeze" bugs, so he's sorting through the data today
[15:21]  * slangasek nods
[15:21] <slangasek> I look forward to the good news next week :)
[15:21] <rickspencer3> I suspect we are in good enough shape to ship, as all of the bugs ...
[15:22] <rickspencer3> can be worked around by turning off desktop effects
[15:22] <rickspencer3> but that's painful, so I'm looking forward to good news too :)
[15:23] <rickspencer3> bug #341898 also seems to be xorg, but I'm not clear if it's still an issue or not
[15:23] <rickspencer3> I should be able to find out next week after everyone is back from holidays
[15:23] <rickspencer3> (that's it from desktop team, unless there are questions)
[15:23] <slangasek> superm1 (mythtv) isn't on holidays
[15:23] <rickspencer3> okay
[15:23] <slangasek> so if the bug needs followed up on you could tag him
[15:23] <rickspencer3> I'll ping him after this
[15:23] <davidbarth> slangasek, rickspencer3: while we're on the desktop, can I also mention the bugs on our radar (https://wiki.canonical.com/DesktopExperienceTeam/JauntyReleaseStatus)
[15:24] <slangasek> (well, I'm presuming a bit; he's in the US, he might still be on holiday)
[15:24] <rickspencer3> slangasek: ack
[15:25] <rickspencer3> davidbarth: thanks for bringing up bug #358775
[15:25] <rickspencer3> I think it's an easy fix (non-intrusive) but it is really late for the design team to start checking whether everything is to spec
[15:26] <slangasek> davidbarth: sure - the only one of those that isn't targeted currently is 331369, I guess we should target that if you're looking for an exception
[15:26] <slangasek> (done)
[15:26] <davidbarth> rickspencer3: tedg may be able to comment better for #358775
[15:26] <rickspencer3> slangasek: if we do 358775 I suppose we'll need an exception as well
[15:26] <rickspencer3> also, it will impact screen shots, documentation, etc...
[15:26] <davidbarth> slangasek: yes, will do; it's a one liner, but a regression potential
[15:27] <davidbarth> rickspencer3: correct
[15:27] <slangasek> 358775> I thought I already pushed through an update for that, or was I just reading patches?
[15:27] <davidbarth> rickspencer3: also #317271 and #357455 are dups apparently, and not a trivial change
[15:27] <slangasek> ah, yes, was just reading my bug mail :)
[15:28] <davidbarth> rickspencer3: we are still evaluating whether the change is worth the potential impact
[15:28] <rickspencer3> davidbarth: which change, you mean mt's move the icon bug?
[15:28] <rickspencer3> 358775 ?
[15:29] <davidbarth> rickspencer3: no, the "logout..." that exist immediately if you have another session opened with the same account
[15:29] <rickspencer3> right
[15:29] <davidbarth> rickspencer3: it's an odd case
[15:29] <rickspencer3> davidbarth: shall we discuss outside the meeting?
[15:29] <davidbarth> rickspencer3: sure
[15:30] <slangasek> rickspencer3: btw, in response to the freeze mail's request to "let the release team know" about any bugs that should be on the radar but aren't, I got an email from a user that's led me to be concerned about the state of plasma-widget-network-manager
[15:30] <slangasek> [LINK] https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager
[15:30] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager
[15:30] <slangasek> seems there's lots of breakage where wireless passwords are concerned; could you have Riddell follow up on this when he's back from holiday?
[15:30] <rickspencer3> hmmm
[15:30] <rickspencer3> yes
[15:31] <slangasek> (p-w-n-m is the default NM frontend for kubuntu 9.04)
[15:31] <rickspencer3> I'll see what's going on in #kubuntu-devel today
[15:31] <slangasek> ok
[15:31] <slangasek> thanks
[15:31] <rickspencer3> see if the team is dialed in
[15:31] <nhandler> Not much activity Riddell
[15:31] <slangasek> [ACTION] rickspencer3 to follow up with Kubuntu team regarding state of plasma-widget-network-manager and encrypted wireless
[15:31] <MootBot> ACTION received:  rickspencer3 to follow up with Kubuntu team regarding state of plasma-widget-network-manager and encrypted wireless
[15:32] <slangasek> [TOPIC] Mobile team
[15:32] <MootBot> New Topic:  Mobile team
[15:32] <slangasek> lool: hi
[15:32] <lool> list of specs and bugs on our radar:
[15:32] <lool> [link] <https://wiki.ubuntu.com/MobileTeam/Roadmap>
[15:32] <MootBot> LINK received:  <https://wiki.ubuntu.com/MobileTeam/Roadmap>
[15:32] <lool> current high-level status per topic:
[15:32] <lool> - UNR: I saw no notify-osd complaints; good shape except for intel graphics regression on eeepcs (349314, 344443) and pending-upload netbook-launcher gtk label translation issue 356970
[15:32] <lool> - MID image is as good as usual
[15:32] <lool> - armel netbook images: still need plenty of testing since the latest kernel changes (all of iop32x, versatile, ixp4xx have been changed for various bugs); still need a d-i build (in unapproved again currently)
[15:33] <lool> - armel's "iMX51 Babbage": dailies are building, would have liked fixing 359049, but probably doesn't warrant a kernel upload, everything seems to work at this point; some unfortunate issues preventing correct use of USB and wifi; 356517 breaks NM on wired, asac is uploading a fix soon; need some kind of release notes for this flavour
[15:33] <lool> - VFP: pango uploaded, gtk+ ready but being QA-ed (builds were slow yesterday), ffmpeg-debian patch ready, needs review, testing and upload; missing cairo still
[15:33] <lool> - wont make the release: poulsbo, touchscreen
[15:33] <lool> - lpia: overall good shape, d-i images were fixed recently
[15:33] <lool> - armel: overall good shape; update-initramfs/flash-kernel 358762 needs fixing before release though, but has a proposed fix (needs testing and upload)
[15:33] <lool> - important bugs I'd like to cover:
[15:33] <lool>   349314: slowness on intel graphics on eeepcs; Paul Larson says it wasn't this patch causing regressions, Andy says it was, Matt asks for a bug for the regressions
[15:33] <lool>   358762: want advice / ack on proposed changes
[15:33] <lool>   359049: don't think this warrants a kernel upload, but am taking opinions
[15:33] <lool> (done pasting)
[15:34] <lool> Ah there's something I forgot to write down: I've asked for more armel buildds yesterday as we had a growing backlog of needs build packages on armel
[15:34] <slangasek> I'll process the d-i asap
[15:34] <lool> and only 3 builders with 2 being busy on openoffice and openjdk
[15:34] <lool> AFAIK, one more openjdk upload is still needed
[15:35] <ogra> wasnt that just done some mins ago ?
[15:35] <lool> infinity has set up our livefs builder as buildd temporarily and this helped a lot
[15:35] <lool> ogra: No, yesterday evening
[15:35] <lool> ogra: Oh openjdk?
[15:35] <ogra> openjdk-6 (6b14-1.4.1-0ubuntu6) jaunty; urgency=low
[15:35] <ogra>   * Fix native2ascii jdk test case, which let the jdk testsuite fail.
[15:35] <ogra> 20min ago
[15:35] <slangasek> I just approved an openjdk fix, yes
[15:35] <lool> Not sure whether that's the final one
[15:35]  * ogra hopes so
[15:36] <lool> Anyway, we can discuss this later
[15:36] <ogra> with the archive rebuild and the slow buioldds i really fear we wont have built everything by release on armel
[15:36] <slangasek> 359049> yes, milestoning for -updates
[15:36] <slangasek> hmm - or should that be declined altogether, I guess
[15:36] <lool> Updates sound bad
[15:37] <lool> As we don't distinguish between jaunty and jaunty-updates in cdimage/debian-cd
[15:37] <lool> I'd rather have the same udeb name for both
[15:37] <lool> It's either now, or karmic
[15:37] <sbeattie> lool: do we need an ubuntu-mid alternate iso target on the iso tracker? would that have caught the issues with that image an the mini 9 that made it through the beta?
[15:37] <lool> Since the debian-cd/cdimage stuff is versionned per dist, I don't strongly care that we have a hack in an old branch of debian-cd
[15:38] <lool> sbeattie: We're not really committed to supporting that officially, but we could have one if it helps getting more testing / better testing
[15:38] <lool> But when there are issues, we're fixing them as part of lpia QA
[15:39] <slangasek> 358762> can you set that bug back to new and subscribe ubuntu-release, then?
[15:39] <lool> sure
[15:39] <ogra> we could just upload it :)
[15:39] <ogra> and close it .. the fix is three lines
[15:39] <lool> done
[15:40] <slangasek> well, he wanted an ack
[15:40] <lool> ogra: I want a second opinion
[15:40] <slangasek> that's how you get one of those :)
[15:40] <ogra> heh
[15:40] <ogra> k
[15:40] <slangasek> I think I've digested everything above; did I miss anything you needed comments on?
[15:41] <lool> I'd like to know decisions on the other two
[15:41] <lool> 349314: 359049:
[15:41] <lool> 359049: I take it that we agree no kernel uploads anymore, so we'll stick to current hardcoding?
[15:41] <slangasek> yes
[15:41] <lool> 349314: will that be fixed in SRU?
[15:41] <lool> pgraner: ^
[15:41] <slangasek> 349314> what decision do you need?  sounds like the bug isn't fully triaged yet
[15:42] <lool> I hoped we'd have more recent info, or a plan
[15:42] <lool> It's the worst bug hitting UNR / EeePCs users
[15:43] <slangasek> that looks appropriate for an SRU, IMHO
[15:43] <pgraner> lool: we are working with upstream, and will be SRU
[15:43] <lool> Shall we provide a ppa kernel for eeepc users?  release note it?
[15:43] <pgraner> lool: prob could do with a release note
[15:43] <slangasek> yes
[15:43] <slangasek> [ACTION] slangasek to add release-note task for bug #349314
[15:43] <MootBot> ACTION received:  slangasek to add release-note task for bug #349314
[15:43] <lool> Ok; thanks for discussion
[15:43] <lool> done for mobile, unless there are any questions?
[15:44] <slangasek> none for me
[15:44] <slangasek> thanks
[15:44] <slangasek> [TOPIC] Kernel team
[15:44] <MootBot> New Topic:  Kernel team
[15:44] <pgraner> slangasek: here goes the cut n paste
[15:44] <pgraner>    * Bug:348275: iwlagn: NM applet doesn't connect to WPA2
[15:44] <pgraner>     - Different cards, different systems, possibly a supplicant issue. Given the symptoms no critical.
[15:44] <pgraner>    * Bug:336055: wrong ESSIDs shown after resume
[15:44] <pgraner>     - Have a fix (abi bumper) we can add if we have to spin another kernel.
[15:44] <pgraner>    * Bug:350491: hibernation should not be allowed when running kernel is gone from disk
[15:44] <pgraner>     - Will have to check with apw on the status.
[15:44] <pgraner>    * Bug:356975: imx51 oops after watchdog call
[15:44] <pgraner>     - No fix, we will keep working, if we spin a new kernel we might be able to include.
[15:44] <pgraner>    * Bug:331589: system beep in jaunty is the most annoying sound known to man
[15:44] <pgraner>     - Fix Committed
[15:44] <pgraner>    * Bug:340014: suspend/resume fails on Samsung NC10
[15:44] <pgraner>     - Looking to be a BIOS or Hardware issue. Shipping hardware to cking to see if he can determine root cause. Possible SRU post-release.
[15:45] <pgraner>    * Bug:358574: [drm:i915_gem_idle] *ERROR* hardware wedged
[15:45] <pgraner>     - Intel freeze issues. rickspencer3 covered in his status.
[15:46] <lool> 356975> You have something to include?
[15:46] <lool> pgraner: In general, do you have any not included iMX51 patches around the corner?
[15:46] <pgraner> lool: are you asking if we are holding back patches?
[15:47] <lool> No, I had in mind that you might have received a bunch to review, and might not have time to consider them or perhaps they aren't suitable for pre-release merging
[15:47] <lool> (I wasn't included in the kernel drops, and it's been a while since the previous one, so I'm hoping that FSL sent fixes for the most annoying bugs)
[15:47] <pgraner> lool: no patches that I'm aware of, can you be more specific?
[15:48] <pgraner> lool: I haven't seen patchs from FSL in weeks
[15:48] <lool> pgraner: I wish for USB fixes and perhaps getting the wifi in shape, but I don't know how much hardware versus software these issues are; FSL is aware though
[15:48] <ogra> the prob with 356975 is that it is only reproducable in use with NM
[15:48] <ogra> which in turn waits for 356517 first
[15:48] <slangasek> if there's any chance the right place to fix 350491 is outside the kernel package itself, we should probably consider that, so we have a chance to fix that before release
[15:48] <lool> pgraner: Ok; too bad then, I hope we'll see patches in the future and they will be SRU-able
[15:48] <lool> pgraner: thanks for the update!
[15:49] <pgraner> lool: np
[15:49] <slangasek> pgraner: is there a test kernel with the fix for 336055 that I could test here, to confirm that it fixes it?
[15:49] <slangasek> 358574> I didn't see this covered in rickspencer3's status report
[15:49] <pgraner> slangasek: I can get rtg to build you one
[15:50] <slangasek> I'd appreciate it
[15:50] <pgraner> slangasek: that is the Intel freeze issues we have 3 or four different freeze bugs that upstream think are all related
[15:50] <slangasek> ok
[15:50] <pgraner> Thats all from kernel team...
[15:51] <rickspencer3> slangasek: ack what pgraner said regarding 358574
[15:51] <rickspencer3> it's part of the whole "freeze" issue
[15:51]  * slangasek nods
[15:51] <pgraner> slangasek: if we don't get fixes we prob should do a release note
[15:51] <slangasek> agreed
[15:52] <slangasek> it's on the radar for now, we can sort that when we're a little closer to release and know more
[15:52] <rickspencer3> I think there is a lot going on upstream as well, so an SRU may become possible if we want to go that route
[15:52] <slangasek> we'll probably need to
[15:52] <slangasek> [TOPIC] Foundations team
[15:52] <MootBot> New Topic:  Foundations team
[15:52] <slangasek> robbiew: hi
[15:52] <robbiew> hi
[15:53] <robbiew>  * Bug:339898: migration assistant offered on full-disk installs - Assigned to evand for investigation.
[15:53] <robbiew> this was opened yesterday (I think)...and doubt evand had a chance to look at it before leaving
[15:53] <robbiew> on holiday
[15:54] <slangasek> it was opened weeks ago, actually
[15:54] <slangasek> turned up in beta QA testing
[15:54] <robbiew> ah
[15:54] <robbiew> whoops
[15:55] <robbiew> 03-09
[15:55] <robbiew> not 04-09
[15:55] <robbiew> heh
[15:55] <robbiew> in any case...seems to have sat
[15:55] <robbiew> so I assigned to evand and will talk to him next week
[15:55]  * slangasek nods
[15:55] <robbiew> Bug:309411: bouncycastle MIR - Is this waiting on response regarding enabling testsuite? noticed it was marked Incomplete by kees.
[15:56] <slangasek> yeah, that should be assigned to me, really
[15:56] <robbiew> heh
[15:56] <slangasek> (I'm partway through getting the testsuite enabled; so that bug'll be closed soon)
[15:57] <robbiew> :)
[15:57] <robbiew> ok
[15:57] <robbiew> Bug 350016: aclocal python.m4 broken - The fix by doko works around the issue with "site-packages" vs "dist-packages", but introduces another with the path associated with --prefix now always ignored, i.e. /usr/local is always used.  We will need to figure out a better workaround, if possible.
[15:57] <lool> Ack, these causes a bunch of FTBFS again
[15:58] <robbiew> not sure what to do on this one, as doko is having to workaround an issue we didn't create
[15:58] <slangasek> I think the workaround needs to be dropped; I believe doko said on #ubuntu-release that he was going to revert that today, though I haven't seen it yet
[15:59] <robbiew> agree
[15:59] <robbiew> ok
[15:59] <robbiew> doko: around?
[15:59] <robbiew> I'll post a comment in the bug to recommend the dropping of the "fix"
[15:59]  * slangasek nods
[16:00] <robbiew> Bug 354793: apt cronjob fails in some timezones - jdstrand posted a proposed fix to apt.cron.daily, and looks to be waiting on the submitter to validate it.
[16:00] <jdstrand> actually, mvo committed it
[16:01] <robbiew> ah
[16:01] <lool> It's bank holiday in germany, he's probably not around
[16:01] <robbiew> sweet
[16:01] <jdstrand> (not to jaunty yet)
[16:01] <robbiew> ok
[16:01] <slangasek> so is mvo the assignee for jaunty?
[16:01] <jdstrand> we spoke verbally that he is, yes
[16:01] <slangasek> marked
[16:01] <jdstrand> I don't recall what the bug says
[16:01] <robbiew> nothing...from mvo heh
[16:02] <jdstrand> there is another bug that will go with that one that we are also working on
[16:02] <robbiew> ack
[16:03] <robbiew> Bug 357884: "pycentral rtinstall" does not add python2.6 symlinks - last comment indicates that the solution is being discussed between cjwatson and mvo.
[16:03]  * slangasek nods
[16:04] <robbiew> Bug 316756: login.defs conffile prompt on upgrade - appears that james_w has released a fix for this one
[16:04] <ogra> wow, that one is returning every second release
[16:04] <slangasek> should stop returning if we kill off system-tools-backends :P
[16:04] <slangasek> in the meantime, fix applied
[16:04]  * ogra remembers he had hunted the same one down in breezy
[16:05] <slangasek> robbiew: anything else we should be tracking?
[16:05] <robbiew> not that I know of
[16:06] <slangasek> ok
[16:06] <slangasek> thanks
[16:06] <slangasek> [TOPIC] Server team
[16:06] <MootBot> New Topic:  Server team
[16:06] <slangasek> dendrobates: hi
[16:06] <dendrobates> hi
[16:07] <dendrobates> bug 350089
[16:07] <robbiew> I ran into this one on upgrade...have /home on a separate partition
[16:08] <slangasek> on upgrade, or on a reinstall preserving /home?
[16:08] <dendrobates> robbiew: I don't think kirkland has been able to reproduce it.
[16:08] <robbiew> reinstalled
[16:09] <robbiew> but preserved /home
[16:09] <slangasek> well, it's not clear why ecryptfs-utils is being removed here
[16:09] <slangasek> and that seems to be the bug we're tracking
[16:09] <robbiew> well...maybe I had a different issue
[16:09] <slangasek> with the removal failure being a bit of UI unpleasantness, which is nevertheless deliberate?
[16:10] <dendrobates> slangasek:  yes, kirkland believes it is a bug in the update-manager logic, per his last comment.
[16:10] <slangasek> ok
[16:10] <robbiew> great :/
[16:10] <dendrobates> slangasek: I have not gotten an update from hom this morning, though.
[16:10] <slangasek> alright, we'll pursue that one afterwards then
[16:10] <slangasek> dendrobates: any other bugs that we should be tracking for server?
[16:11] <dendrobates> apart from that, we have a vmbuilder regression.
[16:12] <slangasek> bug #?
[16:12] <dendrobates> getting.
[16:12] <sbeattie> bug 342359?
[16:12] <dendrobates> bug  342359
[16:12] <dendrobates> yep
[16:13] <dendrobates> jdstrand: has a work around ready to upload.
[16:13] <slangasek> ok; will watch for that in the queue today
[16:13] <dendrobates> he is waiting for an approval from soren that has not come.
[16:13] <dendrobates> ok.
[16:14] <slangasek> anything else?
[16:14] <dendrobates> nope, I think that is all.
[16:14] <slangasek> ok, thanks
[16:14] <slangasek> [TOPIC] MOTU
[16:14] <MootBot> New Topic:  MOTU
[16:14] <slangasek> nhandler: were you covering for ScottK today?
[16:15] <nhandler> Yes slangasek
[16:15] <nhandler> The only issue that he wanted to bring up was the Python 2.6 transition
[16:15] <nhandler> There are still several transition bugs (some with patches) that need to be approved and then sponsored
[16:16] <nhandler> However, the list has been decreasing at a nice rate
[16:16] <slangasek> the two targeted bugs I have for python 2.6 are 353688 and 354415; is there a longer list somewhere?
[16:17] <nhandler> slangasek: I have not seen one. I only know about the bugs where motu-release or ubuntu-universe-sponsors are subscribed.
[16:17] <nhandler> Those are the only ones I have "lists" for
[16:17] <nhandler> I could try and put together a list of bugs if that is desired
[16:18] <slangasek> if they're all in process, no need
[16:19] <slangasek> was mainly wondering if there were bugs I could help along, but if they're waiting on motu-release or u-u-s then I already know how to do that :)
[16:19] <nhandler> slangasek: I think most/if not all of them are in progress. I will try to verify this, and create a list of any transition bugs that need someone to create a patch for
[16:19] <slangasek> there are also some initial FTBFS bugs resulting from the autobuild retest; anyone interested in working on those for universe?
[16:21] <nhandler> I'm not aware of any individual who is working on those bugs. \
[16:21] <slangasek> fair enough
[16:22] <nhandler> However, I can try to change that ;)
[16:22] <slangasek> ok :)
[16:22] <slangasek> nhandler: anything else we need to discuss?
[16:22] <nhandler> ScottK only had that one issue. I personally think we should be in good shape.
[16:22] <slangasek> excellent
[16:23] <slangasek> nhandler: thanks for keeping us informed
[16:23] <nhandler> You're welcome sla
[16:23] <slangasek> [TOPIC] AOB
[16:23] <MootBot> New Topic:  AOB
[16:23] <slangasek> any oddball issues to cover before we adjourn?
[16:24] <slangasek> #endmeeting
[16:24] <MootBot> Meeting finished at 10:24.
[16:24] <slangasek> thanks, folks!
[16:24] <lool> thanks
[16:24] <lool> happy week-end
[16:24] <robbiew> thnx
[16:26] <jcastro> friendly reminder!
[16:26] <jcastro> https://wiki.ubuntu.com/UbuntuOpenWeek/Prep
[16:26] <jcastro> plenty of slots left for openweek
[16:27] <nhandler> Thanks for the reminder jcastro, I should probably give some sort of session
[17:45] <doko> slangasek: yes, around, but the final 2.6.2 release is not yet made. still on my list
[18:09] <ember> persia ping, sorry i wasn't unable to attend