[14:57] <pitti> hello
[14:58] <heno> hey
[14:58]  * slangasek waves
[14:58] <fader_> Howdy
[14:59] <ScottK> o/
[15:00] <dendrobates> o/
[15:00]  * lool   \o/
[15:01] <pgraner-zzzz> o/
[15:01] <sbeattie> hey
[15:01] <cjwatson> hi
[15:01] <slangasek> mdz, davidm_, Riddell, Hobbsee: ping
[15:02] <robbiew> hi
[15:02] <slangasek> #startmeeting
[15:02] <MootBot> Meeting started at 09:02. The chair is slangasek.
[15:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:02] <slangasek> morning, folks
[15:03] <slangasek> [LINK] Agenda: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-04-03
[15:03] <MootBot> LINK received:  Agenda: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-04-03
[15:03] <slangasek> [TOPIC] Outstanding actions
[15:03] <MootBot> New Topic:  Outstanding actions
[15:04] <mdz> slangasek: here
[15:04] <mdz> davidm and I ran over a bit in our last meeting but are here now
[15:04] <slangasek> cjwatson: I see that NewReleaseCycleProcess is updated to talk about targeting the previous release notes; good
[15:04] <slangasek> mdz, davidm_: hi
[15:04] <davidm_> slangasek, hi
[15:05] <cjwatson> slangasek: aye
[15:05] <cjwatson> I did that during the last meeting ;)
[15:05] <slangasek> cjwatson: and I know I saw bugs from 8.10 release notes being targeted - is that all done now?
[15:05] <cjwatson> yep, that's all done
[15:06] <slangasek> great
[15:06] <slangasek> sbeattie: how are regression-release bugs looking?  I'm afraid I haven't had a chance to review them before the meeting
[15:06] <sbeattie> slangasek: bah, I didn't get to the release ones, I'll raise them with the rest of the QA team today.
[15:07] <slangasek> ok, thanks
[15:07] <slangasek> [TOPIC] QA team
[15:07] <MootBot> New Topic:  QA team
[15:08] <slangasek> sbeattie, heno, fader: how goes it?
[15:08] <fader_> Hardware testing is going well... we're not seeing any blockers in our daily testing: http://people.ubuntu.com/~fader/hw-testing/current.html
[15:08] <fader_> cr3 and I did a round of manual testing on some netbooks yesterday which did find some issues, mostly around sound
[15:08] <fader_> http://people.ubuntu.com/~fader/hw-testing/netbooks/
[15:08] <MootBot> LINK received:  http://people.ubuntu.com/~fader/hw-testing/netbooks/
[15:08] <fader_> We will be filing those bugs today
[15:09] <heno> We're running an Audio testing day on Monday
[15:09] <heno> please bring all your odd audio hardware to #ubuntu-testing on Monday :)
[15:09] <heno> pulse sound in seems to be the main problem
[15:10] <slangasek> I notice that the set of 'untested' machines is fairly static - are any of those being addressed?
[15:10] <fader_> slangasek: The untested machines now are mainly those with identified hardware problems or that have been removed for other purposes
[15:10] <mdz> slangasek: some of them are dupes, others are low priority
[15:10] <slangasek> ok
[15:10] <fader_> There's one that is not in that category that I am working on right now
[15:11] <heno> pulse in e.g bug: bug 311497
[15:11] <mdz> slangasek: (sparc are examples of the latter)
[15:11]  * slangasek nods
[15:12] <slangasek> the sparcs at least have annotations about bugs affecting boot
[15:12] <slangasek> are the bugs resulting from audio testing generally regressions from intrepid?
[15:13] <slangasek> or previously-unidentified problems?
[15:13] <davmor2> slangasek: I think they are a mixture of the 2
[15:13] <heno> slangasek: no, our impression is that it's slowly getting better but could be better still
[15:14]  * slangasek nods
[15:15] <slangasek> how has the flood of post-beta bugs been?  any classes of issues we need to highlight that haven't been so far?
[15:15] <heno> [QA team done]
[15:15] <heno> We had a spike of 5-600 bugs
[15:15] <heno> a fair number of upgrade issues have been reported
[15:16] <heno> as usual at beta
[15:16] <heno> pedro and I will work with mvo to help triage them more quickly
[15:16] <slangasek> ok, great
[15:17] <heno> and we'll hoover mailing lists for people's upgrade stories
[15:17] <slangasek> ok, thanks :)
[15:17] <slangasek> [TOPIC] Desktop team
[15:17] <MootBot> New Topic:  Desktop team
[15:17] <pitti> this week we made quite some good progress on RC bug fixing and resolved the remaining "intrusive changes" points; unfortunately we also got a couple of new jaunty targetted bugs
[15:18] <pitti> https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus has the current status
[15:18] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:18] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:18] <pitti> in summary, I'm quite content with the progress, except for bug 348316 which is a bitch
[15:19] <pitti> so if anyone has an USB printer which stopped working in jaunty and has this bug, Till and I would appreciate your help
[15:19] <pitti> facundobatista has it and volunteered to help
[15:19] <slangasek> I have a USB printer and it /hadn't/ stopped working in jaunty
[15:19] <mdz> I'm afraid to say my printer still works too
[15:19] <pitti> other issue is that the messaging indicator still has some upgrade issues and crashes, which the DX team is working on
[15:19] <pitti> mine works just fine as well
[15:20] <pitti> slangasek, mdz: not that I'd complain :)
[15:20] <mdz> pitti: I don't think I have the messaging indicator
[15:20] <mdz> I have indicator-applet and indicator-messages installed, but nothing new/interesting in my panel.  is that normal?
[15:21] <davidbarth> mdz: you need to run pidgin or evolution to see something
[15:21] <tedg> mdz: It only appears if you're running Pidgin or Evolution.
[15:21] <davidbarth> mdz: the indicator appears only when you have "indicating" applications running
[15:21] <mdz> ok
[15:21] <pitti> mdz: if you do intrepid->jaunty upgrade with update-manager, you should get a postinst question about adding it
[15:21] <mvo> the indicator-applet is added automatically on first login
[15:21] <mvo> no question for this
[15:22] <robbiew> +1
[15:22] <mvo> (we asked one for fusa, but that was different because we modified the users config, the indicator is just added)
[15:22] <mdz> (and fusa was in 8.10)
[15:22] <mvo> (yes)
[15:23] <mdz> moving on?
[15:23] <mdz> pitti: oh, what about intel X issues?
[15:23] <robbiew> yes!
[15:23] <mdz> slangasek: I emailed you about this prior to the meeting
[15:23] <pitti> mdz: all done
[15:23] <pitti> mdz: well, FSVO all
[15:23] <pitti> mdz: the 8x5 breakage
[15:23] <mdz> https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/339
[15:23] <mdz> 555
[15:23]  * slangasek nods to mdz
[15:23] <mdz> sorry, bug 339555
[15:24] <pitti> 845 and 855 now work, 865 was worked around with disabling DRI
[15:24] <mdz> pitti: that's good to hear that those are fixed; what was the bug number for that one?
[15:24] <pitti> mdz: bug 304871
[15:24] <mdz> thanks
[15:25] <mdz> pitti: any thoughts on 339555?
[15:25] <pitti> no idea about that one I'm afraid, it wasn't on the release team radar yet
[15:25] <mdz> bug 337608 is also relevant
[15:25] <mdz> since it affects one of the target netbooks
[15:27] <mdz> pitti: could you make sure that at least gets triaged?  it's not clear to me how serious it is
[15:27] <pitti> I'll talk to Bryce about them, whether we can at least bandaid them
[15:27] <mdz> ok, thanks
[15:28] <slangasek> [TOPIC] Mobile team
[15:28] <MootBot> New Topic:  Mobile team
[15:28] <lool> list of specs and bugs on our radar:
[15:28] <lool> [link] <https://wiki.ubuntu.com/MobileTeam/Roadmap>
[15:28] <MootBot> LINK received:  <https://wiki.ubuntu.com/MobileTeam/Roadmap>
[15:28] <lool> current high-level status per topic:
[15:29] <lool> - UNR notify-osd went in; good shape except for intel graphics regression on eeepcs (349314, 344443) and couple of pending-upload netbook-launcher issues (350989, 354003)
[15:29] <lool> - MID image is as good as usual
[15:29] <lool> - armel netbook images: need plenty of testing since the latest kernel changes (all of iop32x, versatile, ixp4xx have been changed for various bugs)
[15:29] <lool> - armel's "iMX51 Babbage": everything required for installers merged in archive; very good progress on the kernel front; work started on building cdimage/debian-cd based images -- instead of custom script -- these dailies are getting urgent; needs more
[15:29] <lool> testing
[15:29] <lool> - NEON: landed
[15:29] <lool> - VFP libs: 2/4 have patches attached; Emmet pursuing work but currently in Taipei for a sprint
[15:29] <lool> - other milestoned bugs: working on the armel issues, pretty much all assigned
[15:29] <lool> - Poulsbo: dropped; issue of intrepid drivers was understood, but it's too late for the jaunty ones now
[15:29] <lool> - touchscreen spec / support: still lacking; notably impacts Samsung Q1U used in mobile team
[15:29] <lool> that's for the status
[15:29] <lool> I'd like to discuss another topic which was brought to my attention this morning, but please ask questions on the status first
[15:30] <mdz> slangasek: how far are we from building imx51 using only the standard tools and repositories?
[15:30] <lool> I guess that was for me
[15:30] <cjwatson> mdz: that's the image work mentioned in lool's status update; it's waiting for my review essentially
[15:31] <cjwatson> (for about the last hour, so I'm not slacking too badly ;-) )
[15:31] <lool> Only one archive bit is missing, it's a binary blob which we would best generate from a tool instead
[15:31] <lool> However the debian-cd work just started; I didn't merge the full imx51 logic still; I expect it will take me a couple of days to get it cleanly mergeable
[15:31] <mdz> lool: from your comment it sounded like your part was done (everything merged in the archive)
[15:32] <mdz> but I misunderstood
[15:32] <slangasek> lool: btw, micro-evtd is seeded but I don't see an MIR for it anywhere so I haven't cleaned up the component-mismatch; do you know if there is an MIR somewhere, and if not, can someone take care of that please?
[15:32] <lool> The images which we generate manually are however fully built from archive (apart that small blob) and install with archive stuff only -- unless new bugs are pending discovery
[15:32] <lool> slangasek: There's a MIR for it, but it has a security bug
[15:32] <lool> It does some nasty things in /tmp
[15:32] <lool> And in general the programming style is really bad
[15:33] <slangasek> ah, there is
[15:33] <lool> I have documented this in Debian and suggested an approach for fixes, but I don't have the hardware, so it's hard to offer to fix them
[15:34] <lool> mdz: So back to what's missing, we need a tool to generate an empty binary config for babbage, I have that in my curtains since weeks; it's a really minor thing; all the rest of what needs to be in archive is in archive
[15:34] <slangasek> lool: are the VFP lib changes still on track, do you think?
[15:34] <lool> Most of the missing work is debian-cd / cdimage work on babbage
[15:34] <lool> slangasek: I do think they are unintrusive and trivial to test, get in, get out
[15:34] <slangasek> I mean, do you think the work will be done in time
[15:35] <lool> I think Emmet should be able to tackle the remaining packages before next week
[15:35] <slangasek> those bugs have lingered for a while already
[15:35] <slangasek> ok
[15:35] <lool> I agree
[15:35] <lool> Emmet has this at the top of his TODO
[15:35] <slangasek> alright
[15:36] <slangasek> cjwatson: you say the debian-cd/cdimage bits are waiting on your review only?
[15:36] <lool> It wont break anything if we don't "fix" these bugs, it will just be slower; I did commit that we would do this though
[15:36] <lool> Only some preliminary work is waiting for review; I didn't attack the actual imx51 changes, only prepared to be able to do them
[15:37] <cjwatson> ah, I hadn't looked enough to be able to say yet
[15:37] <slangasek> ok
[15:37] <lool> (generating vfat images was decided at a level where we don't decide per arch)
[15:37] <cjwatson> based on Oliver's earlier work, though, I think it is tractable for Jaunty
[15:37] <slangasek> cjwatson: do you have an ETA for when that might be done, so we could start getting daily builds?
[15:38] <cjwatson> slangasek: I'll review and hopefully merge lool's changes this afternoon; ETA for the rest of it is with lool, though
[15:38] <mdz> having to manually roll builds for imx51 would be rough going into the final stretch
[15:38] <slangasek> quite
[15:39] <slangasek> cjwatson: sounds good then
[15:39] <lool> Any other question?  I'd like to bring up another topic
[15:39] <lool> ARM indicated that FSL 2D/3D drivers were pending or already around; they wish we'd have an UNR image for armel so that there's a runnable image on systems where they add the drivers.  My personal opinion is that we wouldn't be able to QA such an image ATM and that I doubt the 2D/3D drivers would make it before release (but they might be SRU-ed), so I wouldn't want to release with an unusable or untested UNR armel image.  ARM also asked ...
[15:39] <lool> ... whether it was  possible to add an UNR image after release; I think we would do best by avoiding that as well.
[15:40] <slangasek> I think we're rather far along to be trying to expand the scope of the ARM release
[15:40] <slangasek> (i.e., if you're asking me, then "no")
[15:41] <lool> I am asking, and I did want to officially raise it before I came back with a no
[15:41] <lool> I do believe it's way too risky, but the practical testing constraints led me to think it wasn't possible anyway
[15:41] <slangasek> you might have been asking mdz rather than me :-)
[15:41] <davidm_> lool, from Freescale they said they don't have the drivers, so it's no from me
[15:41] <lool> Eh mdz is here, we had this meeting planned today, and I received that question this morning
[15:42] <mdz> (defer to davidm)
[15:42] <lool> Great, topic closed; done for mobile team
[15:42] <slangasek> moving on!
[15:42] <slangasek> [TOPIC] Kernel team
[15:42] <MootBot> New Topic:  Kernel team
[15:42] <pgraner> Hello.... I'll do the cut n paste of the bugs from slangasek email....
[15:43] <pgraner> * Kernel
[15:43] <pgraner>     * Bug:334994: Degraded RAID boot fails
[15:43] <pgraner>      - Fixed will get uploaded today
[15:43] <pgraner>     * Bug:348275: iwlagn: NM applet doesn't connect to WPA2
[15:43] <pgraner>      - Closed - Invalid
[15:43] <pgraner>     * Bug:292450: Broadcom kernel panics (reopened)
[15:43] <pgraner>      - Not a Jaunty issue we updated Jaunty to the latest Broadcom driver, the only affects Intrepid
[15:43] <pgraner>     * Bug:336055: wrong ESSIDs shown after resume
[15:43] <pgraner>      - Patch was committed, jerone reopened and we can't reproduce. pitti mentioned there might pm-utils work around.
[15:43] <pgraner>     * Bug:348316: CUPS USB printing broken, kernel regression?
[15:43] <pgraner>      - Not confirmed to be a kernel regression yet, testers are not reporting back.
[15:43] <pgraner>     * Bug:348382: linux-image-*-imx51 missing dependency on flash-kernel
[15:43] <pgraner>      - Fix Commited - Will be uploaded today
[15:43] <pgraner>     * Bug:345714: X crash in ioctl on iGM45
[15:43] <pgraner>      - robbiew debugging indicates this is not kernel but libdrm
[15:43] <pgraner>     * Bug:290153: can't boot Intel D945Gnt
[15:43] <pgraner>      - legit and we are workig on it
[15:43] <mdz> pgraner: confirm that 336055 is not a regression from 8.10?
[15:45] <lool> pgraner: Bug:348382: I've unmilestoned this one and dropped it to Low; it's just a nice to have to not take any risk and be consistent
[15:45] <pitti> it isn't from my POV
[15:45] <lool> (But it's fix committed anyway)
[15:45] <mdz> pgraner/heno: we need the list of netbook bugs as well
[15:45] <pitti> slangasek: said he'd work on the pm-utils workaround for 336055
[15:45] <mdz> the ones I have to hand are bug 348012, bug 340014, bug 319825
[15:45] <pgraner> mdz: its not a known regression
[15:45] <mdz> looks like the first two are still open
[15:45] <lool> pgraner: Thanks for the load of fixes in yesterday's kernel upload BTW
[15:45] <slangasek> pgraner: I don't understand how bug #348275 has been marked "invalid", when the bug reporters have stated in the bug that they're having this problem with the current kernel.
[15:45] <mdz> and I'm sure there are more; fader said there was a microphone issue
[15:46] <heno> mdz: fader is heading in to the Lex office to file with ubuntu-bug from the machines today
[15:46] <pgraner> mdz: the first two listed?
[15:46] <mdz> pgraner: 348012, 340014
[15:46] <mdz> pgraner: the first two of my (incomplete) list of netbook bugs
[15:46] <fader_> mdz: 348012 is still valid, but 319825 appears to be fixed... I wasn't able to reproduce it
[15:47] <pgraner> fader_: we think we found the sound issue we need you here to validate
[15:47] <mdz> fader_: how about 340014?  that's the more serious of the two
[15:47] <slangasek> pgraner: 336055 - as pitti says, if this isn't tractable from your side, we can kludge around it in pm-utils
[15:47] <fader_> 340014 is an issue as we don't have a power cord for that machine and I haven't been able to find one anywhere that fits it :(
[15:48] <fader_> (manjo has the cord but not with him; worst case he should be able to ship it once he is back home tomorrow)
[15:48] <slangasek> pgraner: 292450> likewise, there are users reporting this is still a problem in jaunty, so I don't see the basis for closing the bug?
[15:48] <slangasek> (https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/292450/comments/77)
[15:48] <mdz> pgraner: if 340014 doesn't get fixed, we're going to need to drop that model from the list, as we can't say it's compatible
[15:49] <pgraner> slangasek: 292450 there is nothing we can do except update to the latest binary driver which we did.
[15:49] <mdz> fader_: as indicated in the bug, 348012 needs someone to test whether this is the same with the stock OS.  if so, it's invalid and we can disregard it.
[15:49] <slangasek> pgraner: I understand that; but that doesn't mean the bug should be marked fixed if it isn't
[15:49] <pgraner> OK slow down guys I can't grock all this at once one issue at a time pls
[15:50]  * slangasek backs off :)
[15:50] <slangasek> (the kernel is popular!)
[15:50] <mdz> pgraner: you drive, which issue do you want to cover first?
[15:51] <pgraner> mdz: ack, lets go back to the ones that were orig on slangasek's list
[15:51] <mdz> start with 348275 then
 pgraner: I don't understand how bug #348275 has been marked "invalid", when the bug reporters have stated in the bug that they're having this problem with the current kernel.
[15:51] <davmor2> mdz: I got an AAO if you want I can try a standard install on it
[15:51] <mdz> davmor2: (hold on, we'll get there)
[15:52] <mdz> for what it's worth, I have 4965 in this laptop, and I just switched on wifi to test.  I can connect to my home WPA2 network fine with 2.6.28-11.38-generic
[15:53] <pgraner> slangasek: LP 3482775, rtg sees no reason why this doesn't work
[15:53] <pgraner> slangasek: its working with everything we have
[15:54] <mdz> actually, I seem to be able to associate and get an IP, but I can't ping the router. that's odd.
[15:55] <pgraner> mdz: both rtg and I are using the same card here and its working just fine
[15:55] <mdz> pgraner: it seems to be working OK now
[15:55] <mdz> I can ping it from another machine on the wifi net
[15:55] <mdz> it was human error
[15:55] <ogasawara> slangasek: https://bugs.edge.launchpad.net/ubuntu/+bug/348275/comments/27 seems to indicate it's fixed for original bug reporter as well
[15:56] <mdz> so I can't reproduce 348275 either
[15:56] <slangasek> ok
[15:56] <pgraner> slangasek: then we can make it fixed released according to ogasawara
[15:56] <mdz> next? 292450
 pgraner: 292450> likewise, there are users reporting this is still a problem in jaunty, so I don't see the basis for closing the bug?
 slangasek: 292450 there is nothing we can do except update to the latest binary driver which we did.
[15:57] <pgraner> slangasek: bug 336055 - we don't think its a kernel issues
[15:57] <mdz> either there is a bug or there isn't
[15:57] <slangasek> ogasawara: hmm, the preceding comment says "I can connect to my WPA2 network but after computer suspend I can't" (original submitter)
[15:57] <slangasek> I guess that's out of scope for the original report?
[15:58] <ogasawara> slangasek: yes, I'd likely open a new report for that issue after suspend
[15:58] <pgraner> mdz: they reported prior to the latest Broadcom update
[15:58] <slangasek> ogasawara: could you ask the submitter to do that, just so we're following through?
[15:59] <ogasawara> slangasek: sure thing
[15:59] <mdz> ogasawara: (FWIW I suspend every night and it's still working)
[15:59] <mdz> pgraner: do the release notes for the broadcom update say that they fixed this issue?
[15:59] <slangasek> pgraner: lrm hasn't updated since the 23rd, Peter Whittaker reopened the bug on the 27th
[16:00] <slangasek> https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/292450/comments/77
[16:00] <pgraner> mdz: they do not produce release notes
[16:00] <slangasek> (in which he also shows his version number is the one from the latest lrm changelog)
[16:00] <pgraner> mdz: its a black box, we really need to drop this driver
[16:00] <mdz> pgraner: that's a separate discussion, we're stuck with it for 9.04
[16:01] <pgraner> mdz: I know I know....
[16:01] <pgraner> I think that takes care of the first list, on to the netbook list
[16:01] <mdz> pgraner: if the upstream release didn't say they fixed this bug, what possible basis is there for this:
[16:01] <mdz> linux-restricted-modules (2.6.28-4.3) jaunty; urgency=low
[16:01] <mdz>   [Tim Gardner]
[16:01] <mdz>   * Update Broadcom wl to 5.10.27.11 from 5.10.27.6
[16:01] <mdz>     - LP: #292450
[16:02] <pgraner> mdz: thats the shim layer not the blob, rtg derived this from source
[16:02] <pgraner> s/source/shim source/
[16:03] <pgraner> mdz: rtg tells me the problem in question is in the blob not the shim layer
[16:03] <mdz> I don't see any indication in the bug that the new version fixed the problem for anybody
[16:04] <pgraner> mdz: again we don't know all we can do when its in the blob is update to the latest and hope for the best
[16:04] <slangasek> well, that would imply untargeting the bug from the release (--> wontfix), not closing the bug
[16:04] <mdz> pgraner: I understand.  if all we're doing is hoping for the best, though, don't close the bug
[16:05] <pgraner> mdz: got it
[16:05] <mdz> next?  336055
[16:05] <mdz> ?
[16:05] <rtg> slangasek: I did upload an update to wl this morning, here is the commit log: "The 5.10.79.10 update appears to have an update http://www.broadcom.com/docs/linux_sta/wl_iw_v2.patch
[16:05] <rtg>     that is already partially applied. Found the part that wasn't and applied by hand. It
[16:05] <rtg>     looks like it could fix a buffer overrun."
[16:06] <pgraner> mdz: waiting on LP
[16:06] <slangasek> rtg: ok, great - to be uploaded soon?
[16:06] <slangasek> pgraner: that's the "wrong ESSIDs after resume" bug
[16:06] <rtg> slangasek: already uploaded
[16:06] <mdz> excellent
[16:07] <slangasek> rtg: ah, great!
[16:08] <mdz> 348316 pitti covered already
[16:08] <slangasek> [ACTION] slangasek to follow up on state of bug #292450 to make sure it gets retested
[16:08] <MootBot> ACTION received:  slangasek to follow up on state of bug #292450 to make sure it gets retested
[16:08] <pgraner> mdz: on that one, no one else has me too'd it, we put a fix in that has worked for other includeing upstream, I'm suspect the jernone's reopening might be bogus
[16:08] <mdz> 345714
[16:08] <mdz> looks like 345714 needs to go to the desktop team then? pitti?
[16:08] <pitti> looks like
[16:09] <pgraner> mdz: ack
[16:09] <mdz> it's unassigned but pitti will take care of that I'm sure
[16:09] <pitti> assigned to desktop-team for now, will further process it from there
[16:10] <mdz> pgraner: how about the netbooks?  sounds like we need to get hardware into the right hands for 340014 urgently
[16:10] <pgraner> mdz: it will, fader_ was testing yesterday, we have everyone here to work on it
[16:11] <slangasek> pgraner: I can definitely (and trivially) reproduce bug #336055 with 2.6.28-11.38.  It hasn't been 'metoo'ed because some of us have been resigned to this misbehavior for more than one cycle now :/
[16:11] <fader_> 340014 is the one we can't currently test due to lack of a power cable for it
[16:11] <mdz> pgraner: he said he can't test due to a missing cable
[16:11] <slangasek> I'll follow up to that bug though
[16:11] <fader_> I've looked all over... none of the standard 'universal' cables fit it (thanks, Radio Shack)
[16:12] <pgraner> mdz: I just found out the cable didn't come with it
[16:12] <fader_> pgraner: My understanding is that manjo has the cable but brought the wrong one with him to Lexington
[16:12] <pgraner> mdz: In that case we might be able to get it before freeze
[16:13] <mdz> slangasek: we should take the cabling issue offline, can you record an action?
[16:13] <pgraner> fader_: yea, I just found that out
[16:14] <slangasek> mdz: whose action is it?
[16:14] <pgraner> mdz: we think we've squashed the sound issues, we will test today, fix was uploaded in todays kernel
[16:14] <mdz> slangasek: pgraner I guess
[16:14] <pgraner> slangasek: mine
[16:14] <mdz> there are an unknown (to me) number of other netbook bugs which haven't been filed yet
[16:14] <slangasek> [ACTION] pgraner to follow up on missing power cable for bug #340014
[16:14] <MootBot> ACTION received:  pgraner to follow up on missing power cable for bug #340014
[16:14] <mdz> fader_: can you at least tell us how many bugs there are pending to be filed?
[16:15] <fader_> mdz: 5, but they all may be one bug
[16:15] <fader_> (as they all deal with no sound being recorded)
[16:16] <mdz> slangasek: action for fader to get the sound input bug filed
[16:16] <mdz> bug(s) I guess
[16:16] <slangasek> [ACTION] fader to file bugs about sound input on netbooks
[16:16] <MootBot> ACTION received:  fader to file bugs about sound input on netbooks
[16:16] <fader_> mdz: I'll be heading in to the Lex office right after this meeting to file those
[16:16] <mdz> fader_: ok
[16:16] <slangasek> great
[16:17] <slangasek> ok; have we wended our way to the end of the kernel list?
[16:17] <mdz> that's it from me I think
[16:17] <pgraner> slangasek: nothing more from me
[16:17] <slangasek> ok, thanks
[16:17] <slangasek> [TOPIC] Foundations team
[16:17] <MootBot> New Topic:  Foundations team
[16:17] <slangasek> cjwatson, robbiew: hi
[16:18] <cjwatson> https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Jaunty is up to date
[16:18] <slangasek> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Jaunty
[16:19] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Jaunty
[16:19] <cjwatson> we have a moderate number of bugs, but there is reasonable progress on almost all of them
[16:19] <cjwatson> there are a couple of other specific concerns I'd like to raise
[16:19] <cjwatson> mvo is having trouble with python2.6 upgrade fixes (perhaps he can speak for himself on this)
[16:19] <cjwatson> and bug 353090 has come up for no very obvious reason - I'd appreciate help from a GTK expert
[16:20] <mdz> (waiting for the bug page to load...)
[16:20] <cjwatson> '(jaunty) Text hidden on "Who are you?" step'
[16:21] <cjwatson> I've reproduced it, it's just a mystery. The radio button labels are blank until you select one of them
[16:21] <robbiew> mvo has been working on bug 354228
[16:22]  * slangasek nods
[16:23] <sbeattie> Do we have a plan for making python upgrades less brittle? I've been hit by python breakage causing the upgrade to fail twice now.
[16:23] <cjwatson> I think we're in OK shape in general, but with evand on holiday all this week I've had to spend most of the week dealing with installer work, so am not as up to speed elsewhere as I would like
[16:23] <slangasek> cjwatson: do we need to solicit input from the desktop team on that bug?
[16:24] <slangasek> sbeattie: a plan for making intrepid->jaunty work, or a blue-sky plan to make python upgrades less brittle overall?
[16:24] <cjwatson> yes, I'd appreciate it
[16:24] <slangasek> pitti: can you take bug #353090 back to the desktop team and get some eyeballs on it?
[16:24] <mdz> pitti: maybe the DX guys could have a look
[16:25] <pitti> I'll ask robert
[16:25] <sbeattie> slangasek: I'll take what I can get.
[16:25] <cjwatson> I asked a question in our releasestatus page about bug 131227
[16:26] <slangasek> [ACTION] pitti to ask robert to look at bug #353090 (gtk strangeness in ubiquity)
[16:26] <MootBot> ACTION received:  pitti to ask robert to look at bug #353090 (gtk strangeness in ubiquity)
[16:26] <cjwatson> specifically "is this still RC given notify-osd?"
[16:26] <mdz> I'm having some trouble unwinding the maze of python bugs
[16:26] <mdz> cjwatson: can you provide a list of python2.6 upgrade bugs which need help?
[16:26] <cjwatson> mdz: bug 354228 is the current hub, I believe
[16:26] <slangasek> sbeattie: well, fixing 354228 is going to make it "less brittle"; we'll have a better idea once that's fixed whether there are other bugs needing attention
[16:27] <mdz> cjwatson: ah, I missed the open jaunty task on python2.6
[16:27] <cjwatson> there's also a question about 3.0 support there
[16:27] <mdz> it's New/Undecided though
[16:28] <cjwatson> mvo created that task so I assume that's just lack of having done the paperwork
[16:28] <slangasek> cjwatson: 131227> notification-daemon is still in main, I guess some people are going to prefer that to notify-osd; seems like an appropriate bug to fix in the package (incl. in SRU), but not a release blocker per se?
[16:28] <mdz> there's a python2.6 debdiff attached which claims to fix 343228
[16:28] <cjwatson> slangasek: ok, that matches my general opinion
[16:29] <cjwatson> mdz: right, I'm raising it just because it's been thorny so far, wasn't on the agenda, and needs particular QA attention
[16:29] <cjwatson> mdz: to my knowledge mvo is on top of it so far, although he's been making sounds of unhappiness at the design
[16:30] <mdz> cjwatson: ok, just trying to understand how we can help him
[16:30] <cjwatson> it doesn't seem as if he's paying attention to IRC just now, and I haven't spoken to him since this morning, so I think we'll have to take that out of band
[16:30] <mdz> ok
[16:31] <slangasek> all set?
[16:31] <cjwatson> given overtimeness, yes
[16:31] <slangasek> [TOPIC] Server team
[16:31] <MootBot> New Topic:  Server team
[16:31] <slangasek> dendrobates: hey-o
[16:31] <dendrobates> a couple things
[16:31] <dendrobates> soren will push a fix for bug 347622 and bug 347629 today.
[16:32] <dendrobates> Dustin uploaded a fix for bug 341159.
[16:32] <dendrobates> I'm not sure about bug 350089 it was not on my radar. Dustin seems to have looked at it, but not updated it yet.
[16:32] <dendrobates> bug 274849 was fixed a long time ago and not updated correctly.  Now marked as fix released.
[16:32] <dendrobates> There are 2 virt related bugs marked as regression-potential
[16:33] <dendrobates> Soren has not gotten to them, I will investigate and reassign as necessary.
[16:33] <dendrobates> bug 337763
[16:33] <dendrobates> bug 342359
[16:34] <dendrobates> that is all from me
[16:34] <slangasek> dendrobates: hmm, it sounds like you guys are tracking a number of bugs as 'critical' which have not been targeted to the release (https://wiki.ubuntu.com/RCBugTargetting).  Can you try to make sure bugs get targeted to jaunty, so the rest of us know what's going on in that regard?
[16:35] <dendrobates> slangasek: ack
[16:35] <slangasek> thanks
[16:35] <mdz> dendrobates: please also make sure to get bugs into the Triaged state as quickly as possible
[16:36] <dendrobates> mdz: yes, we have one member not doing it correctly.  I will fix that.
[16:36] <mdz> (I updated 341159 in that regard)
[16:36] <slangasek> [TOPIC] MOTU
[16:36] <MootBot> New Topic:  MOTU
[16:36] <slangasek> ScottK: hi
[16:36] <ScottK> Hi
[16:37] <ScottK> Python 2.6 transition is still #1 on the list.
[16:37] <ScottK> We're down to ~ half a dozen packages, but they are all FTBFS for one reason or another and will be hard.
[16:37] <ScottK> Some others are pending archive action for syncs.
[16:37] <mdz> ScottK: can you dump the bug numbers here so folks can help out if they're available?
[16:38] <ScottK> I don't have them handy.  I'll gather them and send mail.
[16:38] <mdz> ok
[16:38] <ScottK> The other transition is clamav.
[16:38] <slangasek> [ACTION] ScottK to mail list of outstanding python2.6 transition bugs
[16:38] <MootBot> ACTION received:  ScottK to mail list of outstanding python2.6 transition bugs
[16:38] <ScottK> We jumped off the cliff and upgraded to clamav 0.95 yesterday.
[16:39] <ScottK> That's got half a dozen rdpends.  We have patches for all but one and have started uploading.
[16:39] <ScottK> I think that'll land OK.
[16:39]  * slangasek nods
[16:39] <ScottK> Even in the unlikely event one has to go to an SRU, I think the benifits of moving forward far outweigh thtat.
[16:39] <ScottK> Some of us have been going through uninstallables and working on those.
[16:40] <slangasek> is there much QA activity this cycle around universe uninstall... yah :)
[16:40] <ScottK> This has resulted in a growing pile of removal bugs.
[16:40] <ScottK> Most of the focus has been on FTBFS and installable.
[16:40] <slangasek> are ubuntu-archive keeping up with them, or are they leaving them for me to deal with on Monday? ;)
[16:40] <ScottK> Python 2.6 sucked up a HUGE amount of time.
[16:41] <ScottK> slangasek: Most of them got filed very recently so AFAIK you'll get them monday.
[16:41] <slangasek> drat
[16:42] <slangasek> ScottK: ok, thanks
[16:42] <ScottK> For Python 2.6 we're in decent shape for builds/installs.  I have a lot of fear around working
[16:42] <ScottK> We'll just have to watch for bugs an react.
[16:42] <ScottK> We don't have a systematic way to really know.
[16:43]  * slangasek nods
[16:43] <ScottK> That's all I have.
[16:43] <slangasek> ok
[16:43] <slangasek> [TOPIC] AOB
[16:43] <MootBot> New Topic:  AOB
[16:43] <slangasek> I don't have anything else to break out today, so rather than flipping index cards - AOB?
[16:44] <slangasek> ISO sizes are doing well, fwiw; still working on refining tools to help us make sure they stay that way, but we found some space by splitting the GNOME user guide by language
[16:44] <mdz> make sure you know about the release party in your area!
[16:44] <slangasek> indeed :)
[16:45] <slangasek> oh, does anyone like charset manipulation in perl or python who would like to reimplement a ruby script for me?
[16:45] <mdz> https://wiki.ubuntu.com/JauntyReleaseParties
[16:45] <cjwatson> like? not especially. capable of? probably
[16:46] <slangasek> ttf-cjk-compact is currently responsible for ~40% of the component-mismatches
[16:46] <slangasek> for a ruby script used once at build time to get the list of glyphs
[16:46] <slangasek> anyway, if cjwatson is my volunteer, we can take that up later :)
[16:46] <slangasek> #endmeeting
[16:46] <MootBot> Meeting finished at 10:46.
[16:46] <slangasek> thanks, all!
[16:47] <pitti> slangasek: oh, is anyone looking at sorting out c-m? I'm afraid I can't, with me being away next week
[16:47] <cjwatson> slangasek: po2ul.rb?
[16:47] <slangasek> cjwatson: yes
[16:47] <heno> thanks
[16:47] <slangasek> pitti: I've been whittling it down over the past few weeks
[16:47] <pitti> okay, thanks all
[16:47] <lool> thanks
[16:47]  * pitti goes to pack stuff now
[16:48] <cjwatson> slangasek: doesn't look too hard
[16:49] <slangasek> yeah, it's "suck in the strings, get them in the right charset, sort -u"