[04:25] <mboman> is it possible to try out UME in a VMware machine?
[07:13] <dholbach> good morning
[14:04] <lool> IRC meeting in 3 hours IIUC
[14:09] <smagoun> lool: davidm: has anyone on your team run into a problem with builds in the last day? One of our nightlies just failed, it looks like debconf-1.5.20 is broken and/or incompatible with MIC.
[14:10] <lool> smagoun: Did you hear about the libc breakage?
[14:10] <smagoun> lool: no, please do tell
[14:10] <dholbach> https://launchpad.net/bugs/201673
[14:10] <ubotu> Launchpad bug 201673 in glibc "Hardy: "invalid pointer: 0xb7ef4b70" no program will start." [Critical,Fix released] 
[14:10] <lool> smagoun: libc6 has a critical bug over night which triggerred crashes in many applications
[14:11] <smagoun> lool: that is unfortunate.
[14:11] <lool> smagoun: Check your log, if it mentions the broken version, it's likely to have broken your build
[14:11] <lool> smagoun: It is :)
[14:12] <smagoun> lool: my log is fairly useless, but rerunning by hand reveals the malloc error during install of debconf, so....looks like I'm in the same boat as everyone else
[14:13] <lool> smagoun: Upgrade libc6 in your chroot by dpkg-deb-ing on top of i
[14:13] <lool> it
[14:13] <lool> dpkg-deb -x libc6_blah.deb /srv/yourchroot
[14:13] <lool> It should fix the libc, then you can fix the chroot
[14:14] <lool> I think 2.7-9ubuntu2 is the fixed version
[14:14] <smagoun> lool: thanks. I'm just going to write off the broken build, it's not critical. This is why I like snapshots. :)
[14:14] <lool> smagoun: I think it's the first time ever Ubuntu breaks as badly
[14:15] <lool> I think some blog posts and mails went out to tell people how to fix broken systems
[14:15] <smagoun> lool: this may the first time ubuntu is broken this badly (and just before beta - who is in charge??), but it's hardly the first time I've been unable to create an image because of a problem in Ubuntu.
[15:36] <DarkRaven> ..
[16:08] <ouellettesr> Hello I wonder if someone can help me, I just installed the pakage ubuntu-mobile, but i cannot figure out how to start it
[16:14] <agoliveira> ouellettesr: A good way to start is read the faq: https://wiki.ubuntu.com/MobileAndEmbedded/FAQ and everything from above :)
[16:18] <ouellettesr> agoliveira, i should have expected an answer like that, i guess i should have clarified a bit. I read the faq and i am still a bit confused. do i have to create my own disk image or is there a way of starting it as an app from my current installation
[16:21] <AtomicPunk> ouellettesr: it has to be an image, I believe it's either Live CD or USB key, or installable CD or USB key
[16:21] <AtomicPunk> ubuntu-mobile is a whole platform
[16:21] <lool> smagoun: it might hard*l*y the first time that hardy is borken for debootstrap (SCNR)
[16:22] <agoliveira> ouellettesr: You can do both. In any case, you can use a device or run it from a chroot. Check out moblin-image-creator.
[16:22] <lool> smagoun: The reason it's quite grave is that it prevents you from upgrading (or even booting!) to fix it :)
[16:23] <ouellettesr> ok thanks everyone :)
[16:31] <lool> mjg59: Hmm did you push the hildon 2.0 updates to hardy or ppa?
[17:00] <sodarock_laptop2> Is there a meeting going on?
[17:00] <lool> #startmeeting
[17:00] <MootBot> Meeting started at 17:00. The chair is lool.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00] <praj-laptop> sodarock_laptop2: the meeting got pushed to 10. it should start now
[17:00] <lool> sodarock_laptop2: There is now :)
[17:00] <lool> Hi everybody, hope everybody is doing fine
[17:00] <rustyl_> morning all
[17:01] <tonyespy> KenKC: like this
[17:01] <lool> NB: amitk will be 5 minutes late
[17:01] <agoliveira> Hi all
[17:01] <lool> I'll chair the meeting this week as David is in another one
[17:01] <rustyl_> what was the URL for the wiki with the agenda?
[17:01] <tremolux> 'lo
[17:01] <lool> https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20080313
[17:02]  * agoliveira proposes that every action today should be given to amitk :)
[17:02] <lool> We'll start by reviewing last weeks action items
[17:02] <lool> [topic] patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted]
[17:02] <amitk> agoliveira: I'm back to thwart your sinister plans
[17:02] <MootBot> New Topic:  patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted] 
[17:02] <lool> I fear patm is going to be in the same call as DannyZ 
[17:02] <lool> err davidm
[17:02] <lool> sorry DannyZ 
[17:02] <agoliveira> Damn... 
[17:02] <lool> patm: Are you around?
[17:02] <patm> I am 
[17:02] <lool> Oh cool
[17:02] <patm> but with no boot chart
[17:02] <lool> Hmm
[17:03] <patm> Please carry forward, sorry
[17:03] <lool> patm: Should put this on someone else's shoulders?
[17:03] <patm> lool, no I will keep it, but we moved a deliverable to this week, so needs to be later
[17:03] <lool> [action] patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted] [cted]
[17:03] <MootBot> ACTION received:  patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted] [cted] 
[17:03] <lool> [topic] davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted]
[17:03] <MootBot> New Topic:  davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted] 
[17:04] <lool> davidm didn't manage to work on this last week; he said he would look over the WE
[17:04] <lool> agoliveira: I'll let you report directly:
[17:04] <agoliveira> Same here. Took more time than expected for Asac provide us with the examples we required and I had a very short week last week.
[17:05] <agoliveira> So, please, push it forward.
[17:05] <lool> I'm carrying on the action; it should be escalated if no progress is made next week as we're nearing the release of hardy and asac needs these
[17:05] <lool> [action] davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted] [cted]
[17:05] <MootBot> ACTION received:  davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted] [cted] 
[17:05] <lool> [topic] kyleN to prepare a mapping of hildon source packages to gettext domains, and list where the gettext domains are in maemo. [cted]
[17:05] <MootBot> New Topic:  kyleN to prepare a mapping of hildon source packages to gettext domains, and list where the gettext domains are in maemo. [cted] 
[17:05] <kyleN> since gettext domains can be set programmatically, there's no absolute way to derive all for a package programmatically. However, I wrote a python tool that gets 90% of the way for an arbitrary/editable set of packages
[17:06] <kyleN> I have a list of the gettext domains for hildon pkgs
[17:06] <lool> Cool; is it published somewhere?  Did you manage to output a mini-map?
[17:06] <kyleN> I have not had a chance to create a deb for it. this is a very busy week for us here...
[17:06] <lool> kyleN: "I have a list of the gettext domains for hildon pkgs" => which one?  the one telling which gettext domains they use or the one they provide?
[17:06] <kyleN> lool, i can email it to you if you are interested
[17:07] <lool> kyleN: Doesn't need to be packaged IMO
[17:07] <lool> kyleN: I think you should publish it on the wiki as an attachment to langpack research page
[17:07] <kyleN> the onees they use
[17:07] <lool> Where we identified this as a prereq
[17:07] <kyleN> I have not yet done the second half: mapping to upstream
[17:07] <lool> Ok; shall I carry on with this part only?
[17:07] <kyleN> yes
[17:08] <lool> [action] kyleN to attach his python script to list gettext domains in use in hildon modules on the langpack research page
[17:08] <MootBot> ACTION received:  kyleN to attach his python script to list gettext domains in use in hildon modules on the langpack research page 
[17:08] <kyleN> python script plus glade file
[17:08] <kyleN> and helper files
[17:08] <lool> [action] kyleN to enhance his python script looking into hildon modules to build a map of where the gettext templates are stored
[17:08] <MootBot> ACTION received:  kyleN to enhance his python script looking into hildon modules to build a map of where the gettext templates are stored 
[17:09] <lool> [topic] kyleN to look into hildon-help; what's is useful for and whether we should package it for UME
[17:09] <MootBot> New Topic:  kyleN to look into hildon-help; what's is useful for and whether we should package it for UME 
[17:09] <lool> kyleN: Tell us all about it!
[17:09] <kyleN> sorr - haven't had a chance to hit this one yet...
[17:09] <kyleN> please carry over
[17:09] <lool> Okay
[17:09] <lool> [action] kyleN to look into hildon-help; what's is useful for and whether we should package it for UME [cted]
[17:09] <MootBot> ACTION received:  kyleN to look into hildon-help; what's is useful for and whether we should package it for UME [cted] 
[17:10] <lool> [topic] lool review progress on Hildon 2.0 updates next week
[17:10] <MootBot> New Topic:  lool review progress on Hildon 2.0 updates next week 
[17:10] <lool> So, I'm supposed to be an example here, and *cough*, I only have hildon-control-panel ready but not even pushed to our bzr repo
[17:10] <lool> I finished pulling the update this afternoon and will push it after the meeting
[17:10] <bfiller> lool: no progress on my end, too busy with customer release, hopefully I'll have some time next week
[17:10] <lool> agoliveira missed the action item which was assigned to him when he was away (during last meeting)
[17:11] <lool> smagoun: did you manage?
[17:11] <smagoun> lool: no progress on my end, too busy with customer release, hopefully I'll have some time next week
[17:11] <lool> bspencer: Did Horace manage to do one or two?
[17:11] <lool> smagoun: You copy-pasted that!
[17:11] <lool> :)
[17:11] <smagoun> lool: yes. We have the same boss.
[17:11] <lool> mjg59: I think you did at least hildon-theme-layout-4 in bzr
[17:12] <lool> Which is the only one you had to do!  100%!
[17:12] <bspencer> lool:  I just got in and saw his email.  I haven't tried it out yet.  But he said he had done something
[17:12] <bspencer> lool: oh, sorry.  I am talking about something else.
[17:12] <bspencer> lool:  I don't know of his status for porting Hildon 2.0   I'll check 
[17:12] <lool> bspencer: Please check with him
[17:12] <lool> It looks like everybody was too busy to do all of it
[17:13] <lool> I personally took some notes of the steps I followed and will add them to the wiki page
[17:13] <lool> [link] https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2%2e0
[17:13] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2%2e0 
[17:13] <lool> I guess we'll have to carry over
[17:13] <lool> [action] lool review progress on Hildon 2.0 updates next week [cted]
[17:13] <MootBot> ACTION received:  lool review progress on Hildon 2.0 updates next week [cted] 
[17:13] <lool> [topic] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list
[17:13] <MootBot> New Topic:  sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list 
[17:14] <lool> Hmm where's sabotage and where's mawhalen?
[17:14] <lool> Anyone from Intel can comment on this or grab the relevant people?
[17:14] <bspencer> I'll get sabotage... I don't know about mawhalen.  Let's postpone this agenda item for 20mins
[17:14] <lool> Yes
[17:14] <lool> bspencer: Thanks
[17:15] <lool> [topic] ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys
[17:15] <MootBot> New Topic:  ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys 
[17:15] <lool> ToddBrandt: Did you have a change to work on enabling it?
[17:15] <lool> or ToddBrandtClone perhaps?
[17:15] <ToddBrandtClone> oh, oy, actually I haven't done that yet
[17:15] <lool> Hmm ok
[17:15] <ToddBrandtClone> I'll do that today, sorry
[17:15] <lool> Bad you
[17:16] <ToddBrandtClone> yea, I know, the bugs took priority
[17:16] <lool> Carrying to check about it next week
[17:16] <kyleN> please note that we are very intested in this as it appears necessary to get gtk theme switching working
[17:16] <lool> ToddBrandtClone: ack
[17:16] <lool> [action] ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys [cted]
[17:16] <MootBot> ACTION received:  ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys [cted] 
[17:16] <lool> [topic] rustyl (+ lool if necessary) document release process for Moblin modules
[17:16] <MootBot> New Topic:  rustyl (+ lool if necessary) document release process for Moblin modules 
[17:16]  * ToddBrandtClone hangs head in shame
[17:16] <lool> So AFAIK, this happened
[17:16] <lool> congrats to rustyl_ 
[17:16] <lool> He managed to do tarball releases of almost all moblin projects I think
[17:16] <lool> rustyl_: kudos to you!
[17:17] <rustyl_> k
[17:17] <lool> rustyl_: I personally had in mind that there would be some kind of process document on moblin.org for module maintainers, but perhaps you have an internal one, to release subsequent tarballs?
[17:17] <rustyl_> we are working on a presentation
[17:17] <bfiller> lool: are there plans to incorporate CDBS into debian/rules so we can make patches?
[17:18] <rustyl_> it just isn't ready yet
[17:18] <lool> bfiller: Yes; I think we'll discuss this in "(lool) Rebasing on the Moblin released tarballs"
[17:18] <lool> bfiller: Just after that
[17:18] <bfiller> lool: thanks
[17:19] <lool> rustyl_: Ok; well thanks for the efforts; I'm around to help you succeed in defining/documenting the process
[17:19] <lool> rustyl_: I'd also like to talk to moving to these new tarballs now, but I made this a separate topic
[17:19] <rustyl_> yea, this needs some discussion
[17:19] <lool> Moving on to current items for today's meeting
[17:19] <lool> Hmm I'll flip two because one is easier
[17:20] <lool> [topic] (lool) Launchpad bugs, ubuntu-mobile subscription, and ume tag
[17:20] <MootBot> New Topic:  (lool) Launchpad bugs, ubuntu-mobile subscription, and ume tag 
[17:20] <lool> EVERYBODY (that's you) please add the ume tag to LP bugs which concern UME
[17:20] <lool> And subscribe the ubuntu-mobile LP team to them
[17:20] <rustyl_> lool, is there a way to apply a tag to a collection of bugs?
[17:20] <lool> This is to help everybody keep track of important bugs we have to follow for UME and derived projects
[17:21] <lool> rustyl_: Excellent question, I think not
[17:21] <rustyl_> or do you have to go through each and every bug
[17:21] <rustyl_> darn
[17:21] <lool> rustyl_: This would seem to suck
[17:21] <lool> rustyl_: You might be able to set it via email though
[17:21]  * rustyl_ looks to see if his moblin-media bugs are tagged already
[17:22] <lool> rustyl_: We have some hacked up python bindings to deal with bug reports though
[17:22] <lool> rustyl_: Perhaps you can use these to do as you desire?
[17:22] <lool> rustyl_: "python-launchpad-bugs"
[17:22]  * sabotage hears his name being taken in vain
[17:22] <rustyl_> i'll read about it
[17:23] <lool> rustyl_: But please file a feature request if you can't find the tagging feature you're looking for
[17:23] <rustyl_> ok
[17:23] <lool> rustyl_: You'd have to file it against "malone", that's the launchpad bug tracker
[17:23] <lool> sabotage: Thanks for coming; I'll reopen your topic now then
[17:23] <lool> So please everybody tag and subscribe!
[17:23] <lool> And file bugs, don't discuss issues via email or IRC :)
[17:24] <lool> [topic] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list
[17:24] <MootBot> New Topic:  sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list 
[17:24] <lool> sabotage: Tears flows on my face: no themes tools guide this week?
[17:24] <bspencer> s/don't discuss issues via email or IRC/don't discuss issues JUST via email or IRC
[17:24] <lool> bspencer: Right
[17:24] <lool> Mention the bug in your email :)
[17:24] <sabotage> ok, so I dropped the ball this week, but I've identified the wiki that I will be publishing it in
[17:25] <lool> sabotage: Do you need any help to publish the guide?
[17:25] <sabotage> can you make days longer?
[17:25] <lool> And your thoughts on implementation options?
[17:25] <lool> sabotage: I can keep you up longer before you're allowed to sleep :)
[17:26] <sabotage> honestly, I've been completely swamped with another project, so I just need to kick it out for visibility
[17:26]  * sabotage was up till 1:30am last night as it is
[17:26] <lool> sabotage: Please try to push this out this week -- even a draft
[17:26] <sabotage> yep, ball is already rolling
[17:26] <lool> Cool
[17:26] <lool> [action] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list [cted]
[17:26] <MootBot> ACTION received:  sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list [cted] 
[17:27] <sabotage> is HappyCamp on?
[17:27] <lool> Resuming on next item to discuss
[17:27] <lool> [topic] (lool) Rebasing on the Moblin released tarballs
[17:27] <MootBot> New Topic:  (lool) Rebasing on the Moblin released tarballs 
[17:27] <bspencer> sodarock
[17:27] <sabotage> HappyCamp, HappyCamp_ubuntu  need you to read my email and set me up
[17:27] <lool> So, we have these cool Moblin tarballs
[17:27] <sabotage> this will get the theme guide moving
[17:27] <lool> We should move to using them
[17:28] <lool> rustyl_: I'm not sure I made this clear enough, but one thing which we want to keep is Intel publishing its releases all the way down to the ppa
[17:28] <rustyl_> lool, i understand
[17:28] <lool> But the transition frmo the current mode to the mode where we use tarballs needs a little extra efforts
[17:28] <bspencer> rustyl_: lool:   how does that work again, with ubuntu adding patches on their own?
[17:28] <lool> It's similar in spirit to the Hildon 2.0 modules transition
[17:28] <rustyl_> and there is confusion on our end
[17:29]  * bspencer confesses a bit of confusion :)
[17:29] <lool> bspencer: The idea is that we put patches in debian/patches; when a new upstream release comes out and you push it to the ppa, you drop the debian/patches which have been merged upstream and port the other ones
[17:29] <lool> rustyl_: Where is the confusion?
[17:29] <bspencer> lool:  ok.  I understand.  I missed that patches change
[17:30] <lool> This will make the Ubuntu/ppa specific changes into separate patches, and easy to rebase on the next release
[17:31] <rustyl_> lool, If you gave everyone a written test that made them explain exactly what commands/steps you need to do go from "i have a new tarball release" to "i am now calling dput to push to the ppa", i'm afraid most intel people would fail the test
[17:31] <ToddBrandtClone> Do each of the project owners need to upload their source to the hardy ppa for each release still or has this been streamlined
[17:31] <lool> rustyl_: Ok, the cool thing is that it's going to be very easy
[17:31]  * ToddBrandtClone Todd trumps bspencer's confusion
[17:31] <lool> Once we get it done *once*
[17:31] <lool> Subsequent updates are going to be easy
[17:31] <GrueMaster> i fail.
[17:32] <lool> ToddBrandtClone: We would like project owners to please continue doing so
[17:32] <ToddBrandtClone> lool: ok, our source repo layout has changed so I guess I have some more questions for rusty
[17:32] <lool> It's so damn easy that it's basically: dget -x the current ppa source, uupdate with the new tarball, update the packaging and patches, upload
[17:32] <ToddBrandtClone> rusty_: do we have a HARDY branch now in addition to GASTON?
[17:32] <rustyl_> ToddBrandt, the packaging for hardy is not in the source repository
[17:33] <rustyl_> ToddBrandt, that hardy branch is now defunct 
[17:33] <ToddBrandtClone> rustyl_: yea but we still haev to use the debian tools to create the source package, which require the debian dir, which is no longer in master
[17:33] <lool> ToddBrandtClone: Exactly, that dir you retrieve from the ppa each time you plan an upload
[17:33] <lool> ToddBrandtClone: It might have been updated by other folks, for example me
[17:33] <ToddBrandtClone> ahhh
[17:34] <ToddBrandtClone> the missing piece, I'm learning, gotcha
[17:34] <rustyl_> yeap, that's the idea
[17:34] <lool> If you prefer, instead of "uupdate" you simply "copy over the debian/"; it should end up being the same
[17:34] <ToddBrandtClone> k, thx
[17:34] <lool> This is the *target* process
[17:34] <lool> Before this, we need to add support for debian/patches/ in each package
[17:35] <lool> mjg59 did it in hildon-theme-layout-4
[17:35] <ToddBrandtClone> ok, so until then we create the hardy packages like before
[17:35] <lool>   * Add simple-patchsys from CDBS
[17:35] <lool>   * Build-depend on CDBS
[17:35] <lool> That's his changelog entry
[17:35] <lool> What we did in debian/rules:
[17:35] <lool> - he added:
[17:35] <lool> include /usr/share/cdbs/1/rules/simple-patchsys.mk
[17:35] <rustyl_> we several things on moblin that need to do a new release, so we have some projects to try to run through the new process
[17:35] <lool> - he changed the dependencies of the targets to apply/unapply the patches:
[17:36] <lool> build: apply-patches build-stamp
[17:36] <lool> This means applying the patches is a prereq for the build
[17:36] <lool> You might have to rename clean: to clean:: as simple-patchsys.mk defines it as well
[17:36] <lool> This is all it takes to add debian/patches support
[17:36]  * agoliveira is happy that the word "quilt" didn't make into this conversation so far :)
[17:37] <lool> The other thing to do is to compare the Ubuntu ppa tree to the moblin release it claims to base on to see which changes were done since this moblin release
[17:37] <bfiller> lool: do moblin folks take the patches in debian/patches and incorporate them into the source and remove the patches?
[17:37] <lool> These changes should be converted to debian/patches/*.patch files
[17:38] <lool> bfiller: The person authoring the patch should take care to send it to moblin folks
[17:38] <rustyl_> bfiller, i think incorporating existing packages before making a release is a good goal
[17:38] <lool> Moblin folks are naturally welcome to look from time to time if there would be interesting patches which failed the upstreaming process
[17:38] <lool> Does anybody has any question on how it will work and what remains to be done?
[17:39] <rustyl_> it makes a nice way to send a patch.... send an email to the maintainer with moblin devel list cc'ed, and at the same time upload the patch to the ppa
[17:39] <bfiller> lool: so if I had a patch, I would put the patch in debian/patches, upload to the ppa and also send the patch to moblin?
[17:39] <lool> Perhaps we should file a bug instead of mailing the maintainer?
[17:39] <lool> rustyl_: Would that work for you?
[17:39] <ToddBrandtClone> I vote for mailing the maintainer, that info would be very useful
[17:40] <lool> bfiller: Perhaps opening a bug is more logical than using email
[17:40] <lool> ToddBrandtClone: Doesn't the maintainer get an email for new bugs?
[17:40] <rustyl_> yes, filling a bug is good
[17:40] <rustyl_> the maintainer will get the mail via launchpad
[17:40] <davidm>  Can do both but filing a bug is important,  and has been requested by Don Johnson.
[17:40] <ToddBrandtClone> ok
[17:40] <davidm> Need tracking
[17:40] <rustyl_> but we need to cc the devel list for potential discussion on the patch
[17:41] <lool> rustyl_: I think that's a logical escalation when a bug fix isn't consensual indeed
[17:41] <lool> (or any change, not necessarily a bug fix)
[17:42] <lool> Should I document what we just discussed on a wiki page? (how tarball releases work down to the ppa and how patches are added+sent back)?
[17:42] <davidm> lool, yes please
[17:42] <ToddBrandtClone> yes
[17:42] <rustyl_> yes
[17:42] <cwong1> +1
[17:43] <lool> [action] lool to document tarball release + ppa upload process and patch addition + submission process
[17:43] <MootBot> ACTION received:  lool to document tarball release + ppa upload process and patch addition + submission process 
[17:43] <davidm> Just out of the other meeting, sorry I'm late.
[17:43] <lool> Ok; last thing to discuss on the topic is who is going to do the work to conver the ppa packages to the layout
[17:43] <lool> This requires adding support for debian/patches and extracting the current ppa-only changes as patch files
[17:43] <lool> I propose we split that like the Hildon 2.0 modules
[17:44] <lool> Does that work for everybody?
[17:44] <lool> rustyl_: Would you be willing to participate?
[17:44] <lool> Who from Intel would be willing to take a share?
[17:44] <lool> Everybody I guess! :)
[17:45] <rustyl_> lool, if somebody does the first package, then I would be happy to do (or delegate) several of the other packages
[17:45] <bspencer> mawhalen -- since she's not here.
[17:45] <lool> rustyl_: deal
[17:45] <rustyl_> i just need the first package to cookbook from
[17:45] <rustyl_> and by several, i mean i can find people to do all the rest of the moblin projects
[17:46] <lool> rustyl_: I'll mail you with the steps I follow for a sample package, you will split the work amongst Intel people for some modules you'll list me and the others we shall do?
[17:46] <lool> rustyl_: Cool
[17:46] <lool> [action] lool to send rustyl_ steps to update ppa packages for the new tarball based release process
[17:46] <MootBot> ACTION received:  lool to send rustyl_ steps to update ppa packages for the new tarball based release process 
[17:47] <lool> [action] rustyl_ to assign ppa packages updates for the new tarball based release process
[17:47] <MootBot> ACTION received:  rustyl_ to assign ppa packages updates for the new tarball based release process 
[17:47] <lool> Does anybody have any question on this?
[17:47] <rustyl_> yea
[17:47] <rustyl_> what 'project' to i write launchpad bugs against?
[17:47] <rustyl_> 'launchpad' doesn't work
[17:48] <lool> rustyl_: To report the malone bug?
[17:48] <rustyl_> to report the 'i want to assign a tag to a couple hundred bugs at once' feature request
[17:48] <lool> rustyl_: https://bugs.launchpad.net/bugs/+filebug select "Project" type "malone" and search
[17:48] <lool> s/search/choose
[17:49] <rustyl_> what is malone?
[17:49] <lool> As I was saying earlier, it's the Launchpad bug tracking subproject
[17:49] <rustyl_> got it
[17:49] <lool> rustyl_: https://launchpad.net/projects/?text=launchpad 
[17:50] <lool> rustyl_: You'll see "Launchpad Bugs"
[17:50] <rustyl_> https://bugs.launchpad.net/malone/+bug/201874
[17:50] <lool> It's technical/unix name is "malone"
[17:50] <ubotu> Launchpad bug 201874 in malone "Need ability to apply tag to a collection of bugs" [Undecided,New] 
[17:50] <lool> rustyl_: Tada
[17:50] <bfiller> slightly obscure, I'd say :)
[17:50] <bfiller> malone, that is
[17:50] <rustyl_> it keeps thing mysterious
[17:51] <bfiller> good way to keep people from filing bugs :)
[17:51] <GrueMaster> Nah, it's perfectly intuitive.
[17:51] <lool> Let's end the meeting in a mysterious way then!
[17:51] <agoliveira> rustyl_: Santa Rosa? Diamondville? McAslin?
[17:51] <agoliveira> :)
[17:51] <lool> [endmeeting] malone! soyuz!
[17:51] <lool> #endmeeting
[17:51] <MootBot> Meeting finished at 17:51.
[17:51] <rustyl_> i sl8r
[17:51] <lool> told you it would be mysterious
[17:51] <lool> Thanks everybody for attending
[17:57] <amitk> jayc: I have rebased the ume trees on zinc. Looking at your merged ACPI_VIDEO patch next.
[17:59] <jay> amitk: thanks
[18:00] <jay> amitk: once that ACPI_VIDEO thing is clear to me I will upload moblin new patches to ume.
[18:00] <agoliveira> mjg59: When are you arriving in Recife?
[18:04] <anoikis> hi there
[18:04] <anoikis> any polish here?
[18:08] <anoikis> nie macie kurwa co robi chyba
[18:08] <anoikis> i z zwiazku z tym nic nie robicie
[18:09] <anoikis> bez sensu:D
[18:52] <mjg59> lool: just bzr,  haven't uploaded it yet
[18:53] <mjg59> agoliveira: tomorrow
[18:54] <agoliveira> mjg59: Nice. I was able to manage go there and I'm leaving tomorrow afternoon. See you there then.
[18:57] <lool> mjg59: Okely
[19:01] <lool> Mithrandir: Could you please add me to the ChanServ access list for #ubuntu-mobile?
[19:07] <Mithrandir> lool: done
[19:07] <lool> Mithrandir: thanks!
[19:07] <lool> Mithrandir: Whois markuman BTW?
[19:14] <Mithrandir> no idea, some guy who registered the channel ages ago and wanted to use it for something laptop-related.
[19:14] <Mithrandir> I prodded some freenode people to get it transferred to us, but didn't have the time to push it through
[20:37] <inuka_desk> smagoun, ping..
[20:38] <smagoun> inuka_desk: what's up?
[20:38] <inuka_desk> samgoun, you get the 3 drivers from arms right?
[20:38] <inuka_desk> smagoun, do you get modified libraries of mesa with that ?
[20:38] <smagoun> inuka_desk: which 3 drivers?
[20:38] <inuka_desk> sorry 3d  drivers for poulsbo
[20:39] <smagoun> inuka_desk: I get 3d drivers and a libgl1-mesa-dri-psb from ARMS
[20:39] <smagoun> that's the only mesa library I get though
[20:42] <inuka_desk> smagoun, you dont happen to use the mesa src that you get from arms right? (assumming you get an updated mesa src)
[20:42] <smagoun> inuka_desk: I don't think we've been pulling mesa source
[20:42] <inuka_desk> smagoun, thanks for the info
[20:43] <smagoun> inuka_desk: am I supposed to pull mesa source from arms?
[20:44] <inuka_desk> smagoun, I think so, I will let you know once I know for sure. 
[20:44] <smagoun> inuka_desk: ok, thanks
[21:01] <davidm> mjg59, are you calling in?
[21:02] <mjg59> davidm: Just done so
[21:23] <inuka_desk> smagoun, FYI you do have to build the mesa src and install the binaries for the 3d poulsbo stuff to work correctly. If not there will be performance issues.
[21:24] <smagoun> inuka_desk: ok, that's really good to know. Do you have any plans to push the mesa changes to the PPA?
[21:24] <inuka_desk> smagoun, no not for now anyway
[21:24] <smagoun> hmm. Ok, I'll take a look at it. Thanks for the info
[21:25] <inuka_desk> smagoun, np