[16:01] <pitti> hello
[16:01] <ttx> o/
[16:01] <ScottK> o/
[16:03]  * lool \o/
[16:06]  * ScottK guesses there's time to go get coffee
[16:07] <ttx> ...
[16:08] <lool> Is slangasek leading the meeting today?
[16:08] <pitti> he was going to
[16:09] <pitti> 1.5 hours ago he said he'd take a nap before the meeting
[16:09]  * lool calls
[16:09]  * pitti call... oh, got beaten to it
[16:09] <lool> voicemail
[16:10] <lool> pitti: I only have one number
[16:10] <slangasek> hi
[16:10] <cr3> could we call his chumpy?
[16:10] <lool> Morning
[16:10] <slangasek> morning
[16:10] <pitti> hey slangasek
[16:10] <slangasek> #startmeeting
[16:10] <MootBot> Meeting started at 10:10. The chair is slangasek.
[16:10] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:11] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-10-23
[16:11] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-10-23
[16:12] <slangasek> [TOPIC] QA Team
[16:12] <MootBot> New Topic:  QA Team
[16:13] <marjo> HW Certification Testing
[16:13] <marjo> Netbooks:
[16:13] <marjo>    passed:      10 (91%)   failed:      0  ( 0%) untested:    1  ( 9%)
[16:13] <marjo> Laptops:
[16:13] <marjo>    passed:      26 (100%)  failed:      0  (  0%) untested:    0  (  0%)
[16:13] <marjo> Servers:
[16:13] <marjo>    passed:      48 (94%)   failed:      0  ( 0%)  untested:    3  ( 6%)
[16:13] <marjo> Desktops:
[16:13] <marjo>    passed:      12 (100%)  failed:      0  (  0%)  untested:    0  (  0%)
[16:13] <marjo> pitti: another 100%
[16:13] <pitti> \o/
[16:13] <lool> impressive
[16:14] <marjo> Karmic Release Candidate Test Report
[16:14] <marjo> 2009-10-22
[16:14] <marjo> == Test Coverage ==
[16:14] <marjo> Image Test Coverage = 100%
[16:14] <marjo> Test Case Coverage = 100%
[16:14] <marjo> Beta Test Coverage = 99%
[16:14] <marjo> Alpha 6 Test Coverage = 58%
[16:14] <marjo> [16:14] <marjo> 10 Test Failures
[16:14] <marjo> Failure Rate 8/194 = 5.1%
[16:14] <marjo> Beta Failure Rate = 8%
[16:14] <marjo> Alpha 6 Failure Rate = 15%
[16:14] <marjo> Based on these test results, Karmic looks good
[16:14] <marjo> from testing point of view
[16:15] <marjo> == Bugs summary ==
[16:15] <marjo> [16:15] <marjo> 38 bugs unfixed
[16:15] <marjo> Critical - 1
[16:15] <marjo> High - 11
[16:15] <marjo> Medium - 8
[16:15] <marjo> Low - 4
[16:15] <marjo> Undecided - 15
[16:15] <marjo> [16:15] <marjo> 11 bugs fixed
[16:15] <marjo> Critical - 1
[16:15] <marjo> High - 7
[16:15] <marjo> Low - 1
[16:15] <marjo> Undecided - 2
[16:15] <marjo> I will send out the detailed test results in an email
[16:16] <marjo> that's all from QA
[16:16] <slangasek> do you have the bug number of the unfixed critical bug handy?
[16:17] <marjo> no i don't
[16:17] <ScottK> 401406
[16:17] <marjo> thx ScottK
[16:18] <slangasek> bug #401406
[16:18] <slangasek> thanks
[16:19] <slangasek> doesn't look like one we need to discuss here
[16:19] <pitti> I feel karmic is really working well if that is the only critical bug we have :)
[16:19] <marjo> agree
[16:19] <cr3> pitti: almost too well, it is unsettling indeed
[16:19] <slangasek> heh
[16:19] <slangasek> [TOPIC] Desktop Team
[16:19] <MootBot> New Topic:  Desktop Team
[16:20] <slangasek> pitti: so let's talk about some non-critical bugs? :)
[16:20] <pitti> This week we landed the new GNOME point release in time. No problems reported from that
[16:20] <pitti> other than that we pretty much exclusively did RC bug fixing
[16:20] <pitti> and some polishing
[16:20] <pitti> https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:20] <pitti> freshly updated again some 5 minutes ago
[16:21] <pitti> so, the remaining bugs which haven't a fix available don't worry me too much any more
[16:21] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:21] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:21] <ScottK> slangasek: Jumping back a topic, I also see Bug 441338 and Bug 443089
[16:21] <pitti> 408530 and 428884 really ought to be fixed in an SRU
[16:22] <pitti> ScottK: sounds like a dupe of bug 264336 ?
[16:22] <ScottK> Dunno.
[16:22] <pitti> sorry
[16:22] <pitti> bug 448921
[16:23] <slangasek> ScottK: for critical bugs?  I was wondering about the one that had been linked from ISO testing; 'critical' looks wrong for 443089, but we can talk about it with the kernel team?
[16:23] <ScottK> Certainly, just trying to make sure I'd given a complete answer.
[16:24] <pitti> so, that eject thing is not really a dk-disks bug (it does what it can), we either need to fix it in the kernel (stop locking altogether) or stop totem from locking it again
[16:25] <slangasek> pitti: 408530, 428884> agreed
[16:25] <pitti> oh, and 77010 was accepted into karmic
[16:26] <pitti> (page updated)
[16:26] <pitti> jockey fix as well (updated again)
[16:26] <slangasek> pitti: 448921 should probably be considered for SRU too, then?
[16:26] <pitti> any questions wrt. desktop from anyone?
[16:26] <slangasek> (-->targeted to karmic)
[16:27] <pitti> slangasek: depends how intrusive it is
[16:27] <pitti> eject button works for CDs, etc. but not for video DVDs
[16:27] <pitti> as soon as you start totem, that is
[16:27] <slangasek> pitti: should it be targeted to keep it on the radar?
[16:27] <pitti> if we need to fix it in the kernel, it might not be appropriate
[16:27] <pitti> slangasek: fine for me; we can still wontfix it if it becomes too intrusive
[16:28] <pitti> done
[16:28] <slangasek> thanks
[16:28] <slangasek> no other questions from me; anyone else?
[16:29] <ScottK> You want any Kubuntu status now?
[16:29] <slangasek> yes, please
[16:30] <ScottK> We have a few uploads pending, but are in good shape generally.
[16:30] <slangasek> (if there's status to mention, that is - not meaning to put you on the spot specifically :)
[16:30] <ScottK> http://www.flickr.com/photos/freeflying/4036438792/in/set-72157622515083587/ <- Kubuntu Netbook on Freescale
[16:30] <MootBot> LINK received:  http://www.flickr.com/photos/freeflying/4036438792/in/set-72157622515083587/ <- Kubuntu Netbook on Freescale
[16:30] <ScottK> I think the news is good.
[16:30] <slangasek> :)
[16:31] <ScottK> The only real serious unresolved problem I know of seems only to affect my laptop, so we probably needn't hold the release for that.
[16:31] <ScottK> BTW, the packagekit upload that's pending is there for Kubuntu to fix a crasher.
[16:31] <ScottK> That's it
[16:32] <slangasek> (noted)
[16:32] <slangasek> thanks
[16:32] <slangasek> moving on?
[16:32] <slangasek> [TOPIC] DX Team
[16:32] <MootBot> New Topic:  DX Team
[16:32] <davidbarth> hi
[16:32] <slangasek> davidbarth: hey
[16:32] <davidbarth> the summary is at: https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus
[16:32] <davidbarth> mainly
[16:32] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus
[16:32] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/KarmicReleaseStatus
[16:33] <lool> davidbarth: https://bugs.launchpad.net/bugs/456412
[16:33] <davidbarth> 1 n-osd crasher that we're trying to reproduce; seems rather specific to emesene though
[16:33] <lool> davidbarth: I think this one should be on your radar as well
[16:33] <davidbarth> lool: hmm, for the release or an SRU?
[16:34] <lool> davidbarth: Either is fine; release is preferred but it's ok
[16:34] <davidbarth> a rhyhtmbox issue due to n-osd
[16:34] <lool> I'm sorry, I failed pinging you directly on this bug
[16:34] <davidbarth> lool: if you take the patch before the release, we can rush this one in; we'll see with neil or jason
[16:34] <lool> (It's just ugly)
[16:34] <lool> (Not breaking anything)
[16:34] <davidbarth> lool: i'm more concerned about the keyring issue
[16:35] <lool> Well that one seems intrusive to fix
[16:35] <davidbarth> and a n-osd font problem for people using fractional fonts (ie 9.4, instead of just 10pt)
[16:35] <lool> So even if it's an usability issue, I think the test might have to be deferred if it is intrusive
[16:35] <lool> s/test/fix/
[16:35] <davidbarth> lool: the point is that i'm not sure who's looking at it now
[16:36] <davidbarth> lool: it falls right in the middle of unr, desktop, etc.
[16:36] <lool> Hmm
[16:37] <lool> In my eyes, netbook-launcher + UNR's window picker applet are responsible for hiding/showing windows as they appear/disappear, even if metacity is involved
[16:37] <lool> So it would seem logical that they review the state of open windows on startup
[16:37] <davidbarth> so i guess my point now is asking the desktop team which patches they still want to take for the release, between the 3 n-osd and a potential one for xsplash; see http://tinyurl.com/ylhxuzy
[16:38] <lool> At least I think that's what I proposed on the bug; if it's not possible or a bad idea, could you comment on the issues with the approach in the bug?
[16:38] <davidbarth> and how to manage the unr one, which has impacts outside of unr itself
[16:38] <davidbarth> pitti, slangasek, lool?
[16:39] <pitti> davidbarth: if they are tiny and 100% safe, I'm fine with slipping them in
[16:39] <slangasek> which one is "the UNR one"?
[16:39] <lool> Oh I failed to comment on the bug too, I only chatted with njpatel on IRC tss I suck
[16:39] <lool> https://bugs.launchpad.net/ubuntu/+source/netbook-launcher/+bug/447886
[16:39] <davidbarth> yep
[16:40] <davidbarth> it's a nasty usability issue, basically, you boot unr for the first time and you can't really connect to the network!
[16:40] <lool> I think something like "for all open windows, put window on top" at the end of the netbook-launcher startup sequence would do the trick, but again I'm fine deferring that as a SRU
[16:40] <pitti> that seems worth fixing in final
[16:40] <lool> I think libwnck can help with this
[16:41] <slangasek> yes, if it can be corrected in a targeted manner in netbook-launcher, I think it would be best to have that in final
[16:41] <lool> I've updated milestone
[16:41] <davidbarth> ok, so we're saying: try hard to fix this one, as a workaround specific to netbook-launcher; using tricks we see fit to bring the keyring window on the top
[16:42] <lool> davidbarth: I think it's really not a workaround to do what I suggest: if netbook-launcher crashes and is respawned, the same issue will happen I bet
[16:42] <lool> And you can't use root window tricks since it's a complex set of windows, not just a single x window
[16:43] <slangasek> none of the others seem quite as bad for usability impact; I think we would take targeted fixes for them on Monday if available, but if not they all seem like reasonable SRU candidates
[16:43] <davidbarth> lool: can we see that offline after the meeting?
[16:43] <lool> davidbarth: Sure
[16:43] <davidbarth> slangasek: ok
[16:43] <slangasek> hmm, the xsplash one doesn't seem critical to me and probably not something we want to SRU for
[16:43] <slangasek> bug #435692
[16:44] <lool> I agree; it's just not perfectly pretty
[16:44] <slangasek> I realize it's aesthetically displeasing, but the timeout code has caused us enough problems already for one release cycle
[16:44] <slangasek> and I would prefer not to try to change it at the very end
[16:44] <pitti> and for slower machines it's ugly either way
[16:45] <slangasek> davidbarth: do you agree?
[16:45] <davidbarth> slangasek: i agree it's tricky to move now
[16:46] <slangasek> so you're ok with leaving that until lucid?
[16:46] <davidbarth> slangasek: moving it as a tentative sru though, or as an indenpendant ppa
[16:46] <slangasek> ok
[16:46] <pitti> doesn't really sound like SRU matter either IMHO
[16:47] <slangasek> pitti: tend to agree, but figure we can discuss that when the fix is available; PPA is obviously ok :)
[16:47] <slangasek> anything else on the DX front?
[16:48] <davidbarth> nope, that's it
[16:48] <slangasek> [TOPIC] Mobile Team
[16:48] <lool> [link] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic
[16:48] <lool> Overview of overall status (more details since we're close to release):
[16:48] <lool> * UNR: good shape
[16:48] <lool>   * wubi needs image rerolling + testing; davmor2 offered help, StevenK is looking for a license key
[16:48] <lool> * general armel stuff
[16:48] <lool>   * toolchain related rebuilds have been pushed
[16:49] <lool> * armel+mx51: ok
[16:49] <lool>   * Babbage 2.0 is in a bad shape for both Jamie and I, but my hardware is very unstable; could either be hardware breakage and/or kernel/bootloader regressions   :-/   We need to dig up what's happening here but we suspect the kernel mxcfb changes regressed our graphics
[16:49] <MootBot> New Topic:  Mobile Team
[16:49] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic
[16:49] <lool> * armel+dove: ok
[16:49] <lool>   * Need to cleanup installation instructions
[16:49] <lool>   * Installation is very slow
[16:49] <lool> * Ubuntu Moblin Remix: ok
[16:49] <slangasek> for wubi you're referring only to a UNR image reroll, right?
[16:49] <lool>   * APT error is really fixed
[16:49] <lool>   * would like to fix mutter crash
[16:49] <lool> Yes
[16:49] <lool> That said, I pushed sources which are in all images
[16:49] <slangasek> (for the bug we've already discussed - ok, good)
[16:49] <lool> Like apt
[16:49] <lool> (For the toolchain rebuilds)
[16:51] <slangasek> mutter> I guess that's best effort; bug is listed as confirmed yet, do you think this will be fixed on Monday?
[16:51] <lool> slangasek: I was hoping for today
[16:51] <slangasek> ok
[16:51] <slangasek> no other questions from me; anyone else?
[16:52] <slangasek> [TOPIC] Server Team
[16:52] <MootBot> New Topic:  Server Team
[16:52] <slangasek> ttx: hi
[16:52] <ttx> slangasek: o/
[16:52] <ttx> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus was updated
[16:52] <ttx> The key remaining issue is bug 458850, which is a consequence of eucalyptus not acting like EC2 about ephemeral disks
[16:53] <ttx> We confirmed with EC2 community that this was a feature they are usually relying on
[16:53] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:53] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:53] <ttx> So we would like to fix that in our images themselves. That should just affect the cloud images, not the server ISO
[16:53] <ttx> we would also fix bug 458576 in the same run
[16:54] <ttx> this last one is really low-risk. The first one... that depends on how smoser fixes it exactly
[16:54] <slangasek> latter sounds ok, sure
[16:54] <slangasek> will have to wait and see the fix for the former
[16:54] <ttx> slangasek: exactly
[16:55] <ttx> we expect to be affected by the maven overhaul, since it toucjhes libraries used in server packages
[16:55] <ttx> bug 454822
[16:55] <slangasek> ttx: do you know how close we are to being done with maven?  I haven't been able to track it, every time I look there's yet another bug report somewhere about it
[16:55] <ScottK> I think we are getting close
[16:55] <slangasek> how close?
[16:55] <pitti> I keep playing whack-a-rat with NEW and syncs
[16:56] <pitti> maven2 built now \o/
[16:56] <ttx> slangasek: doko reported maven2 building now
[16:56] <ScottK> That close
[16:56] <pitti> doko_ says some plugins are still missing
[16:56]  * pitti hugs doko_ for his great efforts on this
[16:56] <doko_> maven2 itself is built, will be published within a few minutes
[16:57] <slangasek> the wiki page mentions commons-beanutils and backport-util-concurrent - are those still needed?
[16:57] <ttx> slangasek: those were updated already
[16:57] <ScottK> I think they are done.
[16:57] <ttx> slangasek: those were the ones affecting eucalyptus
[16:57] <slangasek> ok, but they're already done?
[16:57] <ttx> doko_: you expect a tomcat6 update now ?
[16:57] <doko_> slangasek: yes
[16:58] <ttx> tomcat6 is on the server CD, so...
[16:58] <slangasek> doko_: so are we completely done with maven2 package updates in main for karmic?  the missing plugins are optional, I hope?
[16:58] <ScottK> Also potentially affecting the server CD ... I'm planning to cherrypick the Debian clamav repo over the weekend (I was expecting an upload in Debian that hasn't materialize) that close out a number of clamav packaging bugs and then next week I'll push clamav 0.95.3 to -proposed.
[16:59] <doko_> ttx: yes, but not now. needed for maven-site-plugin and maven-debian-helper. we should include this if possible. http://people.canonical.com/~doko/tmp/ has my current tomcat6 merge
[16:59] <doko_> slangasek: no, libservlet2.5-api-java needs the POM as well, see the current merge above, I still have to test that
[16:59] <ttx> doko_: I'll review it
[17:00] <ttx> (not now)
[17:00] <slangasek> doko_: why is libservlet2.5-api-java needed?
[17:00] <slangasek> ScottK: clamav> ack
[17:00] <doko_> slangasek: b-d for maven-site-plugin
[17:01] <slangasek> and why would we not just tell people "sorry, this bit didn't make it"?
[17:01] <doko_> and libmaven-site-plugin-java is needed for maven-debian-helper
[17:01] <ttx> (sigh)
[17:02] <pitti> the maven OS
[17:02] <doko_> slangasek: well, the source package is in, and if ttx can review it ...
[17:02] <doko_> I'll work on that tomorrow
[17:02] <ttx> I'll do my best
[17:02] <doko_> have to leave now, sorry
[17:03] <slangasek> doko_: that still doesn't answer the question of why we want to fiddle with a package on the server CD the week of release to get this universe package working
[17:03] <slangasek> I guess we'll discuss that out-of-band, since doko has to go
[17:03] <slangasek> anything else for server?
[17:04] <slangasek> [TOPIC] Kernel Team
[17:04] <MootBot> New Topic:  Kernel Team
[17:05] <slangasek> pgraner, apw: about?
[17:05] <pgraner> slangasek: yep, sorry we are sprinting today
[17:06] <slangasek> pgraner: no worries; one way or another I want to touch base with you on the two bugs I've posted to the wiki, do you have time for that right now?
[17:06] <pgraner> slangasek: sure
[17:06]  * pgraner looks
[17:06] <slangasek> bug #453579
[17:06] <slangasek> bug #459022
[17:07] <slangasek> the first one was Keybuk's "ext4 is making swiss cheese of my ISO downloads" bug
[17:07] <slangasek> I would appreciate it if the kernel team could follow through and see whether this is reproducible at all
[17:08] <Keybuk> slangasek: I've just updated my desktop to karmic with a reinstall to get proper ext4
[17:08] <slangasek> (if not reproducible, triage it away - if it is reproducible, we need to figure out where the bug is)
[17:08] <Keybuk> and replacement laptop hard drive has arrived, and being installed right now
[17:08] <Keybuk> so if I can reproduce it, I'll let you know
[17:08] <slangasek> Keybuk: ok, thanks
[17:08] <Keybuk> I'm still not 100% sure it's not the dodgy pre-production SSD in that other laptop
[17:08] <apw> Keybuk, if you could that would help a lot
[17:08] <Keybuk> the only reason I filed it was other people were reporting the corrupt deb thing
[17:08] <Keybuk> kernel team have access to the same dodgy pre-production SSDs though - so they could test
[17:09] <apw> Keybuk,which model is it
[17:09] <Keybuk> apw: am I allowed to say? :p
[17:09] <apw> Keybuk, tell me offline in case
[17:09] <Keybuk> the ones we were given at the last UDS
[17:09] <pgraner> Keybuk: thats NDA
[17:09] <slangasek> Keybuk: yes, dodgy hardware is a possibility - but we should be aggressive about trying to reproduce this (incl. on other hardware) so we're sure it's ok to turf this for release
[17:10] <pgraner> slangasek: ack, we will get back to you shortly, we are all here so we can quickly sort it, hopefully
[17:10] <slangasek> thanks
[17:10] <pgraner> slangasek: and the metapkg bug we will fix right now
[17:10] <slangasek> pgraner: great, thanks!
[17:11] <slangasek> that's it from me - any concerns on your side?
[17:11] <pgraner> slangasek: nope we are holding with what we got
[17:11] <slangasek> how big's the queue for the day-zero kernel SRU drop? :)
[17:12] <pgraner> slangasek: we have 3 or 4 patches pending but they are minor.
[17:12] <slangasek> ok
[17:12] <pgraner> slangasek: to answer no we are not doing a day zero
[17:12] <slangasek> sounds good; will let you get back to sprinting then :)
[17:12] <pitti> pgraner: would bug 77010 fit there? (config chagne only)
[17:12] <pitti> pgraner: ^ disables CONFIG_HDA_BEEP thing
[17:13] <slangasek> pitti: not a blocker for final, can be discussed out of band, I think?
[17:13] <pgraner> pitti: I'll have apw look at it
[17:13] <pitti> right, for SRU
[17:13] <pgraner> slangasek: yep\
[17:13] <pitti> ok,s orry
[17:13] <slangasek> [TOPIC] Security Team
[17:13] <MootBot> New Topic:  Security Team
[17:13] <slangasek> jdstrand: hi, anything to say release-wise?
[17:14] <jdstrand> o/
[17:14] <slangasek> (AFAIK your RC buglist is empty now)
[17:14] <jdstrand> as always https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus
[17:14] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus
[17:14] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus
[17:14] <jdstrand> there is one bug: bug #457716
[17:15] <jdstrand> oh, someone accepted it! :)
[17:15] <slangasek> fixed already ;)
[17:15] <jdstrand> there are no bugs
[17:15] <slangasek> ok, great :)
[17:15] <jdstrand> ;)
[17:15] <jdstrand> well, no *RC* bugs
[17:15]  * slangasek nods
[17:15] <pitti> jdstrand: just reviewed it, and seemed fine (pinpointed fix)
[17:15] <jdstrand> I am not claiming anything is bug-free
[17:15] <slangasek> heh
[17:15] <slangasek> any questions for security, then?
[17:16] <jdstrand> other than that, I don't have anything. all the pending stuff has been addressed
[17:16] <jdstrand> pitti: thanks!
[17:16] <slangasek> [TOPIC] Foundations Team
[17:16] <MootBot> New Topic:  Foundations Team
[17:16] <slangasek> Keybuk: are you still covering today, or is cjwatson around now?
[17:17] <Keybuk> cjwatson is today
[17:17] <slangasek> cjwatson: ping
[17:18] <slangasek> ok, will follow up out of band I guess
[17:18] <slangasek> Keybuk: anything we should talk about wrt mountall/usplash?
[17:18] <slangasek> or bug #432089?
[17:18] <Keybuk> mountall has a bug that affects a couple of cases (most notable elmo)
[17:18] <Keybuk> I believe ion has fixed that, and I just need to upload once I'm fully back online
[17:19] <Keybuk> usplash has a "not pretty" bug wrt CLEAR, which ion has also fixed
[17:19] <Keybuk> the sreadahead problem isn't simple
[17:19] <Keybuk> I have a possible solution, but you won't like it ;D
[17:19] <cjwatson> urg, sorry, I started late today and my times are completely shot
[17:20] <cjwatson> (didn't get back from NI until lunchtime)
[17:20] <slangasek> Keybuk: heh, let's discuss that after the meeting then so the others don't have to listen to the yelling ;)
[17:20] <cjwatson> there's a bug with RAID and virtio that I think needs to be fixed in grub2, bug 457687
[17:20] <cjwatson> working on that at the moment
[17:20] <cjwatson> and apparently root on iSCSI is busted somehow
[17:20] <cjwatson> bug 457767
[17:21] <cjwatson> I'm on the former, but if somebody serverish could pick up the latter, I'd greatly appreciate it
[17:21] <slangasek> ttx: do you have someone who can look at 457767?
[17:22] <slangasek> cjwatson: can you target/milestone both bugs?
[17:22] <cjwatson> yep
[17:22] <ttx> slangasek: hmm
[17:22] <ttx> slangasek: maybe Dustin, he used to work on that before iSCSI support was taken by Foundations
[17:23] <slangasek> [ACTION] kirkland to follow up on bug #457767
[17:23] <MootBot> ACTION received:  kirkland to follow up on bug #457767
[17:23] <cjwatson> I know it's our responsibility, just takes a while for somebody new to set it up, and I don't think I have personal bandwidth :-/
[17:23]  * cjwatson will owe somebody a favour
[17:24] <slangasek> Keybuk: when are you "fully back online", btw?
[17:24] <Keybuk> slangasek: when the apt run finishes and I reboot after ;)
[17:24] <pitti_> meh, server just broke apparently
[17:24] <slangasek> ok
[17:24] <Keybuk> (rsync is beating apt atm)
[17:25] <slangasek> I think that's all I have on foundations
[17:25] <slangasek> anything else?
[17:26] <slangasek> [TOPIC] MOTU
[17:26] <MootBot> New Topic:  MOTU
[17:26] <slangasek> ScottK: still going strong on the bugfixes?
[17:26] <ScottK> Maven was my exciting topic and we covered that already.
[17:26] <slangasek> hehe
[17:26] <ScottK> For a small value of strong, sure.
[17:26] <ScottK> There's stuff coming in, but it's not a torrent.
[17:27]  * slangasek nods
[17:27] <ScottK> I think we are pretty well into "It is what it is" territory
[17:27] <ScottK> The Kaffe removal (which motu-release has now ack'ed) needs to get done.
[17:27] <ScottK> That's just a stack of sync's and a removal, so shouldn't be a big deal.
[17:28] <slangasek> right
[17:28] <ScottK> Uninstallable packages is much lower than Jaunty.
[17:28] <ScottK> So the FTBFS count is the major worry ATM.
[17:28] <ScottK> I think we ought to revisit how we deal with this stuff at UDS.
[17:29] <slangasek> sounds reasonable
[17:29] <ScottK> That's all I have.
[17:29] <slangasek> ok, thanks
[17:29] <slangasek> any other questions for MOTU?
[17:29] <slangasek> [TOPIC] AOB
[17:29] <MootBot> New Topic:  AOB
[17:30] <slangasek> anything else we need to talk about, or is everybody clear on their marching orders? :)
[17:30] <slangasek> candidate ISO rolls will start as soon as the queue looks quiesced Monday morning (UTC)
[17:30] <ScottK> As a general note, I'd like to mention that in this cycle it's seemed to me that Kubuntu got a lot more support from people outside the Kubuntu team and it's much appreciated.
[17:31] <slangasek> great to hear
[17:31] <marjo> ScottK: i second that
[17:31] <pitti_> slangasek: langpacks finished to build; I'll test them now
[17:32] <slangasek> pitti_: ok
[17:32] <pitti_> slangasek: shall I upload them when I'm happy with them, so that they can build over the weekend?
[17:32] <slangasek> pitti_: yes, please
[17:32] <slangasek> #endmeeting
[17:32] <MootBot> Meeting finished at 11:32.
[17:32] <slangasek> ok, let's go get that bug list down to zero :)
[17:33] <pitti_> yay
[17:35] <lool> thanks
[17:35]  * lool &