[14:05] <ttx> theorically it's the Java meeting time, but persia is not around
[14:07] <ttx> hah - no, it's in an hour.
[15:00] <persia> Who's here for the Java meeting?
[15:02] <elky_> ttx was before
[15:02] <ttx> o/
[15:02] <persia> It's that daylight savings time thing.  It just has to go.
[15:02] <persia> Anyone else?
[15:02] <elky_> no kidding
[15:03] <elky_> no, i'm just muttering away to myself here
[15:03] <persia> OK.  Nothing on the agenda.
[15:03] <persia> Jaunty is frozen, and no critical bugs identified for jaunty.
[15:04] <persia> slytherin and robilad aren't here
[15:04] <persia> Luddovicc isn't here
[15:04] <persia> I've no progress to report on the Java 5 front.
[15:04] <persia> ttx, Anything to report on Contents?
[15:05] <ttx> I generated the java-Contents.gz for Jaunty recently
[15:05] <ttx> and blogged about it
[15:05] <ttx> just playing with it to find examples for the blog post, I found some pretty obnoxious duplication
[15:06] <ttx> that we should try to fix in Karmic where possible
[15:06] <persia> Excellent.  That sounds like a useful goal.
[15:06] <persia> I suspect we'll generate a number of useful bugs for upstream out of that as well.
[15:07] <persia> Next up is attracting new Java packagers.
[15:07] <ttx> I'll try to run a Java packaging session for one of the Packaging Training sessions in May
[15:07] <dholbach> nhandler: ^ :)
[15:07] <persia> Do we have anything for next week?
[15:07] <ttx> I know dholbach has been looking for candidates :)
[15:08] <nhandler> That is great to hear ttx :)
[15:08] <ttx> dholbach: you highlight on "packaging" or "Training" ?
[15:08] <dholbach> ttx: just coincidence :)
[15:08] <nhandler> ttx:
[15:08] <nhandler> ttx: We are tracking sessions on https://wiki.ubuntu.com/Packaging/Training
[15:08]  * nhandler goes to update it for May
[15:09] <ttx> nhandler: I'll pick a date a try to stick to it
[15:10] <ttx> that's all from my side.
[15:10] <persia> Anyone have anything else?
[15:12] <persia> OK.  See you next week then.
[16:37]  * jtholmes is away: for about 3 hours
[22:01] <mcasadevall> #startmeeting
[22:01] <MootBot> Meeting started at 16:01. The chair is mcasadevall.
[22:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[22:01] <mcasadevall> argh
[22:01] <NCommander> We all here?
[22:01] <plars> yep
[22:02] <GrueMaster> In spirit.
[22:02] <NCommander> [topic] Action Item Review from 04/09/09
[22:02] <NCommander> ...
[22:02] <mcasadevall> [topic] Action Item Review from 04/09/09
[22:02] <MootBot> New Topic:  Action Item Review from 04/09/09
[22:02] <mcasadevall> damn it
[22:03] <mcasadevall> [topic] persia to investigate 338148
[22:03] <MootBot> New Topic:  persia to investigate 338148
[22:03] <persia> mcasadevall, I thought you said you were doing that last week.
[22:03] <persia> I haven't looked at it since.
[22:03] <mcasadevall> Oh, thats the VNC4 thing
[22:03] <mcasadevall> Oops
[22:03] <lool> Hey
[22:03] <mcasadevall> I assigned it to me, my mistake
[22:04] <mcasadevall> [action] NCommander to investigate 338148
[22:04] <MootBot> ACTION received:  NCommander to investigate 338148
[22:04] <mcasadevall> sidenote: no progress/ carry over on that
[22:04] <mcasadevall> [topic] persia to chase VFP for cairo ffmpeg and gtk+2.0
[22:04] <MootBot> New Topic:  persia to chase VFP for cairo ffmpeg and gtk+2.0
[22:05] <persia> ffmpeg and gtk2.0+ prepared, massively improved by lool, and uploaded.
[22:05] <persia> I got horribly stuck on cairo, and thought lool had taken it this week.
[22:05] <lool> cairo > I implemented it for Debian; it's in theory easy to merge in Ubuntu, but in practice I should redo it to have smaller changes
[22:06] <persia> lool, Do you expect that to be able to go post-RC?
[22:06] <lool> Unfortunately I didn't find the time; I'm not convinced the cairo changes are acceptable at this point
[22:06] <lool> persia: I chatted about it with slangasek, it was after the RC build were kicked off, but would I see the changes myself I would cry
[22:06] <lool> It's like a rewrite of rules currently
[22:06] <lool> Also, gtk+2.0 had an issue in the vfp flavor alone, and that's not encouraging
[22:06] <persia> Yeah, that's what I was finding, and it's not a simple rules file.
[22:07] <persia> What was the issue?
[22:07] <lool> Missing configure flags
[22:07] <lool> it was using the common configure flags instead of the same ones as for the shared flavor
[22:08] <lool> That caused xinput to go missing, which was quite subtle to miss
[22:08] <persia> RIght.
[22:08] <lool> So I'll try to push cairo if time allows; I'd like an ack from Debian too
[22:09] <lool> Anyway, mcasadevall > moving on
[22:09] <mcasadevall> [action] lool to continue investigation of cairo VFP
[22:09] <MootBot> ACTION received:  lool to continue investigation of cairo VFP
[22:09] <mcasadevall> [topic] lool to spec ec2-package-builder for jaunty+1
[22:09] <MootBot> New Topic:  lool to spec ec2-package-builder for jaunty+1
[22:09] <ogra> haha
[22:09] <mcasadevall> ogasawara, ?
[22:09] <lool> ogra: pff :)
[22:09] <ogra> as if lool would have time to write specs :)
[22:09] <lool> mc<TAB>
[22:10] <mcasadevall> argh
[22:10] <lool> carry<tab> over<tab>
[22:10] <lool> I feel like writing more specs before going in holidays   :-P
[22:10] <lool> Plus deadline approaches
[22:10] <mcasadevall> [topic] ogra to trim selection-of-arm-images to a smaller scope
[22:10] <persia> Remember the specs deadline is the 21st!
[22:10] <MootBot> New Topic:  ogra to trim selection-of-arm-images to a smaller scope
[22:10] <ogra> co ...
[22:10] <ogra> the other two as well
[22:11] <ogra> persia, oh, was it extended ?
[22:11] <ogra> cool
[22:11] <mcasadevall> [topic] GrueMaster to test newer version of Hildon Desktop to see if it resolves cat kills MID bug
[22:11] <MootBot> New Topic:  GrueMaster to test newer version of Hildon Desktop to see if it resolves cat kills MID bug
[22:11] <persia> ogra, Extended?  It's been the 21st since I sent the mail.
[22:11] <GrueMaster> Sorry, couldn't get it to run after rebuilding.  Constant segfaults.
[22:11] <mcasadevall> I'd like to add a sidenote on this one
[22:11] <StevenK> Sounds like an improvement to me
[22:11] <ogra> persia, last wee you said tuesday :P (indeed i assumed this tue)
[22:11] <GrueMaster> Will work on it some more this weekend.
[22:12] <mcasadevall> actually, forget the sidenote
[22:12]  * persia hands ogra a calendar
[22:12] <ogra> heh
[22:12] <mcasadevall> [topic] NCommander to coordinate with lool and re-purpose hardening-wrapper to pass -Os on lpia builds
[22:12] <MootBot> New Topic:  NCommander to coordinate with lool and re-purpose hardening-wrapper to pass -Os on lpia builds
[22:12]  * ogra does a happy dance ... 
[22:12] <mcasadevall> hardening-wrapper is now lpia-wrapper, and mostly done
[22:13] <lool> mcasadevall: Where is it?
[22:13] <mcasadevall> lool, in a PPA, still needs some work
[22:13] <lool> mcasadevall: Which one?
[22:13]  * lool checked yours already
[22:13] <mcasadevall> lool, the lpia compiler optimizations off my account
[22:13] <mcasadevall> lool, remember, we have multi-PPAs now :-)
[22:14] <lool> https://launchpad.net/~mcasadevall/+archive/ppa => I don't see it?
[22:14] <lool> Oh ok
[22:14] <mcasadevall> lool, ignore the build-essential package, thats just there to get builds to build with it by default.
[22:14] <lool> It's actually the fault of my own firefox keywords
[22:15] <lool> mcasadevall: What's the status?  Does it work alright?
[22:15] <mcasadevall> Talked with kees on how we want to handle the hardening-wrapper/lpia-wrapper conflict, and agreed to copy the hardening-wrapper functionality right into lpia-wrapper. Its a fugly solution, but without building a general framework (which is a spec I'm going to pick for karmic), we couldn't come up with anything better that didn't require predepends or horrid horrid abuses of stuff
[22:15] <mcasadevall> lool, works fine on -Os, I just need to add the other two flags. No obvious breakages yet, but I haven't stressed tested it to the point I'm fully happy (generally I'm going to toss it into a chroot then rebuild the base system and if that passes I'll feel its safe enough to toss in achroot)
[22:16] <lool> mcasadevall: is there a way to override this addition altogether?
[22:16] <mcasadevall> lool, yeah, you can turn it off via an environment variable, or via /etc/lpia-wrapper.conf
[22:16] <lool> glibc doesn't build with -Os for instance
[22:16] <lool> mcasadevall: ok; great; happy to pursue the other enhanements as specs then
[22:16] <lool> mcasadevall: Please hand it to IS via the ticket I mentionned
[22:16] <mcasadevall> lool, ATM, it auto-turns off for the kernel and -O0 which is part of hardening-wrapper's functionality
[22:17] <lool> Erg
[22:17] <lool> How does it detect kernel?  that's a bit scray
[22:17] <mcasadevall> lool, -D_KERNEL_
[22:17] <mcasadevall> Which is what hardening-wrapper also does
[22:18] <lool> Ok
[22:18] <mcasadevall> I'll nip this one in the bud tonight, because this weekend likely going to be a complete loss
[22:18] <mcasadevall> (long story there :-/)
[22:18]  * ogra twiddles thumbs watching the meeting turn into #ubuntu-hardening
[22:18] <mcasadevall> [topic] NCommander to test usplash at 800x600
[22:18] <MootBot> New Topic:  NCommander to test usplash at 800x600
[22:18] <ogra> any luck ?
[22:18] <mcasadevall> Didn't get to this, and because I'm kinda transitory this week with LCDs, someone else should take it
[22:19] <mcasadevall> else carry over
[22:19] <ogra> well, its unlikely to work, but given that i'll do more install tests before final i'll give it a try once
[22:19] <ogra> put it on my plate
[22:19] <mcasadevall> [action] ogra to test usplash at 800x600
[22:19] <MootBot> ACTION received:  ogra to test usplash at 800x600
[22:19] <mcasadevall> [topic] ogra nd NCOmmander to post backtraces of #328167 for upstream
[22:19] <MootBot> New Topic:  ogra nd NCOmmander to post backtraces of #328167 for upstream
[22:20] <ogra> havent gotten to that, but i saw you did :)
[22:20] <lool> Not sure what the default kvm res is, but it seems close to 800x600 and I saw usplash there
[22:20] <mcasadevall> I posted a full backtrace, writeup, and repeating instructions including our workaround, and the steps leading up to it
[22:20] <mcasadevall> I've also offered remote root to any developer who wants to try and fix this on my Babbage, no takers :-/
[22:20] <ogra> lool, its the hardcoded nature of the frambuffer itself ...
[22:20] <ogra> you cant vary much, i played a lot with fbset this week
[22:21] <mcasadevall> Well, usplash is supposed to work with /dev/fb0 or /dev/*whatever vesa uses*
[22:21] <lool> 640x480
[22:21] <mcasadevall> The former regressed at some point AFAIK
[22:21] <lool> AFAIK it hardcodes vesa usage nowadays
[22:21] <ogra> right, but it requires that this works at certain modelines which the driver doesnt match is my assumption
[22:21] <mcasadevall> lool, ewww
[22:22] <mcasadevall> Isn't usplash going away for karmic though?
[22:22] <lool> Should be replaced by plymouth, not sure whether it's karmic
[22:22] <mcasadevall> Ok
[22:22] <mcasadevall> [topic] Roadmap Review
[22:22] <MootBot> New Topic:  Roadmap Review
[22:22] <mcasadevall> [topic] offline-installer (ogra)
[22:22] <MootBot> New Topic:  offline-installer (ogra)
[22:23] <ogra> lool, i doubt plymouth can work on a babbage framebuffer
[22:23] <ogra> no progress on any of my specs
[22:23] <mcasadevall> [topic] mobile-setup-wizard (persia)
[22:23] <MootBot> New Topic:  mobile-setup-wizard (persia)
[22:23] <lool> ogra: It's KMS; KMS could very well work on fb
[22:23] <lool> Since it's all abstracted by the kernel
[22:23] <ogra> i thought it needs driver support
[22:24] <lool> ogra: it needs driver support in the kernel
[22:24] <ogra> right
[22:24] <ogra> and we have a driver that doesnt even support a different resolution
[22:24]  * mcasadevall pokes persia 
[22:25] <mcasadevall> ok then ...
[22:25]  * persia double checks before making a confident statement
[22:25] <mcasadevall> oh
[22:26] <persia> Works, except suffering from resolution issues.
[22:26] <mcasadevall> persia, should I leave it on the roadmap?
[22:27] <persia> mcasadevall, Please do: I do need to clean up a few more things before I remove it.
[22:27] <mcasadevall> Ok
[22:27] <mcasadevall> [topic] arm-library-optimization (lool)
[22:27] <MootBot> New Topic:  arm-library-optimization (lool)
[22:27] <ogra> done ?
[22:28] <lool> Hmm nothing to report anymore, we covered
[22:28] <lool> only cairo missing
[22:28] <lool> gtk fix pending after RC (now)
[22:28] <mcasadevall> Ok, I'll leave it on the roadmap
[22:28] <mcasadevall> [topic] poulsbo-packages (persia)
[22:28] <MootBot> New Topic:  poulsbo-packages (persia)
[22:29] <persia> Nothing to report
[22:29] <mcasadevall> [topic] arm-softboot-loader (persia)
[22:29] <MootBot> New Topic:  arm-softboot-loader (persia)
[22:29] <mcasadevall> er
[22:29] <mcasadevall> whoops
[22:29] <mcasadevall> [topic] arm-softboot-loader (NCommander)
[22:29] <MootBot> New Topic:  arm-softboot-loader (NCommander)
[22:30] <mcasadevall> Its on my TODO list as something to do this week, I think we want it for karmic. I've been following debian-arm, it looks like they're implementing something kexec based ont he slug to load larger kernels and initramfses
[22:30] <mcasadevall> Other than that, carry over
[22:31] <mcasadevall> [topic] lpia-versus-i386 (lool)
[22:31] <MootBot> New Topic:  lpia-versus-i386 (lool)
[22:31] <persia> Roadmap items are *automatically* carried over.
[22:32] <lool> That's on mcasadevall's plate ATM
[22:32] <lool> covered already
[22:32] <mcasadevall> [topic] mobile-spec-cleanup (persia)
[22:32] <MootBot> New Topic:  mobile-spec-cleanup (persia)
[22:33] <persia> Post-release.
[22:33] <mcasadevall> [topic] High-Priority Bugs
[22:33] <MootBot> New Topic:  High-Priority Bugs
[22:33] <mcasadevall> [topic] bug #338148: VNC4 FTBFS (NCommander)
[22:33] <MootBot> New Topic:  bug #338148: VNC4 FTBFS (NCommander)
[22:33] <mcasadevall> no progress
[22:33] <mcasadevall> [topic] bug #358762: update-initramfs is missing a trigger for flash-kernel (lool)
[22:33] <MootBot> New Topic:  bug #358762: update-initramfs is missing a trigger for flash-kernel (lool)
[22:34] <lool> That's fixed
[22:34] <mcasadevall> [topic] bug #337809 APIC error on CPU 0
[22:34] <MootBot> New Topic:  bug #337809 APIC error on CPU 0
[22:35] <persia> mcasadevall, hint: check the bugs first, skip the Fix Released ones, and reload the page before *every* topic, because someone will edit the page.
[22:35] <mcasadevall> I guess no progress on this one
[22:36] <GrueMaster> I still see this on my MID.
[22:36] <GrueMaster> Beyond that, no.
[22:36] <mcasadevall> Do we have any new high-priority bugs we want?
[22:36] <mcasadevall> such as the lpia alt network one?
[22:37] <mcasadevall> [topic] Low-priority bugs
[22:37] <lool> No need to track it, it's fix released
[22:37] <MootBot> New Topic:  Low-priority bugs
[22:37] <lool> Or fix committed + uploaded rather
[22:37] <mcasadevall> [topic] bug #299847: libipc-sharelite-perl FTBFS on armel
[22:37] <MootBot> New Topic:  bug #299847: libipc-sharelite-perl FTBFS on armel
[22:37] <mcasadevall> No progress, if/when we get new build hardware, I'm going to mark it Won't Fix if I can't reproduce it.
[22:38] <mcasadevall> Anyway, reminder, specifications are still needed for karmic
[22:38] <mcasadevall> [topic] Any other business
[22:39] <MootBot> New Topic:  Any other business
[22:39] <persia> Anyone have any questions about the process documented at https://wiki.ubuntu.com/MobileTeam/KarmicSpecifications ?
[22:39] <lool> And AR for this week => plars
[22:39] <persia> Also, please do submit things.  There's 25-30 slots that need to be filled.
[22:39] <plars> yes please
[22:40] <mcasadevall> persia, I just submitted another one, and I have another one to be added
[22:40] <persia> And anyone can submit things: you don't need to be a member of ~ubuntu-mobile (as long as it's about the stuff ~ubuntu-mobile does)
[22:41] <lool> Ok; done?
[22:41] <mcasadevall> [topic] Open Discussion
[22:41] <MootBot> New Topic:  Open Discussion
[22:41] <lool> Nothing from me
[22:42] <ogra> nothing here either
[22:42] <lool> Suddenly I realized my screen was quite filed up with temrs and thought I'd take a souvenir screenshot
[22:42] <lool> http://people.ubuntu.com/~lool/jaunty-rc.png
[22:42] <MootBot> LINK received:  http://people.ubuntu.com/~lool/jaunty-rc.png
[22:42] <mcasadevall> My ISP officially killed tiered bandwidth caps in Rochester, NY
[22:42] <mcasadevall> WOOOO!
[22:42] <mcasadevall> I don't have to move!
[22:42]  * persia bangs the specs drum more
[22:42] <ogra> time for 42" ?
[22:42] <lool> ogra: I have more workspaces ;)
[22:43]  * mcasadevall throws https://blueprints.launchpad.net/ubuntu/+spec/rebuilder-framework at persia 
[22:43] <ogra> but you cant see them
[22:43] <mcasadevall> lool, thats ... intense O_O;
[22:44] <lool> ogra: I should have taken a 12-workspaces large screenshot!
[22:44] <mcasadevall> lool, I dunno how you manage with that workspaces, I've seen you use that at UDS and it would hurt me (although I have though about using a tilted window manager, and I must say I do like those)
[22:45] <ogra> lool, yeah !
[22:45] <mcasadevall> Side note: I'm likely going to be MIA this weekend (need to drive back to NYC then back to Rochester)
[22:45] <lool> Oh right, I'm on VAC in 10 days for 2 weeks
[22:46] <mcasadevall> Anything else?
[22:46] <mcasadevall> Beside the lpia CD issue, anything worth noted on CD testing?
[22:47] <plars> iso tracker entries should be up (hopefully) today for lpia and armel
[22:47] <mcasadevall> Awesome
[22:47] <plars> but
[22:47] <plars> I know some people have done testing already
[22:47] <plars> and might have already put results under the arm entry that is out there under netboot
[22:47] <plars> which will probably be deleted since it is getting split up
[22:47] <plars> please check back and put in results again for the appropriate image if that applies to you
[22:48] <mcasadevall> The problem with the QA website is there is no admin interface, and to add a new thing requires DB editing (you need to add a product, then a test case, then links to instructions; its NOT straightforward)
[22:49]  * ogra pinged the release manage directly to report success for the babbage
[22:50] <mcasadevall> I think we can call this meeting to an end
[22:50] <mcasadevall> Going once
[22:50] <mcasadevall> Going twice
[22:51] <mcasadevall> Oh, right, I was wondering if we should add a New Specification Discussion for next meeting (which is the last meeting at the end of the jaunty cycle/first karmic meeting) to overview everything we want, need specs for or have been drafted
[22:51] <mcasadevall> Any yays, nays?
[22:52]  * mcasadevall shrugs
[22:52] <mcasadevall> #endmeeting
[22:52] <MootBot> Meeting finished at 16:52.
[22:54]  * cody-somerville falls over.