[00:00] <ubudog> thanks
[00:00] <Technoviking> Please get invloved in the loco, and get some of people from the forums to show support for you on your wiki or during the meeting
[00:00] <ubudog> all right
[00:00] <Technoviking> and please try back in a few month
[00:00] <ubudog> ok
[00:00] <pleia2> ozzie_: you here?
[00:00] <ozzie_> yes
[00:01] <pleia2> [TOPIC] ozzie_ membership
[00:01] <MootBot> New Topic:  ozzie_ membership
[00:01] <greg-g> please introduce yourself
[00:02] <ozzie_> My name is Ron McNeill and my URL is https://wiki.ubuntu.com/theozzlives
[00:03] <pleia2> ozzie_: what kind of projects is the Oklahoma LoCo up to?
[00:05] <ozzie_> I've been evangelizing Ubuntu since oct 2007 when I discovered it. Shareing my knowledge of this OS since Nov 2007. I encorage my schoolmates, friends, and customers to at least try the CD
[00:06] <ozzie_> I'm a member of the LoCo and am trying to whip OKC into shape
[00:06] <ozzie_> plea2 in OKC not much, I plan to change that
[00:07] <pleia2> that would be great
[00:07] <ozzie_> I've also been involved in Alpha testing since 8.10
[00:08] <greg-g> ozzie_: do you re-sell System76 laptops? I see an image from them on your business website.
[00:08] <ozzie_> My vision is to setup booths at the state fair and techno fairs
[00:09] <ozzie_> that was just to say I work on laptops
[00:10] <greg-g> ah, I see.
[00:10] <ozzie_> I do build Ubuntu machines
[00:11] <greg-g> ozzie_: I'd like to see a bit more involvement with the OKC loco in the future
[00:12] <pleia2> ozzie_: I'd really like to see you work more on getting OKC going, maybe host a few events, take some pictures :)
[00:12] <ozzie_> it is gonna happen
[00:12] <pleia2> and getting testimonals from folks you work with in the community would be great
[00:13] <greg-g> testimonials are really helpful
[00:13] <ozzie_> DuaneDesign was supposed to be here
[00:13] <pleia2> you can ask people to add their testimonals to your wiki page if they can't make the meeting
[00:14] <ozzie_> he said he'd be here
[00:15] <greg-g> Get a bit more involvement and some testimonials and I'd like to see you apply for membership in the future, ozzie_
[00:16] <greg-g> :(
[00:17] <greg-g> Thanks for coming everyone.
[00:17] <greg-g> And congrats to all the new members!
[00:17] <fader_> Thanks everyone :D
[00:17] <pleia2> congrats new members!
[00:17] <pleia2> #endmeeting
[00:17] <MootBot> Meeting finished at 18:17.
[00:17] <oubiwann> thanks, guys!
[00:17] <Technoviking> Yes, please come back in a few months with more work and testimonals and let us know how thing are joing with the OK loco
[00:18] <dmizer> thank you all very much.
[02:57] <Emzzzz> http://imggmi.info/DSC-1268362257.jpg/ do my tits look big?
[15:59] <pitti> o/
[15:59] <jiboumans> \o
[16:00] <slangasek> moin
[16:00] <Riddell> hi
[16:00] <slangasek> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is slangasek.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-12
[16:00] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-12
[16:00]  * Riddell may not be able to stay whole time but ScottK will be here too
[16:00]  * marjo waves
[16:01] <slangasek> [TOPIC] Actions from previous meetings
[16:01] <MootBot> New Topic:  Actions from previous meetings
[16:01] <slangasek>   * QA Team to retest Kubuntu desktop after ubiquity uploads
[16:01] <slangasek>   * slangasek to record server-lucid-ec2-ebsroot work items related to ISO testing integration
[16:01] <ScottK> o/
[16:01] <slangasek>   * ScottK, slangasek to review python sync/merge candidates ~Mar 12
[16:01] <slangasek>   * pitti to follow up on bug #520589
[16:01] <slangasek>   * slangasek to follow up on bug #517300 with asac/ogra
[16:01] <slangasek> my items are all still outstanding, I'm afraid
[16:01] <pitti> likewise-open> upstream replied, they'll incorporate our patch
[16:01] <ogra> slangasek, #517300 is taken by upstream now
[16:01] <marjo>  * QA Team to retest Kubuntu desktop after ubiquity uploads
[16:01] <marjo> Ara has put Ubiquity 2.1.35 in the pairwise tracker [1] to give it a go before the start of next week.
[16:01] <marjo> Next week we will be testing Lucid Beta 1 and it is very important that Ubiquity is in good shape before the release team starts posting candidate images in the ISO tracker.
[16:01] <marjo> If you have a VM machine and around 30 spare minutes, please, pick a
[16:01] <marjo> test case and help us having a promising Beta 1 release.
[16:01] <marjo> [1] http://pairwise.qa.ubuntu.com/
[16:01] <ogra> was a bit tricky to find the responsible person :)
[16:02] <slangasek> marjo: ok, great - has there been a call for testing as well?  looks like there's been one test result so far, for Ubuntu desktop instead of Kubuntu... :)
[16:02] <slangasek> ogra, pitti: ack, thanks!
[16:03] <marjo> yes, email went out
[16:03] <slangasek> pitti: have you looked at bug #520589?
[16:04] <pitti> slangasek: not personally, but chrisccoulson is on it now
[16:04] <slangasek> ok
[16:04] <fader_> pitti, slangasek: yesterday afternoon we think we might have discovered some interesting info about that bug
[16:04] <pitti> (delegation)
[16:04] <fader_> I'll make sure it's in the bug report if it isn't already
[16:04] <pitti> fader_: thanks, appreciated
[16:04] <pitti> chris also has an outstanding question with a test, which needs to be done
[16:04] <cr3> fader_: /etc/network/interfaces, right?
[16:05] <fader_> cr3: Correct; pitti: ^^ this is in the bug report already, from alexmoldovan
[16:05] <fader_> pitti: ack
[16:05] <cr3> fader_: this is strange though, because nm has always behaved that way as far as I know and the bug was reported by someone outside of certification
[16:08] <slangasek> [TOPIC] QA Team
[16:08] <MootBot> New Topic:  QA Team
[16:08] <marjo>  * Hardware testing
[16:08] <marjo> Automated Testing Results
[16:08] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:08] <marjo> Netbook:
[16:08] <marjo> passed: 12 (92%) failed: 1 (8%) untested: 0 (0%)
[16:09] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:09] <marjo> Laptop:
[16:09] <marjo> passed: 29 (100%) failed: 0 (0%) untested: 0 (0%)
[16:09] <marjo> Server:
[16:09] <marjo> passed: 57 (98%) failed: 0 (0%) untested: 1 (2%)
[16:09] <marjo> Desktop:
[16:09] <marjo> passed: 12 (100%) failed: 0 (0%) untested: 0 (0%)
[16:09] <marjo> Manual Testing Results
[16:09] <marjo> http://people.canonical.com/~fader/milestones/lucid/alpha3.html
[16:09] <MootBot> LINK received:  http://people.canonical.com/~fader/milestones/lucid/alpha3.html
[16:09] <marjo> 7 passed with no bugs
[16:09] <marjo> 12 failures, 7 of those are the networkmanager issue and now believed to be specific to test environment
[16:10] <marjo>  * alpha-3 test report
[16:10] <slangasek> bug #532983 - that looks new
[16:10] <marjo> #527828 | kubuntu oem-config 'No valid steps.'
[16:10] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:10] <marjo> #528346 | Impossible to select in wich disk install to (resize)
[16:10] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:10] <marjo> Won't be fixed for lucid, according to cjwatson
[16:10] <marjo> #528331 | [Lucid Kubuntu] Ubiquity crashes in PartMan.py when choosing manual partitioning and creating new partition - NameError: global name 'partman' is not defined
[16:10] <marjo> ubiquity (Ubuntu)                      | Undecided | New
[16:10] <marjo> #527972 | [Lucid Alpha 3] usb-creator.exe does not accept ISO selection on Windows XP system
[16:10] <marjo> usb-creator (Ubuntu)                   | Undecided | New
[16:10] <marjo> ev investigating
[16:10] <marjo> #527870 | karmic -> lucid CDROM only upgrade fails
[16:10] <marjo> libsdl1.2 (Ubuntu)                     | Undecided | New
[16:10] <marjo> update-manager (Ubuntu)                | Undecided | New
[16:10] <marjo> libsdl1.2 (Ubuntu Lucid)               | Undecided | New
[16:10] <cjwatson> (this is an example of iso-testing bugs including things that are in no way release-critical, BTW)
[16:10] <marjo> update-manager (Ubuntu Lucid)          | Undecided | New
[16:10] <marjo> mvo investigating
[16:12] <slangasek> yes, though we should have the ability to filter tho iso-testing bugs by severity, I think?
[16:12] <slangasek> (though, we should probably make sure we're *setting* the severity of these bugs, not leaving them as undecided)
[16:12] <cjwatson> marjo: hmm, I duped a couple of those bugs, maybe after you trawled them for your report
[16:12] <cjwatson> 527828 and 528331 have been fixed
[16:12] <marjo> slangasek: yes, that's the proper approach
[16:12] <marjo> cjwatson: thx!
[16:13] <marjo> cjwatson: yes, that's probably the case
[16:14] <marjo>  * Specs Status
[16:14] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:14] <marjo>  * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:14] <marjo> Work items lucid-beta-1: All WIs on track for beta-1
[16:14] <marjo> [cr3] Extract CPU- and I/O-data provided by bootchart: INPROGRESS
[16:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:14] <marjo> [cr3] Improve test reporting for boot times: INPROGRESS
[16:14] <davmor2> marjo, slangasek kubuntu 64bit didn't upgrade ubiquity
[16:14] <marjo>  * UbuntuSpec:qa-lucid-improve-server-testcases
[16:14] <marjo> Reassigned to hggdh2 from ara; all WIs on track for beta-1
[16:14] <marjo> Work items:
[16:14] <marjo> [hggdh2] Update samba test case in the ISO tracker: DONE
[16:14] <marjo> [hggdh2] Update Lamp test case in the ISO tracker: INPROGRESS
[16:14] <marjo> Determine which test cases are required for the ISO tracker: TODO
[16:14] <marjo> Write a new test case for a no-network interface install: TODO
[16:14] <marjo> Write a new test case for a non internet connection install: TODO
[16:14] <marjo> Write a new test case for a Kickseed install: TODO
[16:14] <marjo> Write a new test case for a repair system install: TODO
[16:14] <marjo>  * Bug:530380: checkbox writes to .cache/checkbox/submission before submission completes - fixed, but not released
[16:15] <marjo> slangasek: that's all from QA team
[16:15] <slangasek> marjo: on the hw testing, it seems that there are several failures with alpha 3 that aren't represented on the current report because the hardware hasn't been retested; do we need to look at those any more closely?
[16:15] <slangasek> three are marked "bugs to be filed", but I don't know the date of that comment
[16:15] <marjo> slangasek: yes; some testing is still in progress
[16:16] <fader_> slangasek: The comment is from yesterday, so we intend to get those filed today
[16:16] <marjo> so, we'll clean up accordingly
[16:16] <marjo> when all is done
[16:16] <slangasek> ok
[16:16] <slangasek> should bug #532983 and bug #531831 be targeted to lucid?
[16:17] <slangasek> er
[16:17] <slangasek> bug #538131
[16:17] <slangasek> and triaged to an importance other than "undecided"
[16:18] <slangasek> davmor2: to a first approximation, I would expect kubuntu+ubiquity to work the same on amd64 and i386; is someone working on testing i386?
[16:19] <davmor2> slangasek: pass bladernr_ are you?
[16:20] <fader_> slangasek: targeted; I'll make sure they get appropriate importances
[16:20] <Riddell> slangasek: kubuntu+ubiquity was tested yesterday, there's a couple of superficial but important issues to fix, otherwise works fine
[16:20] <bladernr_> slangasek:  I am
[16:20] <slangasek> fader_: and should they also be targeted to lucid?
[16:20] <slangasek> bladernr_: cheers
[16:20] <fader_> slangasek: Just targeted them
[16:20] <slangasek> Riddell: ah, ok - I went looking at the pairwise report yesterday, and people were still saying it didn't work, glad to have better results now :)
[16:21] <bladernr_> slangasek:  I was trying 64bit earlier, but the 64bit isos failed to build, so no new ubiquity.  32bit seems fine though so far.
[16:21] <cjwatson> we had a few "breaks the world" type bugs that generated lots of reports each
[16:21] <bladernr_> slangasek:  just finished re-syncing a moment ago so I'll be back on it in a few
[16:23] <slangasek> ok, that's it from me on QA as well - anyone else have questions?
[16:24] <marjo> slangasek: thx
[16:24] <slangasek> [TOPIC] Server Team
[16:24] <MootBot> New Topic:  Server Team
[16:24] <jiboumans> morning; i'm standing in for ttx today
[16:24] <jiboumans> Server team release status: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:24] <slangasek> marjo, fader_: thank you
[16:24] <slangasek> jiboumans: hello
[16:24] <jiboumans> Server blueprints with < 90% completion:
[16:24] <jiboumans> http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html
[16:24] <slangasek> [LINK]
[16:24] <jiboumans> * server-lucid-ec2-ebsroot 55% Remaining work is about automating release procedure
[16:24] <jiboumans> * server-lucid-eucalyptus-merging-and-packaging 57% On track, a couple beta1-targeted bugs left
[16:24] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html
[16:24] <jiboumans> * server-lucid-papercuts 66% On track (one WI per week)
[16:24] <MootBot> LINK received:
[16:24] <jiboumans> * server-lucid-uec-testing 80% On track. Most WI involve testing B1 candidate
[16:24] <jiboumans> * server-lucid-daily-vcs 85% on track
[16:24] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:24] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:25] <jiboumans> All work items on track; trend line looks higher due to targets of opportunity in the puppet spec; we're trying to get upstream to fix as many tests as possible.
[16:25] <jiboumans> FFe will be requested for:
[16:25] <jiboumans>   * Bug:519513: UEC upgrade from 9.10 karmic to Lucid fails
[16:25] <jiboumans>   * Bug:536829: package eucalyptus-cc 1.6.2-0ubuntu12 failed to install/upgrade:
[16:25] <jiboumans>   * Bug:534412: VNET_PRIVINTERFACE not set correctly in a multi-network install (kirkland)
[16:26] <jiboumans> The first 2 expect to be tackled in the next 2 weeks, where our focus is on Eucalyptus fixes
[16:26] <jiboumans> Critical bugs for server, all targeted beta1/critical:
[16:26] <jiboumans>   * Bug:527208: ec2 instance fails boot, no console output on c1.xlarge (Kernel)
[16:26] <jiboumans>   Pushed from Alpha3, to Beta1, now to Beta2
[16:26] <jiboumans>   * Bug:531494: upstart does not run cloud-init job (Foundations)
[16:26] <jiboumans>   Unassigned, retargeted to Beta2
[16:26] <jiboumans> I noticed some activity on the latter in the last half hour, but haven't been able to process that
[16:26] <ScottK> ~ server team related, I'm getting ready to upload clamav 0.96 rc1.  Just waiting on some final testing.  FFe is approved.
[16:27] <cjwatson> jiboumans: the activity was just to push it to beta-2, and nag for more information
[16:27] <jiboumans> cjwatson: ack; we'll get to it asap as it's a release blocker for us
[16:28] <jiboumans> the other being the kernel bug mentioned above for cloud images
[16:28] <jiboumans> slangasek: that's actually all for server team updates from us. Any questions?
[16:29] <slangasek> 519513 is targeted to beta-1, but you say it'll be tackled "in the next two weeks" - should the milestone be moved?
[16:29] <slangasek> likewise for 536829
[16:29] <jiboumans> slangasek: no, the target is beta1 still. Failing that we have an onsite eucalyptus sprint the week after, hence 'no later than 2 weeks from now'
[16:30] <jiboumans> that should only happen if we can't fix it without their direct help
[16:31] <slangasek> ok
[16:31] <slangasek> no other questions here; anyone else?
[16:31] <slangasek> [TOPIC] Mobile Team
[16:31] <MootBot> New Topic:  Mobile Team
[16:31] <slangasek> jiboumans: thanks
[16:31] <slangasek> asac: hi
[16:31] <ogra> https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:31] <ogra> http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html
[16:31] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html
[16:31]  * ogra heree for mobile today
[16:32] <ogra> so thumb2 proting is ongoing but in good progress
[16:32] <slangasek> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:32] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:32] <ogra> arm found a fix for the OO.o bug for us
[16:33] <ogra> the two specs that make the chart look bad should be implemented as soon as the FFe's and MIRs are fully processed
[16:33] <ogra> sadly no progress on the qemu issue, i'm still investigating there
[16:34] <slangasek> why is that one FFe bug marked "fix committed"?  that doesn't make sense...
[16:34] <ogra> we had some kernel regressions that are being sorted atm (suspend/resume on imx mostly)
[16:34]  * ogra checks ...
[16:34] <ogra> hmm, i have to ask asac for that
[16:35] <slangasek> what FFes are you waiting on other than the webservice ones (which are both approved)?
[16:35] <ogra> i think its referring to the needs-packaging
[16:35] <ogra> onle these
[16:35] <ogra> *only
[16:35] <slangasek> I don't see any "needs-packaging" on the reports?
[16:36] <ogra> someone added a tag to the description
[16:36] <ogra> [needs-packaging] [FFe] ubuntu-weboffice-zoho package for armel netbook
[16:36] <slangasek> ok
[16:36] <ogra> and asac set it to committed when the upload happened
[16:37] <slangasek> no upload has happened
[16:37] <slangasek> or else it was rejected..
[16:37] <ogra> hmm
[16:37] <ogra> i'll check that with JamieBennett and asac
[16:37] <ogra> i thought it was in NEW
[16:38] <ian_brasil> it is in REVU i thought
[16:38] <ogra> jamie said its been uploaded
[16:38] <slangasek> not to the archive, it hasn't
[16:38] <slangasek> setting back to confirmed, in the meantime
[16:38] <ogra> thanks
[16:38] <ogra> weird
[16:39] <ogra> anyway, images are in good state for beta
[16:39] <slangasek> 513734 is marked "fix committed", but it seems we now have two bugs about libmad with multiple patches pending?
[16:40] <ogra> both for armel ?
[16:40] <slangasek> yes
[16:41] <ogra> oh, yes, there is an ftbfs bug as well
[16:41] <ogra> i'll make sure tehy get merged
[16:41] <slangasek> well, someone also needs to make a call on which patch to apply :)
[16:41] <ogra> right
[16:41] <ogra> but that should happen on one bug :)
[16:42] <ogra> i didnt work on it but will make sure the right people discuss
[16:42] <slangasek> ok
[16:42] <ogra> well, i dont have anything else
[16:42] <slangasek> I'm available to sponsor uploads, if that would help Dave any - would've uploaded it already if I knew which patch to take
[16:43] <ogra> i'll tell him :)
[16:43] <ogra> (but i can sponsor as well indeed )
[16:43] <slangasek> bug #527720 isn't listed on https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid, but is targeted to beta-1 - on the radar?
[16:44] <cjwatson> if the mobile team thinks that's correct, I encourage them to just upload
[16:44] <ogra> oh, thats just an oversight, yes, its on our thumb list
[16:44] <cjwatson> I didn't feel qualified to review it when I was uploading klibc the other day
[16:45]  * slangasek nods
[16:45] <slangasek> no other questions from me; anything else no mobile?
[16:45] <ogra> https://edge.launchpad.net/ubuntu/+source/webservice-office-zoho btw
[16:46] <slangasek> s/no m/on m/
[16:46] <slangasek> ogra: ah, package renamed, tricky
[16:46] <slangasek> ogra: should that bug be closed, then?
[16:46] <ogra> just missing the MIR and seeding
[16:46] <slangasek> (ought to have been closed in the changelog, I would think)
[16:46] <ogra> i think the bug was also for the MIR status
[16:46] <ogra> as soon as its in main it will be closed
[16:47] <slangasek> there's no mention of MIR in that bug report, currently
[16:47] <slangasek> I guess someone has some follow up to do :)
[16:47] <ogra> heh, yeah
[16:47] <slangasek> [TOPIC] Kernel Team
[16:47] <MootBot> New Topic:  Kernel Team
[16:47] <slangasek> ogra: thanks
[16:47] <ogra> :)
[16:47] <slangasek> apw, ogasawara: hi
[16:47] <apw> hi
[16:48] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Beta-1 activity is summarised at the second URL below, with those item pushed out shown as At Risk.  The burndown chard for Beta-1 is at the third URL, and our burndown chart is at the fourth:
[16:48] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:48] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:48] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:48] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team-ubuntu-10.04-beta-1.html
[16:48] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:48] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:48] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team-ubuntu-10.04-beta-1.html
[16:48] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:48] <apw> Of the pushed out Alpha-3 items three have been postponed to M, two low priority items have been further pushed out to Beta-2, and two have patches in testing.  The remaining item is in progress and should hit first thing Beta-2.
[16:48] <apw> Of the Beta-1 items highlighted we are making reasonable progress most outstanding items are not release critical.  Two involve kernel changes and both of these are expect to be ready in time for the first upload of Beta-2 allowing testing before they hit they userbase.  Of the bugs called out, one is fixed in the kernels in the archive, one has a patch in testing, and one remains under investigation.
[16:48] <apw> All of the lucid kernels hit the Beta-1 freeze and still look good for release.  We have just recieved a TI OMAP kernel which is now going through FFe and MIR.  The drm 2.6.33 backport is included in these kernels and testing of this is looking good.  Test reports show a number of pending issues are resolved with no additional regressions.

[16:49] <pitti> apw: ah, I actually had a question about the TI kernel (in the MIR bug)
[16:49] <apw> pitti, sure.
[16:49] <pitti> apw: so is that one that we want to officially (LTS-)support? Tim made it sound a bit like a "demo"
[16:49] <apw> ahh yes, i'll get with rtg and get you an answer, thanks for the tickle
[16:49] <pitti> if we want to officially support it, then of course there's no question about the MIR
[16:49] <apw> we are erring to only supporting the non-core kernels for 18 months, but that needs to be codified
[16:50] <pitti> but ARM variants pile up, and I was unsure whether this should actually stay in universe
[16:50] <apw> pitti, ack ... i don't have an answer for you at this moemnt but yes we need a formal statement of what we support and for how long
[16:50] <slangasek> apw: which of those three bugs is fixed in the archive?  All three were showing as open last night when I prepared the agenda
[16:51] <ScottK> pitti: Unless there's community capability to maintain this I'm not aware of, I don't think it ought to be in Universe.
[16:51] <apw> and then we can use that as a basis for deciding where they go
[16:51] <pitti> ScottK: right, or partner or whatnot
[16:51] <pitti> but a 5 year security support commitment for a demo kernel sounds excessive
[16:51] <ScottK> pitti: Yes.
[16:51] <ScottK> pitti: I didn't think armel was LTS?
[16:51] <pitti> (note, I'm not saying it's a demo kernel -- that's what I want to find out about)
[16:52] <ScottK> Oh, that was mobile
[16:52] <apw> pitti, if its ok i'll take it off line and get you a formal response, but i think we intend to not LTS any of the armel, but use 18 month support for them
[16:52] <pitti> ScottK: oh, I don't know? apw?
[16:52] <slangasek> pitti: none of the ARM images are LTS-supported; though we would need the kernel package in main to build images for it at all (d-i build-dep)
[16:52] <pitti> apw: ok
[16:52] <apw> slangasek, that was what i thought, that CD == must be in main
[16:52] <pitti> alright, so sounds like the MIR is a no-brainer then
[16:53] <slangasek> apw: not CD generally, but a) that's how the *Ubuntu* CDs are built, b) kernels are special :)
[16:53] <apw> slangasek, the KVM bug is the one which is closed, the kernel in beta-1 has the patches out and so is 'fixed'
[16:53] <apw> we also know what the fix is so when the cve is reapplied it should not recur
[16:53] <slangasek> apw: btw, the "official" word on arm support is here: https://wiki.ubuntu.com/LucidLynx/ReleaseManifest
[16:54] <apw> slangasek, thanks
[16:54] <slangasek> (... except for the part where it's not yet updated to say netbook instead of desktop :P)
[16:55] <slangasek> no other questions here; anything else on kernel?
[16:55] <slangasek> [TOPIC] Desktop Team
[16:55] <MootBot> New Topic:  Desktop Team
[16:55] <slangasek> apw: thanks
[16:55] <slangasek> pitti: hi
[16:56] <pitti> https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:56] <pitti> == Beta-1 WIs ==
[16:56] <pitti> - Adding some missing settings to gdmsetup is a target of opportunity, and might slip to beta-2 or be dropped at all;
[16:56] <pitti> - Other specs are mostly done, just a few cleanup/polish things left on each
[16:56] <pitti> - desktop-lucid-startup-speed: all code changes from desktop team are in; remaining is a delay of the U1 daemon (target of opportunity, OLS team), and an improvement of netbook-launcher-efl (target of opportunity, mobile team, moved to beta-2)
[16:56] <pitti> - desktop-lucid-new-firefox-support-model: Remaining one for Beta-1 is to identify extensions to be kept in archive, not bound by beta-1 freeze
[16:56] <pitti> - lucid-duplicated-packages: What remains is dropping db4.7 and tcl8.4; moved to beta-2, and targets of opportunity; still needs some discussion whether it's worth it
[16:56] <pitti> - desktop-lucid-dx-integration: all code changes landed; what's left is test plan, better apport hook, and D-Bus API documentation
[16:57] <pitti> == Bug front ==
[16:57] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:57] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:57] <pitti> We did not get a lot of RC bugs fixed recently yet, there was still a lot of feature/integration/other bug fixes work to do.
[16:57] <pitti> e'll fully concentrate on bug fixing from now on (except for Bryce, who got tasked with yet another new feature from high above). Seb is currently selecting bugs which are not RC, but which we really want to fix for lucid to improve the experience.
[16:57] <pitti> imagine a "W" in front of the last sentence
[16:57] <pitti> [EOR]
[16:58] <pitti> oh, btw, there's a branch of Robert's for gdmsetup to allow you to disable the startup sound
[16:58] <pitti> that's one of the most wanted things
[16:58] <pitti> we'll get the FFE bug set up ASAP
[16:59] <slangasek> pitti: hmm, bug #518045 deferred - should I go ahead and take that one, if Bryce is busy?
[16:59] <slangasek> will be a fairly common blemish on people's upgrade testing, otherwise
[16:59] <pitti> slangasek: that would be highly appreciated, of course
[16:59] <ScottK> pitti: I'll be doing Kubuntu when you're ready ....
[16:59] <slangasek> taken
[16:59] <pitti> cheers
[17:00] <pitti> ScottK: I am from my side, unless more questions arise (but I can answer them later, too)
[17:00] <slangasek> pitti: I'm concerned about bug #512615
[17:00] <ScottK> The main concern for Kubuntu is the new branding.
[17:00] <ScottK> We're expecting drafts on Monday.
[17:00] <cjwatson> those won't be in the beta then ...
[17:01] <cjwatson> at least not entirely
[17:01] <slangasek> pitti: I haven't checked the status in a few days, but the last I knew was that a fix was possible today, but there was no guarantee it wouldn't be un-done later by an upstream update bumping the library prereqs
[17:01] <pitti> slangasek: due to how firefox needs to be packaged these days there's not a lot we can do about it unfortunately :(
[17:01] <ScottK> Made lots of progress on the installer this week and got KDE Firefox integration in.
[17:01] <ScottK> doko is looking at ia64 (qt4-x11 ICE).
[17:01] <ScottK> I think that's it.
[17:01] <pitti> ScottK: (we need to use the firefox-bundled cairo now)
[17:01] <slangasek> pitti: we could at least build against system cairo now, so that I don't go blind unnecessarily between now and release
[17:02] <pitti> slangasek: oh, does it look that bad for you?
[17:02] <Riddell> Couple of high priority if superficial issues for Ubiquity before beta 1, bug 538142 and bug 538147
[17:02] <slangasek> pitti: all my text is rainbow striped, it's horrible
[17:03] <jdstrand> slangasek: indeed
[17:03] <pitti> Riddell, ScottK: are you guys currently waiting on MIRs? there was a huge catch-up this week, but not sure we got everythign you are waiting for
[17:03] <pitti> slangasek: ok, I'll check that with asac/Chrsi
[17:03] <Riddell> pitti: yes I think we're good for those
[17:03] <pitti> Chris, too
[17:03] <cjwatson> Riddell: are those ones you and your team expect to be working on, or do you need us to take them?
[17:03] <cjwatson> I'm never quite sure what the expectations for Kubuntu installer bugs you file are
[17:03] <Riddell> cjwatson: I expect to work on them with shtylman
[17:03] <slangasek> I'm not exactly happy with the options, but in this case I would definitely say that I'd rather have the bug fixed now for release even if we know there's a risk we'll have to regress later
[17:04] <slangasek> (and anyway, we might find a better solution between now and release)
[17:04] <asac> back
[17:04] <cjwatson> Riddell: ok, thanks
[17:04] <asac> we should use the system cairo?
[17:04] <asac> hmm. lag
[17:04] <asac> so i guess i am not here
[17:05] <slangasek> asac: using the system cairo as long as we can would suppress this bug, at least...
[17:05] <cjwatson> asac: we see you
[17:05] <pitti> slangasek: right, discussing with the ff gurus
[17:05] <asac> oh ... ok lets hope connection doesnt go down
[17:05] <asac> slangasek: we cant go for system cairo
[17:05] <asac> unless you want us to roll out new upstream releases together with firefox security updates
[17:06] <slangasek> ScottK: who's responsible for the Kubuntu branding drafts, is there an action item there to make sure this is done in plenty of time for beta-2?
[17:06] <asac> we have to live with the font rendering bug or fix it (i assume thats the bug that triggered it)
[17:06] <ScottK> slangasek: The design team is working on them.
[17:06] <jdstrand> maybe we can use the system cairo to buy us some time and upstream can get/enable that patch
[17:06] <asac> jdstrand: buy us time?
[17:06] <ScottK> slangasek: I know Edubuntu has issues too.
[17:06] <slangasek> asac: if we hit a point where the system cairo is too old for the new firefox, then we switch to the bundled cairo and eat the regression <shrug>
[17:06] <asac> if we release with system-cairo its really scary to switch to in-source cairo in SRU/security
[17:07] <asac> whatever we go for we should have from the beginning
[17:07] <mdeslaur> why not just include the lcd-filtering patch?
[17:07] <jdstrand> asac: I thought I remembered that upstream was still deciding on what to do, and that the decision wouldn't be made in time for lucid. if we use system cairo until they figure that out, our users won't notice
[17:07] <asac> slangasek: right. we know abut the font rendering regression. but we dont know what other regressions
[17:07] <asac> switching to in-source cairo in stable updates really feels bad
[17:07] <jdstrand> rainbow fonts feel worse :P
[17:08] <slangasek> asac: "there might be other regressions" is mushy - there might be regressions *anyway* if we stick with bundled cairo
[17:08] <mdeslaur> asac, slangasek: why not just include the lcd-filtering patch? Is upstream _preventing_ us from including it?
[17:08] <pitti> hm, including our cairo patch into the ffox source sounds like an interesting option, too
[17:08] <slangasek> [ACTION] review status of branding for Kubuntu, Edubuntu next week
[17:08] <MootBot> ACTION received:  review status of branding for Kubuntu, Edubuntu next week
[17:08] <slangasek> mdeslaur: as in, applying the lcd-filtering patch to the bundled cairo?
[17:08] <asac> slangasek: upstream does quite thorough QA on it.
[17:08] <asac> they just dont see that they have a proper fix for the lcd cairo issue
[17:08] <asac> we can ask them to apply the patch
[17:09] <asac> in our distro, but they will say: "low quality"
[17:09] <mdeslaur> slangasek: it's what I've been doing...I've got firefox in my PPA with it
[17:09] <asac> becuse they didnt take it they dont want us to hav it
[17:09] <slangasek> asac: I don't consider their QA sufficiently thorough when it has this glaring defect on Ubuntu
[17:10] <asac> i agree with you in most points. just saying how it is and that we were forced to go this road because they bump requirements for stuff we used as system-libs in the past
[17:10] <slangasek> asac: "low quality" meaning what?  Does that jeopardize the trademark agreement?
[17:10] <slangasek> mdeslaur: sure, I know it's technically possible, but there are horrible issues surrounding the mozilla package and branding
[17:10] <asac> and dont allow us to unpatch ;)
[17:10] <asac> we can reopen this discussion with them again using this bug
[17:10] <asac> anywy, to move forward, how about checking if we can get the lcd patch in our repo?
[17:11] <asac> slangasek: yes
[17:11] <mdeslaur> slangasek: we could always rename it "FuzzyFox"
[17:11] <asac> trademark mostly, but also they generally believe that we shouldnt be on a different code base
[17:11] <asac> that they test
[17:11] <slangasek> mdeslaur: we could call it abrowser, or iceweasel, or any number of other things... it certainly wasn't *my* decision to kowtow to Mozilla on the trademark question :)
[17:11] <asac> especially wrt to sqlite etc. where we had problems in the past because we used system
[17:12] <jdstrand> asac: have they been discussing what to do or just kind of ignoring the issue?
[17:12] <slangasek> asac: can I give you an action to follow up with upstream, then?
[17:12] <asac> so its not that they are really wrong. for instance, there are sometimes performance boosts/drops of 20% or something with minor sqlite versions
[17:12] <jdstrand> iirc, it is an oldish bug
[17:12] <slangasek> asac: in this case, we have empirical evidence that they are wrong
[17:12] <jdstrand> (in their bug tracker)
[17:12] <asac> slangasek: ok
[17:12] <asac> slangasek: right, but one ;)
[17:12] <asac> they have plenty where our libs are bad ;)
[17:13] <slangasek> those aren't the libs we're proposing to use system versions of
[17:13] <asac> anyway, i have been fighting on this for years. and i dont see it improving
[17:13] <ScottK> jdstrand: fsvo of old.  I have bugs I filed in 2000 that are still open.
[17:13] <ScottK> (in that bug tracker)
[17:13] <asac> just want to make the packaging reflect that and "ship the stuff they claim to be so perfect"
[17:13] <slangasek> [ACTION] asac to talk to mozilla upstream about the need for system cairo in Ubuntu
[17:13] <MootBot> ACTION received:  asac to talk to mozilla upstream about the need for system cairo in Ubuntu
[17:13] <asac> and really hope keeping this bug not hidden will help
[17:14] <slangasek> well, I don't want stuff that Mozilla claims is perfect, I want stuff that doesn't make my eyes bleed
[17:14] <jdstrand> system cairo or filtering patch...
[17:14] <asac> yes. we will find a way ;)
[17:14] <pitti> (where the in-line filtering patch seems better FWIW)
[17:14] <asac> right. most likely we will go that road
[17:15] <slangasek> ok - anything else for Desktop? :)
[17:15] <jdstrand> it seems very close to what they would have blessed anyway
[17:15] <asac> ok thanks ... guess occupied enough time here ;)
[17:15] <pitti> thanks asac
[17:15] <slangasek> [TOPIC] DX Team
[17:15] <MootBot> New Topic:  DX Team
[17:15] <slangasek> pitti, ScottK, asac: thanks
[17:15] <davidbarth> slangasek: hi
[17:15] <slangasek> davidbarth: hi
[17:15] <davidbarth> so quickly: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus as usual
[17:16] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:16] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:16] <davidbarth> 2 bo still not 100% for the release; gtk is now 100% deferred
[17:16] <davidbarth> dx-lucid-application-indicator
[17:16] <davidbarth> 2 app ports remaining: hplip (497877) and vino (497883)
[17:16] <davidbarth> still working with upstreams to get the patches accepted; issue with hplip triggering a kde dependency
[17:17] <slangasek> bo->bp, I guess?
[17:17] <davidbarth> bp yes, sorry
[17:17] <davidbarth> and me-menu, still 2 targets of opportunities with about-me and the custom-dialog
[17:18] <davidbarth> this week i focused on fixing bugs like the avatar thing and some others
[17:18] <slangasek> "targets of opportunity" on the default desktop are probably not going to get in for beta-1; should these be bumped to beta-2?
[17:19] <davidbarth> yes, they won't go in beta-1
[17:19] <davidbarth> i'll carry them over, but now the team is mostly in bug fix mode
[17:19] <davidbarth> we've tightned the bug net with seb128 this week
[17:20] <davidbarth> other releases this week: see the wiki link for details of version numbers and all
[17:20] <davidbarth> Of note:
[17:20] <davidbarth> indicator-me-0.2.5-0ubuntu1: bug fixes, hide missing options, show avatar in menu, fixes 525951
[17:20] <davidbarth> indicator-session-0.2.5-0ubuntu2: left over from last week
[17:20] <davidbarth> indicator-sound-0.1.3-0ubuntu1: bug fixes + mute warning
[17:20] <davidbarth> notify-osd-0.9.27-0ubuntu1: bug fixes required for an upcoming nm-applet patch
[17:20] <davidbarth> we're working through the list of milestoned bugs
[17:21] <slangasek> sounds good
[17:21] <davidbarth> there have been a couple of UIF exceptions requested by sabdfl after a design review yesterday and today; we're preparing the bugs for that
[17:21] <slangasek> any questions on DX?
[17:21] <slangasek> ah
[17:21] <davidbarth> eh
[17:22] <slangasek> ok, will look for those bugs (with trepidation :)
[17:22] <davidbarth> 1 string change, and one rendering change
[17:22] <slangasek> ok
[17:22] <ScottK> Is DX the right team to track the artwork issues?
[17:22] <davidbarth> ScottK: not really
[17:22] <ScottK> OK.
[17:23] <davidbarth> ScottK: happy to help if we can; but the design team is really the one producing the material
[17:23] <ScottK> Do we have a design team rep that comes to the release meetings?
[17:23] <davidbarth> ScottK: agateau can be assigned to the integration if that helps, for example
[17:23] <ScottK> davidbarth: The current problem is not having the artwork.
[17:24] <davidbarth> ScottK: i'll try to help after the meeting
[17:24] <ScottK> davidbarth: OK.  For Kubuntu I know it's in progress.  Edubuntu, I don't know.
[17:24] <ScottK> Thanks
[17:26] <slangasek> anything else?
[17:26] <slangasek> [TOPIC] Foundations Team
[17:26] <MootBot> New Topic:  Foundations Team
[17:26] <slangasek> davidbarth: thanks
[17:27] <slangasek> cjwatson: hi
[17:27] <cjwatson> [LINK] http://people.canonical.com/~pitti/workitems/canonical-foundations-ubuntu-10.04-beta-1.html
[17:27] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-foundations-ubuntu-10.04-beta-1.html
[17:27] <cjwatson> (haven't had time to update the usual release status page this week, sorry!  this will be a QA-team-length paste ...)
[17:27] <cjwatson> == Work items ==
[17:27] <cjwatson> software-center ratings-and-reviews unfortunately postponed to lucid+1; we have 80%, but there are too many questions about the server side still outstanding
[17:27] <cjwatson> most work items either deferred to beta-2 or postponed entirely to lucid+1; exceptions are:
[17:27] <cjwatson>  * foundations-lucid-release-collaboration-with-debian: java/X (probably OK to defer these but we still need confirmation; I'm asking around)
[17:27] <cjwatson>  * foundations-lucid-pre-desktop-lucid-startup-speed: console-setup (patch sent for review today, so I think this is safe for beta-1)
[17:27] <cjwatson>  * foundations-lucid-supportable-binaries: most of it - postpone to beta-2?
[17:27] <cjwatson>  * foundations-lucid-computer-janitor: fixes pending review
[17:27] <cjwatson> == Bugs ==
[17:27] <cjwatson>  * Bug:531494: cloud-init job not running in eucalyptus without ramdisk
[17:27] <cjwatson>   - needs information from server team, as noted in bug
[17:27] <cjwatson>  * Bug:506297: Graphical Ubuntu logo enabled on servers, no more login prompt
[17:28] <cjwatson>   - fixes in ppa:scott/ppa, all bugs now believed fixed but undergoing testing
[17:28] <cjwatson>  * Bug:500198: casper-md5check needs to be ported to plymouth
[17:28] <cjwatson>  * Bug:506418: [lucid] live cd does not shutdown
[17:28] <cjwatson>   - both done today
[17:28] <cjwatson>  * Bug:432631: clean up system/per-user proxy handling
[17:28] <cjwatson>   - no progress; commented with a query about deferral
[17:28] <cjwatson>  * Bug:524439: console-setup: needs porting to udev/upstart
[17:28] <cjwatson>   - patch sent for review today, looking good
[17:28] <cjwatson>  * Bug:368060: Map of Kashmir when selecting the timezone is incorrect
[17:28] <cjwatson>   - nagged Ken about this recently, no answer yet
[17:28] <cjwatson>  * Bug:531697: ICE building qt4-x11 in IA64
[17:28] <cjwatson>   - assigned to doko who is investigating
[17:28] <cjwatson>  * Bug:529366: Regression: usb-creator-gtk doesn't work as of 0.2.16
[17:28] <cjwatson>   - pushed to beta-2; there's a separate bug which is allied to the parted change, so we may have some more investigation to do here
[17:28] <cjwatson>  * Bug:534293: libtommath ftbfs on all archs in lucid
[17:28] <cjwatson>   - assigned to me, will look ASAP
[17:28] <cjwatson>  * Bug:530632: Upgrading from 8.04 to 10.04 fails on update-initramfs
[17:28] <cjwatson>   - assigned to mvo
[17:28] <cjwatson>  * Bug:537262: does not terminate at computer shutdown
[17:28] <cjwatson>   - Scott reassigned this so I'm suspecting that it's not a sendsigs bug after all ...
[17:28] <cjwatson> == Other ==
[17:28] <cjwatson> I'm worried about DVD builds; while I kicked another attempt off during the meeting in the hope of having good news (I don't yet ...), we haven't had successful builds since January, and we're going to have to push to fix this
[17:29] <cjwatson> --
[17:29] <slangasek> foundations-lucid-supportable-binaries generally doesn't require any uploads, so if I can squeeze it in, I'll still be working on that for beta-1
[17:32] <slangasek> no other questions here - anyone else?
[17:32] <cjwatson> (also, Ken did answer about the Kashmir bug, he's on it)
[17:33] <cjwatson> I suspect the answer for DVD builds is "keep an eye on it over the weekend" for me :(
[17:33] <slangasek> I'll be doing the same, fwiw
[17:34] <slangasek> [TOPIC] Security Team
[17:34] <MootBot> New Topic:  Security Team
[17:34] <slangasek> cjwatson: thanks
[17:34] <slangasek> jdstrand: hi
[17:34] <jdstrand> o/
[17:34] <jdstrand> https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:35] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:35] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:35] <slangasek> (dear mootbot, https is also a URL)
[17:35] <jdstrand> once again, in terms of release, not much to report. we are on track
[17:36] <jdstrand> I won't be here next week, so someone from the security team can fill-in for me
[17:36] <slangasek> jdstrand: bug #528274 - keeping this on your team since I think you're the best ones to follow up with the ubuntuone folks on it as necessary
[17:37] <slangasek> jdstrand: but I also figure if kees isn't nagging them about it, I don't need to, so :)
[17:37] <jdstrand> slangasek: sure. kees submitted the profile, I reviewed the merge proposal. it is committed in their tree
[17:37] <slangasek> upload scheduled? :)
[17:37] <cjwatson> (DVD livefs build on i386 just succeeded!)
[17:37] <jdstrand> that I don't know, but I will follow up on it
[17:38] <slangasek> cjwatson: yaaaay
[17:38] <slangasek> jdstrand: ok
[17:38] <slangasek> anything else on security?
[17:38] <jdstrand> that's it from me
[17:38] <slangasek> [TOPIC] MOTU
[17:38] <MootBot> New Topic:  MOTU
[17:38] <slangasek> jdstrand: thanks
[17:38] <slangasek> ScottK, sistpoty|work: hello
[17:38] <jdstrand> sure :)
[17:38]  * sistpoty|work waves
[17:39] <ScottK> Hello.
[17:39] <ScottK> sistpoty|work: Why don't you go first.
[17:39] <sistpoty|work> haskell transition: good progress, however ghc6 doesn't build on armel (under investigation)
[17:39] <sistpoty|work> [LINK]: http://orangesquash.org.uk/~laney/haskell-installability/
[17:39] <MootBot> LINK received: : http://orangesquash.org.uk/~laney/haskell-installability/
[17:40] <sistpoty|work> ocaml transition: looks as if it's almost done (haven't tracked it too close though, to be honest)
[17:40] <ScottK> We also have a Ruby transition in progress.  Lucas is worried about getting it done in time.  A bunch of Ruby stuff just landed in binary New, so it'd be appreciated if that can get a quick review.
[17:40] <sistpoty|work> other business: ubuntu-release delegates: please comment on [LINK]: https://lists.ubuntu.com/archives/ubuntu-devel/2010-March/030376.html
[17:41] <sistpoty|work> that's it from my side
[17:41] <slangasek> ack, will comment today
[17:41] <sistpoty|work> thanks!
[17:41] <slangasek> jdstrand: you have time for binary NEW today?
[17:41] <slangasek> if not, I might have a look over the weekend
[17:42] <pitti> for the Debian syncs we don't generally check them a lot anyway
[17:42] <sistpoty|work> oh, I'd have a few requests for source-new that went through debian's new already, I've usually told that I'm ok if the requester can find an archive admin to do new, so... ;)
[17:42] <ScottK> I've been accepting Universe packages as they hit unaccepted.
[17:43] <slangasek> cjwatson: oh - is it time to point the IRC bot at the lucid queue?
[17:43] <cjwatson> probably - I can do that
[17:43] <slangasek> thanks
[17:44] <slangasek> anything else?
[17:45] <jdstrand> slangasek: yes
[17:45] <slangasek> I assume that's "yes" to binary new, not to AOB? :)
[17:45] <jdstrand> slangasek: I may not get to all of it, but it seems doable
[17:45] <slangasek> ok, cheers
[17:45] <slangasek> #endmeeting
[17:45] <MootBot> Meeting finished at 11:45.
[17:45] <slangasek> thanks, all
[17:46] <marjo> slangasek: thx!
[17:46] <Keybuk> cjwatson, slangasek: so I'm not really sure what to do with plymouth atm
[17:46] <pitti> thanks all
[17:46] <Keybuk> I keep testing it harder, and keep finding more bugs ;)
[17:47] <cjwatson> are they worse than the current bugs?
[17:47] <Keybuk> so I've still got ENTER-kills-X issues
[17:48] <Keybuk> and there appears to be an issue where everything's fine, except you end up on the wrong VT at the end of boot
[17:48] <Keybuk> the former seems to now only affect boots where plymouth had to use text.so
[17:48] <Keybuk> the latter appears to only affect boots where plymouth used the framebuffer renderer
[17:48] <Keybuk> I don't know of any bugs with the drm renderer (ie. intel, nouveau, radeon)
[17:50] <cjwatson> that sounds better than what we have now at least in terms of user count, but I haven't rebooted yet after upgrading from the PPA :)
[17:51] <Keybuk> the enter-killing-X issue is confusing me, because I realllly thought I'd eradicated all of those
[17:54] <Keybuk> I haven't really researched what bugs are open
[17:54] <Keybuk> and it doesn't seem worth closing them in an upload anyway, since everyone will just reopen them again
[17:55] <slangasek> I think the major bugs that are open are "autologin -> fail", "hit enter -> fail", "hit 2 -> fail", "boot w/o splash -> fail", "use nvidia -> fail"
[17:55] <Keybuk> "hit 2" ?!
[17:55] <slangasek> yes
[17:55] <Keybuk> as in the number 2 ?! :p
[17:55] <slangasek> I don't know why, it must be some magical sequence when in raw mode
[17:55] <slangasek> yes
[17:56] <Keybuk> one assumes so
[17:56] <Keybuk> there must be some console string that X just gets totally emo about and commits suicide
[17:56] <Keybuk> that happens to appear for both Enter and 2
[17:57] <slangasek> the enter could equally be that X is fighting getty for the console, and getty has respawned due to a failed login, no?
[17:57] <Keybuk> yes
[17:58] <Keybuk> though if X is on VT7, and Plymouth has reset VT7 back into raw mode again, Enter does also kill X then
[17:58] <slangasek> ok
[17:59] <Keybuk> of course, now I can't replicate this enter reoccurance
[18:10] <Keybuk> but I can now replicate silly vt1
[18:10] <Keybuk> meh
[18:15] <Keybuk> so anyway, yes, those two bugs
[18:15] <Keybuk> would you prefer I uploaded plymouth as it is in the PPA now, and then worked on these two bugs to "improve" matters
[18:16] <Keybuk> or wait until I've got something where people won't file the same bugs again
[18:16] <jcastro> Keybuk: I have a machine with this enter problem if you need me to test something
[18:16] <Keybuk> slangasek: ^ I guess it's your call ;)
[18:16] <Keybuk> jcastro: is your machine running plymouth from my PPA?
[18:16] <jcastro> no, stock lucid, want me to go update and try it?
[18:16] <Keybuk> jcastro: sure
[18:17] <jcastro> ubuntu-boot ppa or something else?
[18:17] <Keybuk> ppa:scott/ppa
[18:24] <jcastro> Keybuk: well, for sure it's happening less, I've tried it three times and hasn't done it yet.
[18:24] <jcastro> Keybuk: is there a time-window for triggering it? I am basically trying it right after I log in.
[18:26] <Keybuk> jcastro: depends, what type of graphics card do you have?
[18:26] <jcastro> it's an nvidia ION1
[18:27] <jcastro> which afaik is a version of the geforce 9400m
[18:28] <Keybuk> are you using nouveau or nvidia-glx
[18:28] <jcastro> nvidia-glx
[18:28] <Keybuk> ok
[18:28] <Keybuk> you're in the danger category for that one
[18:29] <Keybuk> I assume you saw my oh-so-funny text version of the splash screen?
[18:29] <jcastro> yeah I think it's clever. ;)
[18:29] <jcastro> however, I could get it to crash consistently before, now I'm on boot #5 and it hasn't done it yet.
[18:31] <Technoviking> jcastro: weird I have a 9400 and have not had that problem
[18:31] <slangasek> Keybuk: I'd prefer an upload now, even if it's only an incremental improvement
[18:32] <Keybuk> slangasek: gdm and mountall are already in the queue
[18:32] <Keybuk> just making the plymouth changelog a little more descriptive
[18:32] <jcastro> Technoviking: I have only read about people with the problem until I upgraded the machine to lucid
[18:38] <Technoviking> jcastro: I did a clean install, wonder if that made a difference