[15:59]  * marjo waves
[16:00]  * ttx waves
[16:00] <pitti> hai
[16:00] <seb128> hey
[16:01] <jdstrand> o/
[16:01]  * slangasek waves
[16:01] <slangasek> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is slangasek.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-04-16
[16:02] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-04-16
[16:02]  * asac waves
[16:02] <slangasek> [TOPIC] Previous actions
[16:02] <MootBot> New Topic:  Previous actions
[16:02] <slangasek>   * rickspencer to ask designers about new Edubuntu logo
[16:02] <slangasek>   * doko to grep the archive for codecs.open in python code, to find other packages broken by http://bugs.python.org/issue691291
[16:02] <slangasek>   * ScottK, slangasek to review python sync/merge candidates (INPROGRESS)
[16:02] <slangasek>   * marjo to make sure the outstanding optional testcases for beta2 get tested this week
[16:02] <slangasek>   * ogasawara to triage bug #557429 for final (DONE)
[16:02] <slangasek>   * pitti to get discussion of SRU extension for GNOME, KDE, OOo, OpenJDK point releases on UDS agenda
[16:02] <slangasek>   * Riddell to investigate the lingering Kubuntu installer issues
[16:02] <slangasek>   * ScottK to put out a call for Kubuntu daily ISO testing
[16:02] <pitti> slangasek: SRU extension is on the agenda
[16:03] <slangasek> ok, thanks
[16:03] <pitti> https://wiki.ubuntu.com/DesktopTeam/10.10/BlueprintList
[16:03] <slangasek> how'd we do on the other action items?
[16:03] <marjo> slangasek: Ara working with dpm and ttx to cover some optional test cases.
[16:04] <slangasek> great
[16:04] <slangasek> ScottK, Riddell: how have we fared with the Kubuntu installer?
[16:06] <slangasek> [TOPIC] QA Team
[16:06] <MootBot> New Topic:  QA Team
[16:06] <marjo> HW Testing (automated)
[16:06] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:06] <marjo> Netbooks:
[16:06] <marjo>    passed:   13 (93%) failed:    0 ( 0%) untested:  1 ( 7%)
[16:06] <marjo> Laptops:
[16:06] <marjo>    passed:   39 (90%) failed:    3 ( 7%) untested:  1 ( 3%)
[16:06] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:06] <marjo> Servers:
[16:06] <marjo>    passed:   64 (94%) failed:    0 ( 0%) untested:  4 ( 6%)
[16:06] <marjo> Desktops:
[16:06] <marjo>    passed:   13 (100%) failed:    0 (  0%) untested:  0 (  0%)
[16:06] <marjo> HW Testing (manual)
[16:06] <marjo> http://people.canonical.com/~fader/milestones/lucid/post-beta.html
[16:06] <MootBot> LINK received:  http://people.canonical.com/~fader/milestones/lucid/post-beta.html
[16:06] <marjo> passed: 45 (76%)    failed: 14 (24%)
[16:06] <marjo> Bugs will be reported on all failures
[16:07] <fader_> (Just to clarify, bugs have been reported for all failures; some just have not been triaged yet)
[16:07] <marjo> fader: thx for clarification
[16:08] <marjo> ISO Testing Bugs Status
[16:08] <marjo> http://people.canonical.com/~marjomercado/isotestingbugs.html
[16:08] <marjo> 558382	Partitioner throws "Unable to satisfy all constraints" when trying to use previously created partitions - cjwatson to investigate
[16:08] <marjo> 557930	[Lucid Beta2] After first boot Live Kubuntu Netbook doesn't start X and fallback to a textual terminal - pedro to work with Riddell
[16:08] <marjo> 557807	Offers video resultions not actually supported on Lucid Intel 865G - brcye investigatin
[16:08] <MootBot> LINK received:  http://people.canonical.com/~marjomercado/isotestingbugs.html
[16:08] <marjo> 556962	kernel BUG at /build/buildd/linux-2.6.32/drivers/gpu/drm/drm_fops.c:146! - jfo to triage
[16:09] <marjo> slangasek: that's it from QA team, unless there are questions
[16:10] <marjo> slangasek: thx
[16:11] <slangasek> marjo: what were the selection criteria for the 4 bugs you pasted?  there are several more bugs on the isotestingbugs page
[16:11] <marjo> slangasek: i just pointed out the "new" bugs
[16:11] <marjo> for emphasis
[16:12] <slangasek> ok
[16:13] <slangasek> no other questions here; anyone else?
[16:13] <slangasek> [TOPIC] Server Team
[16:13] <MootBot> New Topic:  Server Team
[16:14] <slangasek> marjo: thanks
[16:14] <slangasek> ttx: hi
[16:14] <ttx> o/
[16:14] <ttx> Updated team status at https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:14] <ttx> Bugs status:
[16:14] <ttx> Bugs targeted to release:
[16:14] <ttx> bug 563428 and bug 563434
[16:14] <ttx> This is about consistency in our cloud offering, will be fixed Monday at the latest
[16:15] <ttx> Other Lucid RC bugs :
[16:15] <ttx> bug 532733
[16:15] <ttx> lacking input from ogra and the reporter team
[16:15] <ttx> bug 513273
[16:15] <ttx> in progress
[16:16] <ogra> ttx, huh ?
[16:16] <ttx> https://bugs.launchpad.net/bugs/533029 -- new FFe review needed
[16:16] <ogra> i'm giving input the whole day
[16:16] <ttx> ogra: ah, recently ?
[16:16]  * ogra didnt do anything else but testing for that bug since he got up
[16:16] <ogra> yep
[16:16] <ttx> ah
[16:16] <ttx> sorry about that, I missed that
[16:16] <ogra> and i'm just done with the last combo of options
[16:16] <ttx> so it should msee movement now :)
[16:16] <ogra> doesnt fix anything
[16:17] <ttx> bug 552360 -- fix just committed
[16:17] <ttx> bug 563084 -- fix just committed
[16:17] <ttx> bug 563053 -- in progress, hopefully done today
[16:17] <pitti> ttx: I just reviewed that
[16:17] <ttx> the page also lists the identified lucid targets of opportunities
[16:17] <pitti> there are 4 remaining rdepends
[16:18] <pitti> two of which are mythtv, which I woudln't like to break without further coordination with superm
[16:18] <ttx> zul ^
[16:18] <ttx> On the specs side, a few work items left :
[16:18] <ttx> erver-lucid-uec-testing (31%) On track, not affected by freeze, mostly about testing RC and final milestones
[16:18] <zul> ttx: next on my list
[16:19] <ttx> server-lucid-apt-mirror-ec2 (0%) Blocked on IS (mirror deployment in progress), testing-only and not affected by freeze
[16:19] <ttx> server-lucid-puppet-uec-ec2-integration (44%) Hope to commit more testsuite fixes, remaining items are doc-only and not affected by freeze
[16:19] <ttx> RC Bugs affecting server, in other teams:
[16:19] <ttx> bug 559582
[16:20] <ttx> I think mvo is on top of this one
[16:20] <ttx> bug 563916 -- we'll probably releasenote it
[16:20] <ttx> which leaves bug 557429, that you put on the agenda
[16:21] <mvo> ttx: I think that is fixed now, may not be in the archive yet, haven't checked
[16:21] <slangasek> ttx: yes - can anyone on your team work on that, or does it need to be Foundations instead?
[16:21] <jdstrand> that one is possibly not as dire as it sounds
[16:21] <slangasek> jdstrand: oh?
[16:21] <ttx> slangasek: we kinda lost our last specialists recently, but if you're overworked, that's probably the one with the most overlap between our teams
[16:21] <jdstrand> at least the wording in release notes makes it seem a bigger failure
[16:22] <jdstrand> I reported that bug, so I get all the comments on it now
[16:22] <jdstrand> the issue is specifically that if you remove one disk, it comes up degraded (fine)
[16:22] <jdstrand> if you remove that disk, and add the other one, it comes up degraded (fine)
[16:22] <jdstrand> but if you add back the first, it comes up in sync
[16:22] <ttx> slangasek: I just doubt anyone in our team has sufficient expertise to fix mdadm
[16:23] <jdstrand> so you have two disks that were independently updated and removed, etc
[16:23] <jdstrand> there is obviously a bug, and it needs to be fixed, but it is probably not a common operation
[16:23] <ttx> jdstrand: is that a regression ?
[16:23] <jdstrand> (I don't have numbers to justify that statement)
[16:23] <jdstrand> ttx: actually, no
[16:24] <jdstrand> the guy who jumped on it and talked to updated linux-raid discovered it existed in karmic and earlier
[16:24] <jdstrand> s/updated/upstream/
[16:24] <ttx> ok, makes more sense to me
[16:24] <slangasek> jdstrand: not common, but as serious as I understood it to be...
[16:24] <cjwatson> we have very little mdadm expertise in foundations either, I fear
[16:24] <jdstrand> it just so happens that ext3 kinda scooted around it by happenstance
[16:24] <jdstrand> ext4 hits it though
[16:24] <slangasek> hmm? how is it filesystem-dependent?
[16:24] <ttx> cjwatson: yes, but you're overrall technically proficient :P
[16:24] <jdstrand> slangasek: oh, it is serious for sure-- total data loss
[16:25] <jdstrand> slangasek: it isn't technically fs independant-- there is something about ext3 that just by pure luck avoids it
[16:26] <slangasek> ttx: between the installer and plymouth/mountall, I think Foundations is quite busy until release; if someone on Server could take lead on this, I think that would be for the best
[16:26] <jdstrand> I don't have the details-- I'm not an mdadm expert-- I've just been following the bug
[16:26] <ttx> slangasek: ok, we'll do our best.
[16:26] <ttx> slangasek: I'll move it into our land at the top of that file
[16:27] <ttx> that's all for me
[16:27] <slangasek> ok, thanks
[16:27] <slangasek> anyone else have questions?
[16:28] <slangasek> [TOPIC] Mobile Team
[16:28] <MootBot> New Topic:  Mobile Team
[16:28] <slangasek> ttx: thanks
[16:28] <slangasek> asac: hi
[16:28] <asac> hi!
[16:28] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:28] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:28] <asac> so yeah. all specs done \o/ ... work item trackker is a bit lagging still
[16:29] <asac> already cleaned that up
[16:29] <asac> we uploaded openoffice with -marm and are hoping that that now works (we confirmed locally)
[16:29] <asac> main problem we are now facing is really just omap
[16:30] <asac> in particular "endless mountall+fsck loop on batteryless systems (e.g. beagle) see bug 563618"
[16:30] <asac> imx/dove are in great shape still ... so we are ready for release on that front
[16:30] <asac> besides a few RC bugs ;)
[16:31] <asac> we are waiting for archive to settle before we can try out potential workaround for "532733: qemu-kvm "apt/dpkg in qemu-system-arm hangs if a big task is installed" "
[16:31] <asac> maximus we havent found to investigate and are hoping for help on desktop team still
[16:31] <asac> bug 528887 and bug 522858
[16:32] <asac> and i am investigating our firefox rendering bug on armel my self (currently doing debug builds etc. ... that take a bit)
[16:32] <asac> bug 443147 that is
[16:32] <slangasek> I'm very unlikely to accept changes for 563618 in final - this code has flip-flopped far too many times for me to believe that someone is going to find a magic, regression-free solution to the problem in the next 2 weeks
[16:32] <asac> slangasek: hmm.
[16:32] <ogra> slangasek, i just posted a workaround this second :)
[16:32] <asac> slangasek: so in the bug there is a current workaround approach
[16:32] <asac> which does ugly stuff for BROKEN_CLOCK in initramfs ;)
[16:33] <asac> maybe check the bug
[16:33] <slangasek> if this is blocking validation of the OMAP images, I think ogra needs to hook up a battery as someone suggested on IRC
[16:33] <slangasek> ok, I'll take a look today, but I'm very hesitant to make changes here
[16:33] <ogra> slangasek, its not bugging me, i can edit fstab to not check
[16:33] <asac> ok. if you are aware of the current suggested approach and say no way, thats fine i guess
[16:33] <ogra> slangasek, it will bug all other users though
[16:34] <asac> right ... and we expect omap to be the first image that really gets good community
[16:34] <ogra> xactly
[16:34] <asac> so lets see if we can get the hacky workaround going. feels safe from what i see (if it works)
[16:34] <asac> but your say
[16:34] <ogra> indeed i can put up a wikipage that tells you how to edit /etc/fstab and /lib/init/fstab
[16:35] <asac> right. we probably can survive ;)
[16:35] <ogra> but danger is that people keep it that way and end up with corrupt filesystems
[16:35] <slangasek> asac: who have you reached out to for help on maximus?
[16:35] <asac> slangasek: desktop team through release meeting and didrocks directly
[16:35] <asac> i can poke harder
[16:36] <asac> or after firefox is fixed look on my own
[16:36] <pitti> right, this doesn't really sound like an arm specific problem, or is it?
[16:36] <pitti> (well, at least I never saw it myself)
[16:36] <asac> pitti: its not arm specific
[16:36] <slangasek> assigned the bugs to didrocks
[16:36] <pitti> right, I think he can help with this
[16:37] <asac> pitti: use the 2d launcher to see it ... if you dont have the bandwidth to help out on that it will fall back to us
[16:37] <pitti> we don't have so many RC bugs any more
[16:37] <asac> right. thats what i hoped ;)
[16:37] <pitti> asac: hm, I should try that again; last time I tried the 2d launcher it still crashed right away
[16:37] <asac> pitti: heh. that should work now. and all that dont have proper 3d get the 2d launcher now by default for netbook
[16:37] <asac> pitti: if you have problems let us know
[16:38] <asac> ... ok thats it from my side
[16:38] <asac> any questions?
[16:38] <ogra> just rip out your 3D chip from your netbook :)
[16:38] <slangasek> asac: no mention of bug #559301?
[16:38] <pitti> ogra: kvm! :-)
[16:38] <slangasek> oh, it's been marked invalid
[16:38] <asac> yes
[16:38] <slangasek> ok then
[16:38] <asac> thats what i found when preparing the report ;)
[16:38] <ogra> slangasek, no, you reviewed flash-kernel :)
[16:38] <asac> so i didnt want to raise that again ;)
[16:38] <ogra> slangasek, we dont fiddle with /boot anymore but use NAND
[16:39] <slangasek> no other questions here
[16:39] <asac> yay for NAND
[16:39] <slangasek> anyone else?
[16:39]  * ogra likes to note that omap might still show issues
[16:39] <ogra> while all pieces were tested separately there was no fully built image yet with the bits
[16:39] <asac> ogra: right. but they come as we go ;)
[16:40] <asac> no need to atlk about things that might happen ... even if we know that something is likely to happen ;)
[16:40] <ogra> if the buildds cope tonight should be the first one with all pieces in it
[16:40] <asac> right
[16:40] <ogra> just wanted to warn :)
[16:40] <asac> ok guess no other questions. thanks!
[16:41] <slangasek> [TOPIC] Kernel Team
[16:41] <MootBot> New Topic:  Kernel Team
[16:41] <slangasek> asac, ogra: thanks
[16:41] <apw> o/
[16:41] <slangasek> apw: hi
[16:41] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Most of the open work-items items are not release related at this time:
[16:41] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:41] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:41] <apw> On the items pulled out on the agenda, the configuration review just waits the delivery of the final configuration annoucenement which has been delayed due to workload.  Of the bugs, the first one we have patches and testing is looking good, given the timing it is proposed we shoot for an early SRU for that.  The second we do not yet have root cause so I have also pushed that to lucid-updates.
[16:41] <apw> We have had to break the kernel freeze to pull in some KMS blacklist patches for a trio if i8xx graphics driver which work much better with UMS, and also for some ATI Radeon based server which were booting to blank screens.  These kernels are building now.  All (5!) others are in and built.
[16:41] <apw> We have one other more serious issue with Dell systems which overheat, patches for this have been evolving and the latest look good.  Testing on problematic MacBooks is ongoing to confirm the fix.  As we do not yet have confirmation of the fix and the machine affected boot well enough to perform an update we are proposing to SRU that fix when its complete.

[16:42] <slangasek> apw: what's the bug number for the dell heat problem?
[16:42]  * apw finds
[16:43] <apw> bug #526354
[16:43] <pitti> hm, TBH I'd rather try to squeeze that into final if possible (and resonable wrt. regression potential)
[16:43] <pitti> people run live CDs, or don't upgrade right away, etc.
[16:43] <apw> pitti, it only occurs following a s/r as far as i can tell, it took me ages to realise thats what it was
[16:43] <pitti> ah
[16:44] <apw> obviously its release teams call, but i don't think we'll have non-regression confidence on this one till early next week
[16:44] <pitti> apw: we might disable s/r on those machines as a workaround if the kernel fix doesn't land in final, perhaps?
[16:44] <pitti> (pm-utils hook)
[16:44] <apw> this is the aborted fix which broke thinkpads and macbooks so i am reticent to break them all again
[16:45] <pitti> oh, I see :)
[16:45] <slangasek> pitti: can you take an action for the pm-utils hook?
[16:45] <apw> yeah thats not a bad idea, i am not 100% sure of all the models affected
[16:45] <pitti> slangasek: I'm happy to do that once I'm told which models to blacklist it on
[16:46] <apw> i know of at least 3 dells which are affected, we could start with those i guess
[16:46] <slangasek> [ACTION] pitti to investigate pm-utils hook for final to disable s/r on dells affected by bug #526354
[16:46] <MootBot> ACTION received:  pitti to investigate pm-utils hook for final to disable s/r on dells affected by bug #526354
[16:46] <slangasek> alright - anything else?
[16:46] <apw> notihgn here
[16:47] <slangasek> apw: how soon after release are you expecting the first SRU to hit?  there are definitely some Bugs Of Interest in the list
[16:47] <apw> normally we aim for 7 days after so scoop up as much as possible of the instant bugs
[16:48] <slangasek> ok
[16:48] <apw> if you have BOI that you think should be in there, make sure i am aware of the numbers
[16:48] <slangasek> apw: they're all targeted and milestoned to lucid-updates - I'm not tracking them more specifically than that
[16:48] <apw> i will start uploading ~preN kernels shortly to the kernel preproposed PPA as they accumulate
[16:48] <apw> slangasek, good enough thanks
[16:49] <slangasek> [TOPIC] Desktop Team
[16:49] <MootBot> New Topic:  Desktop Team
[16:49] <slangasek> apw: thanks
[16:49] <slangasek> pitti: hi
[16:49] <pitti> usual weekly summary and details about RC bugs are on
[16:49] <pitti> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:49] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:49] <pitti> just two WIs left for final, of which one does not affect the distro (Launchpad bug filing page update) and the other is to disable the "File a bug" menu entry, which is prepared, but should happen only before the release candidate
[16:49] <pitti> this week we got a great number of RC and non-RC bugs fixed; there are two uploads in unapproved which fix a couple of bugs which really ought to hit final for a good first-time ubuntuone installation, and for fixing a rather embarrassing CD detection problem
[16:49] <pitti> the remaining open RC bugs (5) are good SRU targets and do no break installation, so I'm relatively positive that we will get a good release at this point
[16:50] <pitti> (I had one "except that one", but it just got fixed in bzr by the Kubuntu guys,  thanks!)
[16:50] <pitti> so, I think we just earned two more from this meeting, I'll add them to our page in due course
[16:51] <Riddell> Kubuntu?
[16:51] <pitti> please
[16:51] <Riddell>  * daily's looking in decent shape for RC
[16:51] <Riddell>  * New logo in and everyone happy
[16:51] <Riddell>  * tinyurl.com/yjybcx9 milestoned bugs down to three (once Ubiquity uploaded)
[16:52] <Riddell> some ubiquity bugs needs more checking though
[16:52] <cjwatson> which ones?
[16:52] <Riddell> bug 538505 amichair has said he'll look into, but we can live with it
[16:52] <cjwatson> yeah, I agree with your assessment
[16:52] <Riddell> bug 538505 I couldn't recreate on virtualbox 538505
[16:52] <Riddell> I'll try it on real hardware later
[16:52] <cjwatson> 538505 538505 538505
[16:53] <cjwatson> sorry :)
[16:53] <Riddell> bug 563309
[16:53] <Riddell> that's the one
[16:53] <slangasek> Riddell: on kdesdk, there's also a recommends: on optipng, same problem - do you want to look at that Recommends as well and decide which way to go before I accept kdesdk, and save us some build time?
[16:53] <cjwatson> I guess that's one I can look at
[16:53] <cjwatson> bit of an art to debugging those state machine assertions
[16:54] <Riddell> and bug 528678 I need to check although installing in French worked fine last I tried
[16:54] <Riddell> slangasek: oh fooey, will do
[16:54] <Riddell> we have uploads of kdepim and kdebase-workspace outstanding
[16:55] <slangasek> pitti: the ubuntuone-client upload in unapproved unfortunately breaks string freeze, dpm has nacked it and I agree with him; do you have time yet today to follow up with Chipaca, to get that change dropped?
[16:55] <cjwatson> hmm, I thought 528678 had been fixed somewhere down the road, but I agree it's worth checking
[16:55] <pitti> slangasek: not myself any more, but I'll delegate it to Ken
[16:55] <pitti> (in fact I already talked to him)
[16:57] <slangasek> pitti: was more looking for the release team side of it; ok, I'll circle around with Chipaca and Ken
[16:57] <pitti> slangasek: ah; sorry, not today any more from me
[16:57] <pitti> I can have a look at the queue tomorrow morning, though
[16:58] <slangasek> hopefully we'll have it done before that :)
[16:58] <slangasek> Riddell: when do you expect those uploads to happen?
[16:58] <Riddell> slangasek: imminently
[16:58] <slangasek> ok
[16:59] <slangasek> no other questions from me; anyone else
[16:59] <slangasek> ?
[16:59] <slangasek> [TOPIC] DX Team
[16:59] <MootBot> New Topic:  DX Team
[17:00] <slangasek> pitti, Riddell: thanks
[17:00] <slangasek> davidbarth: hi
[17:00] <davidbarth> slangasek: hi
[17:00] <davidbarth> (i'm on a call at the same time, but here is the list of bugs on our list)
[17:00] <davidbarth> https://bugs.launchpad.net/ayatana/+milestone/ubuntu-10.04
[17:00] <slangasek> davidbarth: I had put bug #522858 to you, thinking this was something njpatel worked on; but I guess you're off the hook for that one :)
[17:00] <slangasek> [LINK] https://bugs.launchpad.net/ayatana/+milestone/ubuntu-10.04
[17:00] <MootBot> LINK received:  https://bugs.launchpad.net/ayatana/+milestone/ubuntu-10.04
[17:00] <davidbarth> yeah, i've seen this one
[17:01] <davidbarth> i don't have an answer yet, but i'll action it for sure between njpatel and DBO
[17:01] <davidbarth> apart from that, so ted has been working on fixing some dbusmenu issues
[17:01] <davidbarth> there is one that is still not fixed and uploaded, being:
[17:01] <davidbarth> #549096	Duplicate Broadcast Icons in Indicator Applet
[17:02] <davidbarth> but he's on it and hopes to have a fix for this one today
[17:02] <davidbarth> seb128 has just pointed out a crasher also, we're just adding id to our bug roster
[17:03] <slangasek> alright
[17:03] <davidbarth> the auto-mnemonics one will be for an sru, too involved and late at this stage (that's #548652	menu mouse-scrolling broken, when themes enable gtk-auto-mnemonics)
[17:03] <davidbarth> and last
[17:03] <davidbarth> we've noticed an issue with the kmail patch that doesn't work great with the gnome desktop
[17:04] <davidbarth> agateau is on this one since this afternoon and rushing to get a proper fix
[17:04] <davidbarth> that's it for DX
[17:04] <slangasek> ok, thanks
[17:04] <slangasek> anyone have questions?
[17:05] <slangasek> [TOPIC] Foundations Team
[17:05] <MootBot> New Topic:  Foundations Team
[17:05] <slangasek> davidbarth: thanks again
[17:05] <slangasek> cjwatson: hi
[17:05] <pitti> kmail> I suggested to back that out, BTW
[17:06] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:06] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:06] <cjwatson> Bug 534743 needs a patch from a dmraid expert (possibly psusi?); we have suitable people for the other bugs there
[17:06] <cjwatson> (discussing on #ubuntu-devel, too)
[17:06] <cjwatson> Other issues that have arisen:
[17:06] <cjwatson>  * grub2 menuentry quoting change broke both pygrub and os-prober; both of those have been fixed, but it raises the possibility that there may be other programs parsing grub.cfg wrongly (e.g. GRUB menu editors?).  Unfortunately attempting to use double quotes and escape things properly appears to break grub2 for reasons as yet unclear, so we may have to live with this and fix programs like menu editors in SRUs.
[17:06] <cjwatson>  * Design requested changes to the CD boot splash screen; I want to check some details of that with Mark before making the changes
[17:06] <cjwatson>  * Marjo raised a partitioning constraint handling bug that seems to be still hanging around: bug 558382
[17:06] <cjwatson>  * Bug 563117 isn't milestoned at present, but seems concerning if reproducible
[17:06] <cjwatson> Good news: oem-config/server appears to actually work now; we're out from under most of the pile of customer priority bugs
[17:06] <cjwatson> --
[17:07] <slangasek> 534743 already has a branch linked, is that one not adequate?
[17:07] <cjwatson> Scott objected to it in comment 4
[17:07] <cjwatson> I'm trying to find out whether that objection still stands
[17:07] <slangasek> ok
[17:07] <Keybuk> I'm not sure it does
[17:08] <Keybuk> why is bug #563117 on mountall ?!
[17:08] <cjwatson> "but practically speaking, dmraid disks don't have any circumstances where they emit a change event other than this, AFAICS"
[17:09] <cjwatson> so that may not be an issue
[17:09] <persia> Keybuk: Because alvin chose that package, and nobody has been able to figure out where it belongs yet.
[17:09] <Keybuk> persia: why is it a bug?
[17:09] <cjwatson> Keybuk: because kirkland muttered on #ubuntu-server that that was where he thought it lived
[17:09] <Keybuk> that seems like deliberate behaviour to me
[17:09] <cjwatson> I commented that it probably belonged somewhere else
[17:09] <cjwatson> /dev/mapper/ names should be stable, and they're more explanatory than UUIDs
[17:09] <persia> Keybuk: Renders systems unbootable with snapshots of system partitions because they share the same UUID
[17:09] <Keybuk> yes, but that then wouldn't allow you to move the filesystem *off* RAID to a normal disk
[17:09] <cjwatson> we've long taken the approach that we don't UUIDify names that are already stable
[17:09] <Keybuk> which we want to support
[17:10] <Keybuk> persia: lies.  only one emits the UUID in its event
[17:10] <cjwatson> if that change was intentionally made, it might have been nice if somebody had informed the installer team
[17:10] <Keybuk> cjwatson: we changed that approach in karmic iirc
[17:10] <cjwatson> meanwhile, I think that upgrades should be consistent with installs
[17:10] <Keybuk> I'm pretty sure you were in the BOF at the time ;)
[17:10] <persia> Keybuk: OK.  Alvin tested quite a bit.
[17:10] <cjwatson> I have absolutely no memory of this
[17:10] <cjwatson> it is entirely new to me
[17:11] <cjwatson> anyway, what's making the change on upgrade?  I couldn't find the operative code
[17:11] <cjwatson> there used to be stuff in volumeid or something years ago
[17:11] <Keybuk> do-release-upgrade isn't it?
[17:11] <cjwatson> oh, it's in update-manager itself
[17:11] <cjwatson> ?
[17:11] <Keybuk> I thought we moved that stuff there, yeah
[17:12] <cjwatson> nope
[17:12] <cjwatson> no matches
[17:12] <Keybuk> you're right that nothing calls blkid or vol_id in postinst anymore
[17:12] <cjwatson> it was apparently there at one point for upgrades to hardy
[17:12] <Keybuk> maybe the reporter is hallucinating
[17:13] <Keybuk> and their fstab never had /dev/mapper entries <g>
[17:13] <cjwatson> two hallucinations, persia reproduced it
[17:13] <slangasek> I was checking an LVM-using desktop I just upgraded here and found that it has UUIDs in fstab, but the fstab is 2 years old
[17:14] <cjwatson> for the record, I'm not going to change the installer for this now - can't afford the retesting time :-/
[17:14] <slangasek> so that doesn't count
[17:14] <slangasek> Keybuk: only one emits the UUID - ok, but which one?
[17:14] <Keybuk> slangasek: whichever one kees thinks should this week, usually
[17:14] <Keybuk> he's changed it at least three times ;-)
[17:15] <persia> Regarding relesae-criticality: there are two trivial workarounds: a) don't snapshot system filesystems, b) edit fstab
[17:15] <Keybuk> cjwatson: I've checked my changelogs, I *deleted* the fstab migration script ages ago
[17:15] <slangasek> Keybuk: sure; further evidence that the /dev/mapper names are the stable ones we should use...
[17:15] <Keybuk> so I'm not aware of it existing anywhere
[17:15] <Keybuk> slangasek: those are set by the same rules
[17:16] <slangasek> Keybuk: er, snapshots have unique lvm names, so that shouldn't be an issue
[17:16] <Keybuk> anyway
[17:16] <Keybuk> this is LVM :)
[17:16] <Keybuk> you can make it do whatever broken things you want <g>
[17:17] <slangasek> persia: if you were able to reproduce this, do you mind sending an upgrade log to the bug?
[17:18] <persia> slangasek: I hadn't considered a bug when I reproduced it (some time ago), and only ack'd it when alvin was testing and reported it.  I'll see if I can get my test laptop to recognise it's HD again, and reproduce there (my test server doesn't play with LVM well).
[17:18] <slangasek> ok
[17:19] <persia> (if anyone with better current HW availability wants to do this before me, I shan't complain)
[17:20] <slangasek> alright - anything else on Foundations?
[17:20] <slangasek> [TOPIC] Security team
[17:20] <MootBot> New Topic:  Security team
[17:20] <slangasek> cjwatson: thanks
[17:20] <slangasek> jdstrand: hi
[17:21] <jdstrand> hi!
[17:22] <jdstrand> as always https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:22] <jdstrand> nothing really new there, so I probably won't reference it again
[17:22] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:22] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:23] <jdstrand> I mentioned last week we'd be doing install audits. that didn't happen this week, but is planned for next
[17:23] <slangasek> ok
[17:23] <jdstrand> it seems bug #528274 stalled. I unmilestoned it-- it should probably be taken off the list
[17:23] <slangasek> ack
[17:24] <jdstrand> in other news, mvo disabled apparmor on hardy to lucid upgrades (but reenabled on reboot), to make sure that bugs in the Hardy with a new apparmor userspace and profiles won't affect the install
[17:24] <jdstrand> there was a bind9 bug that prompted this, but it is resolved now
[17:24] <jdstrand> (in update-manager)
[17:24] <jdstrand> Other than that, we are continuing to do bug fixing and make sure lucid is up to date on security updates.
[17:25] <ScottK> It's worth mentioning that yesterday was death day for clamav < 0.95 and I'm watching people in #clamav who run other distros scream and shout.  So far one Ubuntu user showed up and he'd kept the old clamd.conf by mistake.  Thanks for the security team's work on this.
[17:25] <jdstrand> we are going to go through our cve-tracker to make sure lucid is in excellent shape
[17:25] <slangasek> jdstrand: is it, or are you still in the process of making sure?
[17:26] <jdstrand> ScottK: well, we shoved it through with some testing, but thanks really should go to you (and cemc) for your testing and thoroughness on the upgrade process
[17:27] <ScottK> One Ubuntu bug to which the reply was "enable updates and upgrade."
[17:27] <ScottK> Thanks
[17:27] <jdstrand> slangasek: we are always triaging CVEs with up to date info, but we give a big push prior to release to make sure
[17:27] <slangasek> ok
[17:27] <jdstrand> slangasek: we are in the process of the big push
[17:27] <slangasek> sounds good
[17:27] <jdstrand> it is a little harder to keep up with the dev cycle since we don't see all the syncs and merges, etc
[17:28] <jdstrand> so our tracker can lag a bit at times
[17:28] <jdstrand> anyhoo, that is just a procedural thing our team does each cycle
[17:28]  * slangasek nods
[17:28] <slangasek> anything else for security?
[17:28] <jdstrand> and that is it for me, unless anyone has questions
[17:29] <slangasek> [TOPIC] MOTU
[17:29] <MootBot> New Topic:  MOTU
[17:29] <slangasek> jdstrand: thanks
[17:29] <jdstrand> ScottK: yeah, that was a funny bug :)
[17:29] <jdstrand> slangasek: sure! :)
[17:29] <ScottK> Hello.
[17:29] <slangasek> ScottK, sistpoty|work: hi
[17:29] <sistpoty|work> hi
[17:29] <ScottK> james_w get the NBS hero award.
[17:29] <ScottK> get/gets
[17:30] <ScottK> We're closing in on that.
[17:30] <slangasek> quite!
[17:30] <ScottK> I hope that main upload slow down at some point so the buildds can drain.
[17:31] <ScottK> sistpoty|work: Do you have anything to report?
[17:31] <ScottK> We need to keep up with FFe's, but I think things are in reasonable shape.
[17:31] <sistpoty|work> only that ghc6 made it on armel, and I keep the queue full with rebuilds of the haskell stack :)
[17:31] <pitti> the tetex NBS stuff is all removed now, too
[17:32] <pitti> the rest of NBS doesn't look that worrysome any more
[17:32] <sistpoty|work> others than that nothing from me
[17:32] <ScottK> We still need more push on FTBFS
[17:32] <sistpoty|work> s/rebuilds/give backs/
[17:34] <slangasek> ScottK: is lucas's build results page the active work list for FTBFS?
[17:34] <ScottK> slangasek: I think it's the best one to use.
[17:34] <ScottK> It will catch any that FTBFS due to removals.
[17:35]  * slangasek nods
[17:35] <slangasek> I still need to get the "freeze is on" mail out today, I'll include a pointer
[17:35] <ScottK> doko just delivered his list in #ubuntu-release and it's not as short as I'd hoped.
[17:36] <ScottK> We need a recipe for assessing those and trying to fix them.
[17:36] <slangasek> hmm, yes
[17:36] <slangasek> I'll follow up on that today as well
[17:37] <ScottK> Great.
[17:37] <slangasek> anything else before we adjourn?
[17:37] <ScottK> I don't think so.
[17:37] <slangasek> #endmeeting
[17:37] <MootBot> Meeting finished at 11:37.
[17:37] <slangasek> thanks, all!
[17:37] <pitti> thanks everyone
[17:37] <apw> slangasek, thanks