[14:58] <pitti> hello
[14:59] <ScottK> Hello.
[14:59] <fader_> Howdy
[14:59] <robbiew> hi
[15:00] <heno> hey
[15:00] <sbeattie> hey
[15:01] <mdz> hello everyone
[15:01] <davidbarth> hi
[15:02]  * pgraner o/
[15:02] <rickspencer3> hi
[15:02] <cjwatson> hi
[15:03] <rickspencer3> pgraner: I was thinking of filing a critical RC bug: desktop background has no bunny
[15:03] <rickspencer3> but I figured slangasek wouldn't find it too funny
[15:03]  * robbiew calls slangasek
[15:04] <slangasek> here
[15:04] <lool> wee
[15:04] <robbiew> hey
[15:04] <robbiew> :)
[15:04]  * lool hugs slangasek and hands a good cup of RC coffee to him
[15:05] <pitti> hey slangasek, good morning
[15:05] <slangasek> morning :)
[15:05]  * robbiew adds an espresso shot to slangasek's good cup 
[15:05] <pgraner> rickspencer3: dooh!
[15:06] <mdz> slangasek: good morning
[15:06] <slangasek> Riddell, dendrobates, Hobbsee: ping?
[15:07] <dendrobates> slangasek: o/
[15:07] <Hobbsee> temporary pong!
[15:08]  * ScottK thinks Riddell is busy scribbling release notes.
[15:08] <slangasek> ok, hi all :)
[15:08] <slangasek> #startmeeting
[15:08] <MootBot> Meeting started at 09:08. The chair is slangasek.
[15:08] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:08] <slangasek> [TOPIC] Outstanding actions
[15:08] <MootBot> New Topic:  Outstanding actions
[15:09] <slangasek> one outstanding action from last week:
[15:09] <slangasek>  * rickspencer to follow up with Kubuntu team regarding state of plasma-widget-network-manager and encrypted wireless
[15:09] <ScottK> Thus my thought Riddell is busy scribbling release notes.
[15:09] <slangasek> rickspencer3: did you find anything there?
[15:09] <rickspencer3> yes
[15:10] <rickspencer3> I follows up with the Kubuntu team last week
[15:10] <rickspencer3> they discussed the issue, and it's obviously not easy to fix
[15:10] <rickspencer3> the result is that they are documenting the workaround on their release notes
[15:10] <rickspencer3> they are also including knetworkmanager on the alternate install CD for users who need to go that route
[15:10] <ScottK> alternate CD/dvd
[15:10] <rickspencer3> right
[15:10] <rickspencer3> thanks ScottK
[15:11] <slangasek> ok, thanks
[15:12] <rickspencer3> slangasek: ack on ScottK's theory, I believe Riddell is writing the release notes as we speak
[15:12] <cjwatson> ScottK: it only seems to be on the DVD right now
[15:12] <slangasek> as I said in the email, with the RC shortly behind us I didn't try to produce an exhaustive list of RC bugs in the agenda
[15:12] <ScottK> cjwatson: Yes.  That's the intent.
[15:12] <slangasek> [LINK] https://bugs.launchpad.net/ubuntu/jaunty/+bugs?field.milestone=2202
[15:12] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/jaunty/+bugs?field.milestone=2202
[15:12] <cjwatson> ScottK: oh, you meant s/CD/DVD/ then?
[15:12] <rickspencer3> cjwatson: sorry, I mispoke
[15:13] <cjwatson> I thought by "alternate CD/dvd" you meant both
[15:13] <ScottK> No.  Sorry.  Too much brevity.  Intead of.
[15:13] <mdz> slangasek: is there a version of that list which shows assignee?
[15:14] <slangasek> but that link above gives the entire set of bugs that are currently marked as targeted and milestoned for final; if there are other things your team is working on for inclusion in final, *please* make sure that they get targeted/milestoned ASAP for tracking
[15:14] <slangasek> mdz: I'm not aware of one
[15:15] <mdz> heno: don't you produce a milestone report which provides a more complete summary?
[15:15] <slangasek> [TOPIC] QA team
[15:15] <MootBot> New Topic:  QA team
[15:15] <slangasek> (we'll just hand the floor to heno then)
[15:15] <Hobbsee> mdz: there is, but it's not easy to get at, and i remember it involves constructing URLs
[15:15] <mdz> I swear I've seen it
[15:16] <pitti> mdz: the +milestone page, I bet
[15:16] <pitti> that doesn't have packages
[15:16] <Hobbsee> mdz: look up the previous releases of release notes.
[15:16] <heno> mdz: not sure what you're referring to
[15:16] <pitti> mdz: (re "list with assignee")
[15:16] <mdz> pitti: this was an HTML report of the style the QA team makes
[15:16] <slangasek> there's the milestone page (https://launchpad.net/ubuntu/+milestone/ubuntu-9.04), but there's no way to filter that by targeted bugs
[15:17] <robbiew> sounds like an LP bug to me
[15:18]  * mdz makes a note for 9.10
[15:18] <cjwatson> (arbitrary columns in bug pages: https://bugs.launchpad.net/malone/+bug/78608)
[15:18] <heno> fader_: can you report on HW testing?
[15:18] <fader_> Current status: http://people.ubuntu.com/~fader/hw-testing/current.html
[15:18] <fader_> Servers are looking quite good.  We did a round of manual laptop testing that uncovered a number of bugs, which are reflected on the status page.
[15:18] <fader_> The bugs themselves are listed here: https://wiki.ubuntu.com/Testing/Laptops
[15:18] <fader_> Several laptops were not tested due to a power issue, but cr3 has resolved that and will be doing a final test on those as well
[15:19] <fader_> cr3 is also working to narrow down when those bugs on the laptops were introduced and should have more information on that shortly
[15:19] <heno> (we should be able to make a more useful milestone view, yes)
[15:19] <fader_> Also, for reference, we have the list of manual testing for netbooks on the wiki here: https://wiki.ubuntu.com/Testing/Netbooks
[15:20] <slangasek> [LINK] http://people.ubuntu.com/~fader/hw-testing/current.html - hw testing status
[15:20] <MootBot> LINK received:  http://people.ubuntu.com/~fader/hw-testing/current.html - hw testing status
[15:20] <slangasek> [LINK] https://wiki.ubuntu.com/Testing/Laptops - bugs from manual laptop testing
[15:20] <MootBot> LINK received:  https://wiki.ubuntu.com/Testing/Laptops - bugs from manual laptop testing
[15:20] <slangasek> [LINK] https://wiki.ubuntu.com/Testing/Netbooks - results of netbook manual testing
[15:20] <MootBot> LINK received:  https://wiki.ubuntu.com/Testing/Netbooks - results of netbook manual testing
[15:21] <heno> we're starting ISO smoke testing now
[15:22] <slangasek> fader_: I trust the remaining untested/failed hardware is all non-critical, given that there's no room left for a kernel update before final to fix anything...
[15:22] <heno> start final testing when candidate images are available next week
[15:23] <heno> slangasek: right, we are targeting some for SRUs
[15:23] <slangasek> ok
[15:23] <heno> that's it from QA
[15:24] <slangasek> ok, thanks
[15:24] <slangasek> nothing else to highlight that needs to be escalated for fixing before release?
[15:25] <slangasek> [TOPIC] Desktop team
[15:25] <MootBot> New Topic:  Desktop team
[15:25] <heno> no, we've escalated along the way
[15:25] <slangasek> (guess not)
[15:25] <pitti> As usual, RC bug status is on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:25] <slangasek> heno: great, thanks :)
[15:25] <pitti> The biggest issues we have are with the intel video driver. Lots of fixes went into it already, and at this po
[15:25] <pitti> int we won't touch the Jaunty package any more, since any kneejerk patch will only lead to new regressions.
[15:25] <pitti> Fortunately most of the crasher issues on ReleaseStatus have patches which currently wait testing feedback, so
[15:25] <pitti>  these look like good SRU candidates.
[15:26] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:26] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:26] <pitti> Except for one particular case (bug 349992), the bad performance with default EXA is something we are stuck wi
[15:26] <pitti> th for Jaunty.
[15:26] <pitti> With Karmic, -intel 2.7 and kernel 2.6.30 it should all fix itself, but it looks impossible to
[15:26] <pitti> solve with the Jaunty versions.
[15:26] <pitti> https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes documents workarounds for both the crashes and the bad pe
[15:26] <pitti> rformance, and at least we don't know about systems any more where the driver doesn't work at all, so I think
[15:26] <pitti> it's "good enough" for the release.
[15:26]  * pitti apologizes for the broken line endings; how come that copy&paste works that bad?
[15:27] <mdz> pitti: can you provide a link to the test packages?  I'd love to try fixes for the freeze issue
[15:27] <pitti> mdz: they are all linked from the bug reports
[15:28] <mdz> pitti: 359392?
[15:28] <pitti> mdz: that doesn't have one yet, I'm afraid
[15:29] <pitti> "greedy" might help
[15:29] <mdz> pitti: that seems to be the worst one
[15:29] <rickspencer3> pitti: mdz: also try         Option "EXAOptimizeMigration" "off"
[15:29] <slangasek> pitti: 277589> that doesn't need thorough debugging, I think it just needs you and I to have a conversation about the right place to put the fdi bits so that they're applied in the right order; (https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/277589/comments/51) still not for final, but maybe for SRU?
[15:29] <pitti> mdz: the mitigation here is likely to revert some intel related patches in mesa 7.4
[15:31] <pitti> slangasek: oh, nice
[15:33] <pitti> slangasek: lets talk about this off-meeting then
[15:33] <slangasek> indeed
[15:33] <slangasek> anything else to say about intel?
[15:33] <pitti> yes, but it wouldn't be constructive, nor decent
[15:33] <ScottK> Not that's consistent with the CoC.
[15:33] <slangasek> mm :)
[15:34] <slangasek> [TOPIC] Mobile team
[15:34] <MootBot> New Topic:  Mobile team
[15:34] <lool> list of specs and bugs on our radar:
[15:34] <lool> [link] <https://wiki.ubuntu.com/MobileTeam/Roadmap>
[15:34] <MootBot> LINK received:  <https://wiki.ubuntu.com/MobileTeam/Roadmap>
[15:34] <lool> current high-level status per topic:
[15:34] <rtg> pitti: http://www.advogato.org/person/mjg59/diary.html?start=203
[15:34] <lool> - UNR: a small pile of medium or minor bugs in netbook-launcher, maximus, and desktop-switcher will be addressed in SRUs; more Intel regressions; need to recommend a Windows image writing tool, currently following various strings (OEM's usb-creator fork); need to propagate info on supported netbooks, system reqs, and installation procedure to {www,help}.ubuntu.com; there was a last minute fix to d
[15:34] <lool> isable multiverse and install ubuntu-standard, which I've underlined a key testi
[15:34] <lool> ng point to the team
[15:34] <lool> - armel netboot images: ixp4xx tested post RC (testing started too late and takes 8 hours), versatile passed

[15:34] <lool> - MID image is as good as usual
[15:34] <lool> - armel iMX51 Babbage: good shape, appart of the general hardware/kernel issues
[15:34] <lool> - VFP: all merged except cairo; cairo changes sent to Debian, but relatively large (rules rewrite); I'm writing a less intrusive version but this might miss 9.04 and perhaps be added as SRU
[15:34] <lool> - lpia: we didn't spot the lack of DHCP during the alternate install, new kernel was uploaded to address this; otherwise good shape
[15:34] <lool> - armel: good shape
[15:35] <lool> slangasek: I think davidm and you should spend some time preparing the part of the announcement related to ARM stuff for final
[15:35] <slangasek> yes
[15:35] <lool> Perhaps that happened already
[15:36] <slangasek> this morning I'm drafting an announcement to send to u-d-a about ARM RC; will pass that by davidm and mdz for review ASAP
[15:36] <davidm> we have been do some talking :-/ slangasek might want my head at this point ;-)
[15:37] <lool> slangasek: Otherwise, I don't think we want to link particularly to the orion5x and iop32x flavors, but not sure whether the current publications are automatic or not, in which case it's fine
[15:37] <slangasek> lool: ixp4xx post-RC> all the same, it's linked from the netboot page now, and before the ARM announcement has gone out, so all's well
[15:37] <lool> the former being untested and the latter not good enough
[15:38] <cjwatson> ... what orion5x flavour? I thought we disabled that
[15:38] <cjwatson> (and somebody was complaining that we didn't have it on #ubuntu-devel the other day ...)
[15:39] <lool> cjwatson: Yes, somebody was complaining but I couldn't reply that we simply had no tester for it
[15:39] <lool> And that person had left already
[15:39] <slangasek> lool: cairo> I think I dropped the milestone from that bug because it didn't look SRU-y to me, are you still considering this?  (if so that's fine, I guess it'll pop back up for discussion when it's ready)
[15:39] <lool> cjwatson: I /think/ I saw the netboot kernels at some place
[15:39] <lool> slangasek: Let's see how acceptable you find the changes when looking at the diff
[15:40] <lool> (for cairo)
[15:40]  * slangasek nods
[15:40] <cjwatson> lool: I'm pretty sure I disabled the d-i build for it
[15:40] <cjwatson> (it broke)
[15:40]  * ogra likes to correct ixp4xx numbers, testing takes 11h+
[15:40] <lool> cjwatson: I think that was an additional image, but ICBW
[15:41] <lool> cjwatson: I see it disabled in ./build/config/armel.cfg, probably just my imagination
[15:41] <slangasek> lool: even if the cairo patch is up in time, I'm unlikely to try squeezing that in for final, FYI
[15:41] <lool> slangasek: Ok
[15:42] <slangasek> lool: is there anything else on your radar that should be gotten in for final? bug #338148, maybe?
[15:42] <lool> No, that's ok; it's just to port more packages, but we don't seed it by default
[15:42] <slangasek> ah, didn't see that bug title before I linked to it; seems unlikely
[15:42]  * slangasek nods
[15:43] <slangasek> anything else?
[15:43] <lool> Not from me, happy to take more questions
[15:43] <slangasek> no other questions here, thanks
[15:43]  * ogra likes to point out that usb-imagewriter is in universe now
[15:43] <ogra> on multiple requests
[15:43] <slangasek> davidm: oh, is it settled now whether ARM is going in the u-a mail for final?
[15:44] <davidm> slangasek, not quite yet, will be shortly
[15:44] <slangasek> ok
[15:44] <slangasek> [TOPIC] Kernel team
[15:44] <MootBot> New Topic:  Kernel team
[15:45] <davidm> there was a meeting that interfered with getting that resolved.  Sorry.
[15:45] <pgraner> slangasek: Kernel is in the can.... barring any show stoppers
[15:45] <slangasek> we've had a late kernel upload as mentioned above, fixing DHCP for lpia and also fixing one of our ext4 bugs; things appear to be going smoothly there for its lateness, we should have test images available with that kernel on them by late today
[15:46] <pgraner> slangasek: ack
[15:46] <slangasek> otherwise, as you say there shouldn't be more kernel activity before final - is there anything we need to discuss about jaunty SRU?
[15:46] <pgraner> slangasek: rtg was planning a SRU upload next week to -proposed
[15:46] <slangasek> sounds good
[15:47] <rtg> pgraner: I'm planning to smb do the upload :)
[15:47] <slangasek> :)
[15:47] <rtg> s/to/to have/
[15:47] <pgraner> slangasek: I'll be going thru the hw failures and get them lined up for SRU as well
[15:47] <slangasek> excellent
[15:47] <pgraner> slangasek: nothing else from kernel
[15:48] <slangasek> please make sure bugs that are aimed at SRU get targeted to jaunty, as this significantly reduces the bits the SRU team has to push around when processing them
[15:48] <pgraner> slangasek: WILCO
[15:48] <slangasek> pgraner, rtg: thanks
[15:48] <slangasek> [TOPIC] Foundations team
[15:48] <MootBot> New Topic:  Foundations team
[15:49] <cjwatson> ISO testing was pretty busy for (some of) us last week, fielding issues as they came in
[15:49] <cjwatson> we have a reasonably respectable list of installer bugs for post-RC; this is basically all in the can now, modulo archive acceptance
[15:49] <cjwatson> (he says, tapping the release button on oem-config)
[15:49] <slangasek> :)
[15:50] <cjwatson> upgrade tests are mostly OK now that the python issues have been dealt with
[15:50] <cjwatson> there've been a few reports of usb-creator problems, which may need an upload, but haven't talked with Evan about that yet
[15:51] <cjwatson> we seem to be getting good reports of boot speeds at the moment :-)
[15:51] <slangasek> there was a post-RC accept of a change regarding the rtinstall script, to make sure byte-compilation gets done for python2.6 even if 2.6 isn't listed in supported; any sign of regressions there?  the change seemed moderately risky to me
[15:52] <cjwatson> bug 271962 is my only concern, really; that seems to have been dropped on the floor. Probably an SRU deal though since no fix is known yet
[15:52] <slangasek> right
[15:52] <cjwatson> slangasek: Michael's going to do a test battery with today's archive
[15:52] <slangasek> ok, excellent
[15:53] <cjwatson> that's all I'm aware of; anything I'm missing?
[15:53] <slangasek> nothing I know of
[15:54] <slangasek> thanks
[15:54] <cjwatson> oh, I forgot about bug
[15:54] <cjwatson> 360460
[15:54] <cjwatson> bug 360460 (sorry)
[15:54] <cjwatson> I think that might be a dmraid-only deal, but I'm going to carry on investigating that; not a stop-ship yet, just a worry
[15:54] <slangasek> incomplete> guess I shouldn't wait for that before uploading d-i for the new kernel, in any case
[15:54] <cjwatson> no, I'm just about to upload d-i now
[15:54] <slangasek> ah
[15:55] <slangasek> [TOPIC] Server team
[15:55] <MootBot> New Topic:  Server team
[15:55] <slangasek> dendrobates: hi
[15:55] <dendrobates>  slangasek: hi 2 things.
[15:56] <dendrobates> first pitti brought it to my attention the likewise-open-gui is not in any seed
[15:56] <dendrobates> and will therefore drop out of main.
[15:56] <slangasek> yeah, saw the email on that; it was accidentally unseeded in kirkland's run, I meant to ask you where you wanted it put back
[15:56] <dendrobates> I don't feel it is my call to decide if a gui tool is in main
[15:56] <slangasek> well, ok
[15:56] <slangasek> then pitti can tell us :)
[15:56] <pitti> erm?
[15:56] <pitti> I have never seen it
[15:57] <pitti> dendrobates: so, if you don't know/want it, let's drop it
[15:57] <dendrobates> I thnk it is good for ubuntu, but I think the desktop team needs to decide if they wnat it.
[15:57] <dendrobates> ok
[15:57] <dendrobates> also, kirkland is working on some post-rc kvm bugs.
[15:58] <slangasek> yes, there was an upload in the queue that I kicked back at him; is there a revised upload yet?
[15:58] <dendrobates> slangasek: he spoke with oyu and you were uncertain about  one of the fixes.
[15:58] <kirkland> slangasek: i can split the one controversial one out
[15:58] <slangasek> ok
[15:58] <kirkland> slangasek: i'll upload without the fix you questioned
[15:58] <kirkland> slangasek: however, that one fix is the most critical one, in our opinion
[15:58] <kirkland> slangasek: i see your point about regression chances, however
[15:59] <kirkland> slangasek: and i won't argue with you on that point :-)
[15:59] <slangasek> critical, but higher-risk; if you can give me assurances that it's safe...
[15:59] <slangasek> otherwise, it's fine for SRU when we have more time to bake it
[15:59] <dendrobates> slangasek: we will work on providing that assurance.
[15:59] <ScottK> Speaking of which, slangasek I'd like to discuss after the meeting exactly how much of the clamav update you'll let me get away with.
[16:00] <slangasek> dendrobates: ok - if we can get there, I can always un-reject the upload
[16:00] <slangasek> ScottK: yep
[16:00] <dendrobates> that's all from us, I think we're in pretty good shape.
[16:00] <slangasek> good to hear :)
[16:00] <slangasek> thanks
[16:00] <slangasek> [TOPIC] MOTU
[16:00] <MootBot> New Topic:  MOTU
[16:01] <kirkland> slangasek: i'm uploading with that one patch still in the package, but left out of the debian/patches/series file
[16:01] <ScottK> I think we're in decent shape.
[16:01] <ScottK> My biggest concern continues to be the Python transition.
[16:01] <ScottK> We're mostly through the "won't install due to Python 2.6" problems.
[16:01] <slangasek> we're down to just the one python transition bug on the milestone list; are there more bugs thought to be hiding?
[16:01] <ScottK> So now we're getting the "doesn't work due to Python 2.6 problems"
[16:02] <slangasek> kirkland: that will only make it more awkward to do a sensible review of the SRU later...
[16:02] <ScottK> It's mostly latent stuff I'm worried about.  I've done several uploads myself yesterday and today for this reason.
[16:02] <kirkland> slangasek: ok
[16:02] <ScottK> Mostly the bugs are easy to fix, but I expect a busy SRU season.
[16:03] <pitti> stuff like "as" identifiers?
[16:03] <ScottK> That was one.
[16:03] <slangasek> ScottK: <nod> understood
[16:03] <ScottK> Another is support for Gopher was removed.
[16:03] <ScottK> We actually had a package that supported it.
[16:03] <pitti> right, I remember fixing a package for that as well
[16:03] <cjwatson> we really need to work on automatic scans for this sort of thing
[16:03] <cjwatson> python language changes aren't going away
[16:03] <pitti> python-mechanize AFAIR
[16:04] <ScottK> md5/hashlib is a deprecation warning, but I've seen it cause test suite failures.
[16:04] <ScottK> We'll just have to work through it.
[16:04] <cjwatson> the documentation processors changed, which broke something that was using python's old documentation processor
[16:04] <slangasek> ScottK: I notice the round of bugs that did get filed for universe FTBFS haven't gotten much attention; I was thinking to 'wontfix' those for jaunty, on the theory that if no one's looked at them yet they probably aren't going to get SRU attention and so don't need to be tracked, but can be reopened if someone is keen later
[16:04] <ScottK> Speaking of which, I think we ought to have some sessions at UDS on lessons learned from Jaunty.
[16:04] <cjwatson> I had to make something build-dep on python2.5-dev for that
[16:05] <robbiew> ScottK: good idea
[16:05] <slangasek> ScottK: in reference to python, or more broadly?
[16:05] <ScottK> slangasek: I think we've done the easy ones.  I'd push them to jaunty-updates instead of wontfix, but your call.
[16:05] <ScottK> slangasek: More broadly, but Python is high on my list.
[16:05]  * slangasek nods
[16:05] <ScottK> I think it is something we should do every UDS.
[16:05] <slangasek> will you coordinate with robbiew to get those sessions on the agenda?
[16:05] <robbiew> perhaps every track should have a "Lessons Learned: session
[16:06] <ScottK> I think that's sensible.
[16:07] <robbiew> slangasek: I'll take the action
[16:07] <ScottK> My only other comment is that we're being fairly liberal about pushing stuff through to get features synchronized.
[16:07] <slangasek> [ACTION] robbiew to get "lessons learned from Jaunty" scheduled for UDS
[16:07] <MootBot> ACTION received:  robbiew to get "lessons learned from Jaunty" scheduled for UDS
[16:08] <slangasek> ScottK: is that a cause for concern?
[16:08] <ScottK> Also since this is the last pre-release meeting, I'd like to note that having a motu-release member who also have the archive-admin button in LP has seemed to me to be very helpful this cycle.
[16:08] <slangasek> or just fair warning to us? :)
[16:08] <ScottK> slangasek: Just fair warning.
[16:08] <slangasek> archive-admin button> yep, glad to see that happening
[16:09] <ScottK> I'm confident we're making stuff better, just some of the change is large.
[16:09] <pitti> ScottK: indeed, thanks for helping out with that
[16:09] <slangasek> though I wouldn't have the patience to have to download the packages locally in order to diff them :/
[16:09] <pitti> slangasek: queuediff FTW :)
[16:09] <slangasek> pitti: does that not still download?
[16:09] <ScottK> slangasek: That's been a huge pain.  queuediff wil be a great help.
[16:09] <pitti> slangasek: sure, it has to, but in most cases jsut the two diff.gzs
[16:09] <slangasek> unless you've created a remote diffing service when I wasn't looking, the whinge stands :)
[16:10] <pitti> I have used it a lot today, and it's fairly quick
[16:10] <pitti> in most cases quicker than q fetch / mdebdiff
[16:10] <slangasek> I guess that will vary by connection speed. :)
[16:10] <pitti> slangasek: yeah, it's a pain for native/new upstream release
[16:10] <slangasek> [TOPIC] Known regressions
[16:10] <MootBot> New Topic:  Known regressions
[16:10] <slangasek> [LINK] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=regression-potential
[16:10] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=regression-potential
[16:10] <pitti> but I don't see how this can be helped with in principle, short of soyuz producing the diffs itself
[16:11] <ScottK> Which it ought to be able to do ....
[16:11] <slangasek> so, this is the last time we'll look at this URL for jaunty; next Thursday, all the regression-potential bugs roll over to regression-release
[16:11] <slangasek> many of these are already targeted; any that aren't already in progress are pretty certainly not candidates for further updates before final, though
[16:12] <slangasek> we probably want to mine the remaining items on that list for release notes candidates; any volunteers to help with that?
[16:12] <cjwatson> the ssh/gnome-keyring issues have been a huge pain; I've been getting lots of reports misfiled on openssh for that (both here and in Debian)
[16:12] <cjwatson> is gnome-keyring likely to get fixed?
[16:13] <cjwatson> (usual symptom is something like "Agent admitted failure to sign using the key")
[16:13] <slangasek> hadn't seen that
[16:13] <slangasek> bug ref?
[16:13] <lool> can't delete keys from agent, all keys are loaded in agent etc. I guess
[16:13] <slangasek> there was a gnome-keyring update on the 13th; are these problems from before or after?
[16:14] <pitti> it's been ages since I've seen that (hardy timeframe)
[16:14] <lool> Perhaps I'm mixing unrelated issues, but I see a pile of complaints that g-k forces itself to act as an agent and doesn't work as well as it should be
[16:15] <pitti> slangasek: bug 348126
[16:15] <cjwatson> lool: that's certainly what I'm thinking of
[16:15] <slangasek> seahorse, not g-k?
[16:15] <pitti> it has no useful reproduction steps, though
[16:16] <cjwatson> seahorse used to be a problem; the recent cases I've seen were gnome-keyring, though
[16:16] <slangasek> "please attach your private key to this bug"
[16:16] <slangasek> :/
[16:16] <pitti> slangasek: g-k is right, seahorse task is invalid
[16:16] <slangasek> ok
[16:16] <lool> It's not the place to have a discussion about keeping g-k as a ssh agent or not, let's have this for karmic, but we could at least work on making it a real replacement
[16:16] <cjwatson> err, sorry, I seem not to have an Ubuntu example to hand right now, Debian #524018 is one
[16:16] <cjwatson> but that's a reasonable example of the sort of thing I've been getting reports of in Ubuntu too
[16:17] <lool> Right, the fact we start ssh-agent in almost all Xsessions is the reason I asked upstream to auto disable the SSH components when an agent is already running
[16:17] <slangasek> ok; do we need to escalate that with seb128, and figure out what to do with it post-release? (either for karmic or in SRU)
[16:17] <lool> (I simply suggested to check SSH_AGENT stuff in the env, but upstream told me to disable it in GConf)
[16:18] <slangasek> lool: heh, rather missing the point of "auto" disabling...
[16:19] <lool> Yeah I think it was missing the point of distro needs versus user needs   :-/
[16:19] <pitti> I'll ask seb/robert to triage it and get a reproduction recipe
[16:19] <cjwatson> thanks
[16:19] <slangasek> [ACTION] pitti to ask seb/robert to triage the gnome-keyring "can't use keys" problem
[16:19] <MootBot> ACTION received:  pitti to ask seb/robert to triage the gnome-keyring "can't use keys" problem
[16:20] <slangasek> [TOPIC] ISO size
[16:20] <MootBot> New Topic:  ISO size
[16:20] <slangasek> this is mostly a footnote, since our CD sizes shouldn't be changing very much before final
[16:20] <slangasek> ... which means, if you *are* uploading something for consideration for final, please make sure the size difference for your package is sane
[16:20] <pitti> slangasek: (done)
[16:21] <slangasek> we had one upload that was going to add 800K to the install size of a seeded package... that got rejected
[16:21] <slangasek> [TOPIC] Release notes
[16:21] <MootBot> New Topic:  Release notes
[16:21] <slangasek> there are probably many items that should still get documented in the notes between now and release
[16:21] <pitti> slangasek: yeah, kwwii has a new image (jpg now) which reduces package size by 600 KB
[16:22] <pitti> haven't looked at it yet
[16:22] <slangasek> remember that you can nominate bugs for mention in the release notes by opening a task on the ubuntu-release-notes project; please use this liberally
[16:22] <slangasek> (and ask your teams to do so as well)
[16:22] <slangasek> nominating bugs for the release notes is not a promise to draft the text (though we appreciate help there :)
[16:23] <slangasek> [TOPIC] AOB
[16:23] <MootBot> New Topic:  AOB
[16:24] <slangasek> last call for jaunty! anything else?
[16:24] <cjwatson> there are some ubuntu-archive bugs still open; I'll be trying to finish making a pass through all of them today (not necessarily taking action on them all)
[16:24] <cjwatson> anything filed there after today will need special notice to #ubuntu-release
[16:27] <slangasek> #endmeeting
[16:27] <MootBot> Meeting finished at 10:27.
[16:27] <slangasek> no need to let the clock run out ;-)
[16:27] <robbiew> thnx
[16:27] <slangasek> thanks, folks
[16:27] <pitti> thanks anyone