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