[00:00] <rickspencer3> how were your trips home?
[00:00] <rickspencer3> uneventful, I hope?
[00:00] <TheMuso> Uneventful and long
[00:00] <RAOF> Yup.
[00:00] <rickspencer3> good news that
[00:00] <TheMuso> rickspencer3: However I managed to get a little unwell as a result, but I'm mostly over it now.
[00:00] <rickspencer3> :/
[00:00] <rickspencer3> lots of folks sick
[00:00] <rickspencer3> no Eastern Edition today, obviously
[00:01] <TheMuso> Yep
[00:01] <rickspencer3> RAOF, TheMuso do you guys know what to do wrt blueprints and WIs?
[00:01] <TheMuso> rickspencer3: When you are in an incubator for 20 odd hours, its not hard to get something...
[00:01] <rickspencer3> TheMuso, right, especially after a long week of hard work
[00:01] <TheMuso> rickspencer3: Yes.
[00:01] <RAOF> rickspencer3: I believe so.
[00:02] <TheMuso> rickspencer3: Re blueprints and work items, well aware of what has to happen.
[00:03] <rickspencer3> TheMuso, sweet
[00:04] <crimsun> WRT audio, I've got the two kernel config items filed as bugs and linked to the maverick review spec
[00:05] <crimsun> leann's going to affect those changes. I've also got ossp packaged and will be testing with a (recompiled) kernel locally to document some further changes.
[00:05] <crimsun> s/affect/effect/
[00:06] <crimsun> I'm working with Jon and a few others on the Qt/Phonon bits for Kubuntu.
[00:10] <TheMuso> cool
[00:11] <TheMuso> crimsun: Let me know if there is anything I can do with that to help.
[00:11] <TheMuso> crimsun: And I have begun merging/updating the ALSA stack for maverick.
[00:11] <crimsun> TheMuso: great, thanks
[00:14] <hyperair> Laney: meego interface? you mean moblin integration?
[00:21] <rickspencer3> hi robert_ancell
[00:24] <robert_ancell> rickspencer3, hey
[00:25] <rickspencer3> robert_ancell, welcome home!
[00:25] <rickspencer3> I hope you had an easy enough trip home
[00:25] <robert_ancell> home = #ubuntu-desktop? :)
[00:25] <robert_ancell> yup not too bad, seemed to avoid jetlag this time
[00:26] <rickspencer3> nice
[00:26] <rickspencer3> robert_ancell, I suppose you saw that we asked you to handle the Yorba/Ubuntu connection?
[00:27] <robert_ancell> not yet, but I'm happy to do that
[00:29] <rickspencer3> sweet
[00:29] <rickspencer3> they already love you, so it seemed like a good connection
[00:29] <robert_ancell> rickspencer3, hmm, did I just miss a meeting?
[00:30] <rickspencer3> robert_ancell, no, we cancelled this week
[00:30] <rickspencer3> but will meet on Friday (for you guys) to discuss BPs and WIs
[00:30]  * rickspencer3 whip cracking noises
[00:31] <robert_ancell> rickspencer3, ow
[00:31] <rickspencer3> hehe
[00:31] <rickspencer3> I just made the noises :)
[00:32] <rickspencer3> robert_ancell, do you have enough data to calculate your work item throughput
[00:32] <rickspencer3> ?
[00:32] <robert_ancell> rickspencer3, I don't think I do, at least not from Lucid
[00:33] <robert_ancell> and I'm don't think we tracked enough stuff in Jaunty to get the data from there
[00:33] <rickspencer3> hmmm
[00:33] <rickspencer3> well, I guess just go with a gut feel?
[00:33] <rickspencer3> or use other people
[00:33] <rickspencer3> s estimates as a basis?
[00:34] <robert_ancell> I'm going with gut feel at the moment - do you have a rough estimate for the team?
[00:37] <rickspencer3> not yet
[00:37] <rickspencer3> should have tomorrow though
[00:38] <rickspencer3> maybe have everyone put their estimates on the wiki
[00:38] <rickspencer3> robert_ancell, RAOF, TheMuso, time for me to step away
[00:38] <rickspencer3> do you guys need anything before I log off?
[00:39] <RAOF> I'm good.
[00:39] <rickspencer3> sweet
[00:39] <robert_ancell> nothing at the moment, have a good evening
[00:39] <rickspencer3> RAOF, any feedback about my announcement that we are bumping 8xx users down to VESA?
[00:39] <rickspencer3> anyone bitch, etc...?
[00:39] <rickspencer3> uh, I guess I should say "complain"
[00:40] <RAOF> Not that I've seen yet.
[00:40] <TheMuso> rickspencer3: nothing from me.
[00:40] <rickspencer3> excuse my French
[00:40] <rickspencer3> RAOF, cool
[00:40] <rickspencer3> what blueprint will that go on?
[00:41] <RAOF> General Maverick Xorg plans.
[00:41] <rickspencer3> sweet
[00:41] <rickspencer3> 'night guys!
[03:58] <robert_ancell> RAOF, hey, do you know who maintains libx11?  I need to bump some versions for GTK+
[03:59] <robert_ancell> actually make that libxi, libxcursor and libxinerama
[04:12] <RAOF> robert_ancell: cjwatson just merged libx11 from Debian; is that version not sufficient?
[04:12] <RAOF> The answer would be “Ubuntu X swat” in Ubuntu, but they tend to get pulled unchanged from Debian-X.
[04:15] <RAOF> robert_ancell: What versions do you need?
[04:17] <robert_ancell> the debian subversion for libxi-dev libxcursor-dev and libxinerama-dev
[04:17] <robert_ancell> not sure why gtk has such tight dependencies
[04:18] <robert_ancell> RAOF, so specifically libxi-dev 1.3-4, libxcursor-dev 1.1.10-2 libxinerama-dev 1.1-3
[04:20] <RAOF> Oh, the autosync is broken at the moment, isn't it?
[04:23] <RAOF> Which is why they haven't migrated automatically.
[04:25] <RAOF> robert_ancell: Ah, you need the -udebs for GTK, I take it?  All those are syncs, but I don't have upload privs for them.
[04:26] <robert_ancell> RAOF, yeah, something like that.  What are the udebs for?
[04:27] <RAOF> I think d-i's graphical installer stopped fighting with gtk-on-framebuffer, and succumbed to X.
[04:29] <robert_ancell> yeah, seb said they did that.  This GTK+ package drops support for fb
[04:29] <mclasen> sounds like a win-win to me
[04:30] <robert_ancell> RAOF, so do you expect the sync to work by tomorrow or should I poke someone to get that to work?
[04:30] <robert_ancell> mclasen, :)
[04:31] <RAOF> robert_ancell: I think the problem that the debian archive is currently broken, thus breaking launchpad's debian import, thus breaking autosync.  I don't think that'll be fixed by tomorrow.
[04:32] <robert_ancell> RAOF, hmm, ok guess I'll have to shelve that update
[04:32] <RAOF> I we should be able to manually sync, though.
[04:33] <RAOF> Ahem.  I *think* we should be able to manually sync.  If nothing else, by grabbing the debian source, signing it, and uploading.
[04:35] <robert_ancell> hmm, I don't have core upload privileges though. Do you?
[04:36] <RAOF> No.  Otherwise, I'd have done it for you already :)
[04:37] <robert_ancell> TheMuso, ^ can/should you upload X stuff?
[04:38] <ajmitch> RAOF: you should apply soon then :)
[04:39] <RAOF> ajmitch: Yes :)
[04:40]  * ajmitch can upload X stuff, but most likely shouldn't
[04:48] <TheMuso> robert_ancell: What needs uploading/updating?
[04:49] <robert_ancell> TheMuso, libxi, libxcursor, libxinerama - they just need syncing so I can sync gtk
[04:49] <TheMuso> robert_ancell: Could you request syncs and subscribe ubuntu sponsors?
[04:49] <TheMuso> someone will get to acking them
[04:50] <robert_ancell> TheMuso, RAOF said they're normally automatic, but something has broken the autosync
[04:51] <RAOF> We don't have any Ubuntu changes to these packages, no.
[04:51] <TheMuso> robert_ancell: Yes so if you want to get them manually synced, they need to be requested.
[04:51] <ajmitch> something being a broken apt-ftp-archive on ftp.debian.org, afaik LP being fixed is still blocked on that
[04:51] <RAOF> I can file the sync requests if you like.
[04:53] <robert_ancell> RAOF, please, if you know how to do them
[04:57] <Amaranth> isn't there a tool for that?
[04:57] <Amaranth> requestsync
[04:59] <TheMuso> yeah in ubuntu-dev-tools
[05:05] <RAOF> robert_ancell: Ah, it looks like they've been syncd, they're just waiting in NEW.
[06:30] <robert_ancell> RAOF, ah, thanks
[08:08] <didrocks> good morning
[08:11] <fagan> morning didrocks
[08:12] <RAOF> Morning didrocks, fagan.
[08:12] <fagan> morning RAOF
[08:15] <didrocks> morning fagan, RAOF
[08:15] <didrocks> RAOF: how your jetlag is going?
[08:17] <RAOF> didrocks: Much better.  Now it's just a niggling sore throat :)
[08:18] <didrocks> :)
[08:20] <pitti> Good morning
[08:20] <didrocks> bonjour pitti, comment ça va ?
[08:20] <pitti> c'est bien, merci! et toi?
[08:21] <didrocks> Gut, Danke Schöne
[09:04] <seb128> hey there
[09:04] <pitti> bonojur seb128
[09:05] <seb128> hey pitti
[09:05] <didrocks> salut seb128
[09:05] <seb128> lut didrocks
[09:05] <seb128> how are you?
[09:05] <pitti> seb128: FYI, I just finished my comment on https://wiki.ubuntu.com/RobertAncell/CoreDevApplication :)
[09:05] <seb128> pitti, good, thank you ;-)
[09:05] <didrocks> I'm fine and rested thanks! and you?
[09:05] <pitti> "Never ever let him near the archive!!"
[09:06] <pitti> j/k, gets high time for him
[09:06] <seb128> lol
[09:06] <seb128> didrocks, I'm good thanks, I had a good night
[09:08] <didrocks> I think we can remove games from maverick! evolution 2.30 is so fun by itself (moving the cursor on the treeview hide/show icons) :)
[09:08] <pitti> lol
[09:09] <pitti> fully understanding evolution is quite hard, after all; took mankind a couple of centuries :)
[09:09] <didrocks> heh :)
[09:13] <fagan> hmmm im on maverick and the evo data store stuff hasnt upgraded yet
[09:17] <didrocks> yeah, an archive admin has to accept the libevolution new binary package
[09:17] <seb128> didrocks, looking at it
[09:17] <didrocks> seb128: thanks
[09:48] <seb128> hum
[09:48] <seb128> bug #581799 is weird
[09:48] <ubot2> Launchpad bug 581799 in gvfs (Ubuntu) "Lot of dbus errors (affects: 1)" [Undecided,Incomplete] https://launchpad.net/bugs/581799
[09:49] <seb128> "org.freedesktop.DBus: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.56916': no such name"
[09:50] <seb128> "invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.No Reply: Message did not receive a reply (timeout by message bus" too
[09:50] <seb128> seems he is having dbus issues...
[10:40] <seb128> mvo, you need a ":" on work item lines
[10:54] <mvo> seb128: ok, I though it would automatically put a "todo" if its missing
[10:57] <seb128> mvo, no, it does that if there is nothing after ":"
[10:57] <seb128> but you need the ":"
[10:57] <mvo> thanks seb128
[10:58] <mvo> seb128: should I fix it now or did you fix it already?
[10:58] <seb128> mvo, I didn't yet, please do if you want otherwise I will do it
[11:01] <mvo> seb128: I need to go to lunch now, I can fix it afterwards
[11:02] <seb128> mvo, enjoy
[11:02] <seb128> mvo, in fact it might not be required, I'm being confused now, it seems to work fine without those
[11:02] <seb128> mvo, so ignore me
[11:02] <mvo> ok
[11:03]  * mvo waves
[11:05] <Laney> hyperair: I mean --enable-meego
[11:05] <hyperair> Laney: hmm is it getting stable anytime soon? afaik it's --disabled now since it's marked unstable upstream
[11:06] <Laney> It's good enough to use, and these are dev releases anyway
[11:06] <Laney> can switch off for stable if we need to
[11:07] <didrocks> hyperair: in any case, we want to give it a try for netbook, at least for alpha2
[11:07] <hyperair> didrocks: i see. interesting.
[11:07] <hyperair> Laney: 1.7.0 is in experimental, so i think we can --enable it there and sync over?
[11:08] <hyperair> or should we just --enable it in ubuntu only?
[11:08] <Laney> I was thinking enable it for 1.7.1 and then sync
[11:08] <hyperair> hmm sounds fine.
[11:08] <Laney> it requires some cherry picks for 1.7.0
[11:08] <hyperair> i see.
[11:08] <didrocks> I've just played with it locally, but rather with limited tests
[11:10]  * hyperair needs to get around to packaging 1.6.1
[11:12] <Laney> and the new podsleuth yeah?
[11:12] <Laney> :cool:
[11:38] <hyperair> o yeah, there was a new podsleuth
[11:38] <hyperair> @_@
[14:02] <seb128> didrocks, http://doc.ubuntu-fr.org/cd_ubuntu-fr
[14:02] <seb128> ca devrait pas être mis à jour?
[14:03] <didrocks> seb128: si, je vais de ce pas fouetter ces feignants de contributeur du wiki :)
[14:03] <didrocks> merci!
[14:03] <seb128> didrocks, 'ci ;-)
[14:05] <pitti> rickspencer3: good morning
[14:05] <rickspencer3> hi pitti
[14:05] <didrocks> good morning rickspencer3
[14:06] <fagan> morning rickspencer3
[14:06] <seb128> hello rickspencer3
[14:07] <rickspencer3> Hi didrocks, fagan, seb128
[14:07] <rickspencer3> hope all is well today
[14:07] <fagan> Very well :)
[14:08] <seb128> mvo, there is a webit 1.2.1, do you plan to sru it for lucid?
[14:09] <mvo> seb128: I have no plans for this
[14:09] <seb128> ok
[14:12] <didrocks> mvo: I've written a prototype using heavily "set()", but the code is quite ugly if we take into account the parameters changes and I prefer to rewrite wrapping a class for packages. FYI, recording 1700 entries in desktopcouch takes ~1min on my machine which is not a really fast one
[14:24] <mvo> didrocks: aha, cool - where is the code?
[14:24] <mvo> didrocks: 1min is really not great, is that a desktopcouch limitation
[14:25] <mvo> ?
[14:26] <didrocks> mvo: I'll finish the with set() version and will push it later. Concerning the 1 min for this record, I'm in a loop just creating new records (one per package). I think this is linked with desktopcouch performance
[14:27] <didrocks> mvo: this is only for the first iteration, but I can maybe optimize it, let me check
[14:27] <mvo> didrocks: ok, I don't mind looking at it even if half-finished, just let me know where it is
[14:28] <didrocks> mvo: pushing it in a bit, I have maybe an idea for this performance, need some testing. I'll ping you
[14:30] <rickspencer3> seb128, any reason that robert shouldn't go ahead and upload his fix for bug #445123 ?
[14:30] <ubot2> Launchpad bug 445123 in gdm (Ubuntu Maverick) (and 4 other projects) "No GUI option to disable face browser (affects: 26) (dups: 5) (heat: 168)" [Medium,Confirmed] https://launchpad.net/bugs/445123
[14:30] <seb128> rickspencer3, not at all
[14:31] <rickspencer3> ok
[14:40] <seb128> rickspencer3, don't bother arguing with trolls ;-)
[14:40] <rickspencer3> seb128, I know, I won't follow up
[14:41] <rickspencer3> I just needed to make my POV clear, especially as we are fixing it
[14:41] <rickspencer3> !
[14:43] <desrt>  1843 desrt     20   0 10.1g 9.7g 3320 R  101 82.8 765:50.11 indicator-apple
[14:43] <desrt> :(
[14:43] <desrt> 10 gigs of ram is just too much
[15:02] <chrisccoulson> desrt - we don't want to let good ram go to waste ;)
[15:03] <chrisccoulson> that's pretty extreme though, i've never seen it do that before
[15:15] <kenvandine> desrt, wow... that is impressive!
[15:30] <LaserJock> was there discussion at UDS about the gconf issues with various UNE sessions?
[15:44] <didrocks> LaserJock: in the default GNOME apps one, we talked about that along with gsettings
[15:45] <didrocks> LaserJock: sorry, not GNOME app, but rather GNOME components where we seek for what to update in maverick (on Monday morning IIRC)
[16:27] <seb128> didrocks, you have 3 specs for this cycle? or do I miss some on my list?
[16:27] <seb128> ie oneconf, une application selection, quickly
[16:28] <didrocks> seb128: it's correct
[16:28] <seb128> TheMuso, should desktop-maverick-opentts-to-replace-speech-dispatcher be targetted for this cycle?
[16:28] <seb128> didrocks, thanks
[16:30] <seb128> didrocks, is desktop-maverick-connman superseded by some other specs or handled somewhere else?
[16:31] <didrocks> seb128: I guess that's the one where the gobby document was lost, let me check
[16:33] <didrocks> I guess it finally turned more as a dx blueprint, so I'll change the assignee and I guess kenvandine will have the WI for the indicator stuff
[16:33] <seb128> didrocks, well we need a spec on our side to track connman work, there will be quite some desktop tasks
[16:33] <seb128> didrocks, if those are tracked in an another spec that's fine too
[16:33] <seb128> didrocks, could you check with davidbarth?
[16:33] <didrocks> seb128: yes, but that's more on kenvandine plate or mine?
[16:34] <didrocks> seb128: sure, already asked, waiting for reply :)
[16:34] <seb128> indicator is kenvandine
[16:34] <seb128> connman itself is chrisccoulson I guess
[16:34] <kenvandine> conman would be chrisccoulson?
[16:34] <seb128> kenvandine, yes
[16:34]  * chrisccoulson hides
[16:34] <chrisccoulson> ;)
[16:34] <kenvandine> :)
[16:34] <seb128> chrisccoulson, sorry ;-)
[16:34] <chrisccoulson> heh :)
[16:34] <didrocks> ok, I can assign the blueprint to chriscoulson so, and I'll update the WI with chrisccoulson and davidbarth
[16:35] <kenvandine> put my name next to the indicator stuff
[16:35] <seb128> didrocks, thanks, or check if dbarth already track those in a dx blueprint
[16:35] <didrocks> seb128: I will
[16:36] <seb128> didrocks, 'ci
[16:36] <didrocks> seb128: thanks to you to do all the tedious job of tracking those :)
[16:36] <seb128> ;-)
[16:40] <seb128> chrisccoulson, don't forget to define your work items for tomorrow
[16:40] <seb128> none of your specs are showing up yet on the tracker ;-)
[16:40] <chrisccoulson> seb128 - yeah, i'll do those tonight
[16:40] <seb128> thanks
[16:47] <LaserJock> didrocks: so will Unity use gsettings?
[16:48] <didrocks> LaserJock: no, we even don't have gsettings yet on maverick
[16:49] <LaserJock> so for maverick we will likely still have a mess of gconf settings
[16:49] <LaserJock> if non-Unity continues we can likely have GNOME, non-Unity, and Unity sessions
[16:51] <seb128> didrocks, we do
[16:51] <seb128> didrocks, we have glib 2.25
[16:51] <didrocks> seb128: oh, the new glib and dconf has been pushed already?
[16:51] <didrocks> sweet
[16:51] <seb128> dconf not yet
[16:51] <seb128> gsettings yes
[16:51] <didrocks> ok, so no storage right now :)
[16:52] <LaserJock> heh
[16:55] <LaserJock> didrocks: do you know if unity is going to reuse the "une" namespace or use "unity"?
[16:56] <didrocks> chrisccoulson: I've assigned the spec to you, dbarth suggests to only list there the integration WI (desktop-maverick-connman). kenvandine: you should also put the WI for indicators related work there too, I guess
[16:56] <davidbarth> pitti: ping? could you give your burn down chart cron job a kick before our DX call, please?
[16:56] <LaserJock> I'm trying to figure out what's going to need to be changed so that unity and non-unity don't crash
[16:57] <pitti> davidbarth: running
[16:57] <didrocks> LaserJock: I think we will use "une" one as it's Ubuntu Netbook Edition
[16:57] <didrocks> LaserJock: will be easy, I'll be able to give you an hand once I will push unity into maverick (next week I guess)
[16:58] <LaserJock> what's the plan for the -settings package name?
[16:58] <LaserJock> the one in the PPA is pretty long :-)
[16:58] <LaserJock> if I could figure out a name for "not Unity" we could transition to that :-)
[16:59] <didrocks> LaserJock: nothing decided yet, but it will replace it and we will move the other with netbook-launcher to another name (not very worried, just need to coordinate), but I prefer a more quiet time to discuss that, next week sounds fine for me
[16:59] <davidbarth> pitti: thanks!
[16:59] <didrocks> LaserJock: heh, I will try to get a name this week-end, think about it too ;)
[17:00] <LaserJock> didrocks: maybe it should be Anarchy ;-)
[17:00] <didrocks> excellent ^^
[17:03] <LaserJock> didrocks: Diversity would also be a slightly less militant version :-)
[17:03] <kenvandine> didrocks: ok, thx
[17:03] <didrocks> LaserJock: interesting idea, not really descriptive for netbook-launcher, but yeah :-)
[17:03] <didrocks> LaserJock: we'll figure out I guess
[17:04] <didrocks> it'll just take time
[17:05] <LaserJock> didrocks: well, the idea would be to pull together netbook-launcher, liblauncher, go-home-applet, and window-picker-applet I think since that is the core of the UI, right?
[17:07]  * kenvandine -> lunch
[17:08] <didrocks> LaserJock: and webfav, but yes, that's it
[17:08] <didrocks> kenvandine: enjoy
[17:10] <seb128> pitti, thanks for the "Errors in work item definitions"
[17:12] <rodrigo_> hmm, can't get update-manager -d to upgrade to maverick, is it supposed to work?
[17:13] <fagan> rodrigo_: just edit the sources file
[17:13] <rodrigo_> fagan, s/lucid/maverick you mean?
[17:14] <fagan> rodrigo_: yep
[17:14] <seb128> rodrigo_, check with mvo but I think it's too early, update-manager didn't get updated for that yet
[17:14] <rodrigo_> ok
[17:14] <seb128> rodrigo_, you can dist-upgrade using apt-get though
[17:15] <rodrigo_> seb128, and is it "safe" to upgrade, or should I wait?
[17:15] <seb128> depends of what you call safe, I guess you have been running unstable versions of distro before?
[17:15] <seb128> things might and will break on the way
[17:16] <fagan> rodrigo_: theres nothing broken at the moment from what I can see except evolution
[17:16] <seb128> especially that early when we resync some thousand packages on debian
[17:16] <rodrigo_> seb128, yeah, I mean if it boots, that's enough, I can deal with other problems
[17:16] <fagan> im on 10.10 at the moment
[17:16] <seb128> fagan, how is it broken?
[17:16] <fagan> seb128: it needs libevo
[17:16] <seb128> rodrigo_, ok, so go for it ;-)
[17:16] <rodrigo_> oh, wanted to test evo-couchdb with evolution
[17:16] <fagan> seb128: its stuck between an upgrade
[17:16] <seb128> fagan, which has been newed hours ago and should be available now?
[17:16]  * fagan checks
[17:18] <fagan> seb128: still not upgrading it
[17:18] <seb128> what error?
[17:19] <fagan> Oh I just had to run it in terminal
[17:19] <fagan> the dist-upgrade tool wasnt working for some reason
[17:20] <seb128> fagan, which means it's working now?
[17:20] <fagan> seb128: its upgrading yes
[17:20] <seb128> rodrigo_, it should be working, let me know how the upgrade goes for you
[17:21] <rodrigo_> seb128, ok
[17:21] <rodrigo_> 669mb of updates, /me presses ENTER :)
[17:22]  * fagan restarts
[17:23] <didrocks> rodrigo_: and that's when the pain begins… ;)
[17:24] <rodrigo_> didrocks, well, I've kept my workstation on lucid, so no problem :D
[17:25] <fagan> seb128: the buttons are a little out of wack in evolution http://twitpic.com/1p5yym
[17:26] <seb128> fagan, could be, I'm not running maverick yet and I don't care about bugs so early as long as the softwares runs, you could perhaps open an upstream bug about it though?
[17:26] <fagan> or combo boxes I mean
[17:26] <seb128> we don't have the ressources to deal with small bugs so early in the cycle
[17:26] <seb128> we focus on specs writting and merges for now
[17:27] <fagan> ill look into it myself
[17:27] <fagan> its just something small
[17:27] <seb128> if you decide to run crack versions it's good but please feedback to upstream when you can
[17:27] <fagan> yep will do
[17:28] <fagan> I do test early for every release
[17:28] <seb128> cool, we need early testers ;-)
[17:36] <pitti> seb128: heh, "thanks for spamming me"? :-)
[17:36] <seb128> pitti, lol, yes, the mail content is useful ;-)
[17:37] <seb128> pitti, cjwatson did SRU reviewing btw
[17:38] <pitti> I saw, yes; good
[18:02] <didrocks> dobey: from what I see, you can't now the current computer name as described in ubuntu one without connecting remotely (the information isn't stored locally), do you have a code snippet to have the limited amount of code so that I can retreive this info?
[18:10] <seb128> rickspencer3, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-python-telepathy
[18:10] <seb128> rickspencer3, do you want to track this one for maverick? it needs an assignee if you do and work items
[18:11] <kenvandine> seb128, did you see https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-ubuntu-one-api
[18:12] <seb128> kenvandine, now I did
[18:12] <kenvandine> rickspencer3 had said we wouldn't target any milestones for it but add work items and see what people could jump in and do
[18:12] <kenvandine> basically all targets of opportunity :)
[18:12] <seb128> kenvandine, do you want me to do anything special with it?
[18:12] <seb128> ok
[18:12] <kenvandine> i guess we should accept it right?
[18:12] <kenvandine> and just not target milestones, so anything we get is a win
[18:13] <kenvandine> not sure who to assign it to... i guess me :)
[18:13] <seb128> hum
[18:13] <seb128> you mean define the serie goal?
[18:13] <kenvandine> what ever you think is best
[18:13] <kenvandine> yeah...
[18:13] <seb128> it would make it listed on http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team.html
[18:13] <kenvandine> hum
[18:13] <kenvandine> ok... maybe not
[18:13] <kenvandine> rickspencer3, opinions?
[18:14] <kenvandine> i think rickspencer3 wanted the blueprint so we could track the work, but not have a strong commitment to doing it
[18:14] <seb128> ok, so it seems desktop-maverick-ubuntu-one-api is fine in the current state for this
[18:15] <seb128> desktop-maverick-python-telepathy has a serie goal
[18:15] <kenvandine> ok
[18:15] <seb128> so it's showing up on the workitems tracker
[18:15] <kenvandine> cool
[18:15] <seb128> well, not really since it has no assignee
[18:15] <kenvandine> i'll assign it to me
[18:15] <seb128> we should either find somebody who takes responsability for it
[18:15] <seb128> or drop the serie goal
[18:15] <seb128> and keep it as a target of opportunity
[18:15] <seb128> kenvandine, don't overcommit
[18:15] <kenvandine> since we won't have it on the work items tracker
[18:16] <kenvandine> i am not committing to doing it
[18:16] <seb128> you already have the higher work items number for the team right now
[18:16] <seb128> kenvandine, desktop-maverick-python-telepathy has the serie goal set
[18:16] <kenvandine> but i think i care the most about it, the idea is we want others to get involved in getting it done
[18:16] <seb128> it will be on the tracker
[18:16] <kenvandine> not that one, i was talking about the u1 one
[18:16] <kenvandine> i don't want desktop-maverick-python-telepathy
[18:16] <kenvandine> :)
[18:16] <seb128> ok sorry
[18:16] <kenvandine> sorry for the confusion :)
[18:16] <seb128> all good for the ubuntu one spec
[18:16] <seb128> np
[18:16] <kenvandine> ok
[18:17] <seb128> I will wait on rickspencer3's to comment on the telepathy
[18:17] <seb128> rickspencer3, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-opportunistic-apps-stable-release
[18:17] <seb128> too
[18:17] <seb128> no assignee, no work items... is that superseded by some other specs?
[18:17] <seb128> or informational?
[18:17] <seb128> or does somebody needs to get in charge?
[18:20] <didrocks> kenvandine: ok, so if I get some "get all machine descriptions on ubuntu one" and "get current machine description", that will go into this api?
[18:20] <kenvandine> didrocks: yes
[18:21] <kenvandine> so far we only did the publishFile api
[18:21] <seb128> rickspencer3, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-touch
[18:21] <seb128> too
[18:21] <kenvandine> as a proof of concept
[18:21] <didrocks> I'm just wondering why ubuntu one accept two similar description for different machines, that's not good :/
[18:21] <dobey> didrocks: not sure what you're trying to do with that info, but no it's not cached locally. it's gotten from the Devices widget code, anad the oauth token is just compared with the local one to get the name
[18:21] <kenvandine> didrocks: indeed... i have a ton named gordo :)
[18:21] <dobey> err, to determine if it's the local machine
[18:21] <kenvandine> which is the name of my laptop
[18:22]  * kenvandine thinks we should require the description to be unique
[18:22] <kenvandine> otherwise it isn't really useful
[18:22] <didrocks> dobey: I'm looking from ubuntuone-preference, seems straightforward. Do you think you will still enable people to get twice the same description for different devices?
[18:22] <didrocks> (without forcing to remove them before)
[18:23] <didrocks> kenvandine: yeah, that's quite ackward for my oneconf spec :/
[18:23] <didrocks> I can store the token as an id for the machine, but we will still have tons of things displayed in software-center
[18:23] <kenvandine> i should really clean mine up... i have a ton of old ones from early testing
[18:24] <kenvandine> didrocks: where does it appear in software-center?
[18:24] <kenvandine> or will it?
[18:24] <didrocks> kenvandine: not designed yet, mpt will decide :) but having the same name appears more than one isn't good
[18:24] <didrocks> once*
[18:24] <kenvandine> yeah
[18:25] <kenvandine> wish i had made it to the oneconf session... damn volcano!
[18:25] <kenvandine> anyway... so the idea being software-center could help install the same software on multiple machines?
[18:25] <didrocks> kenvandine: it will be a dropdown in ubiquity, as discussed with michael
[18:25] <didrocks> (forrest)
[18:26] <didrocks> kenvandine: yeah, I have a crappy design made with gimp: http://people.canonical.com/~didrocks/oneconf/sc.png
[18:26] <kenvandine> awesome concept!
[18:28] <didrocks> kenvandine: well, now it's implementation issues ;)
[18:28] <kenvandine> hehe
[18:28] <dobey> didrocks: we don't have any method to prevent that, and haven't really thought about how to do so
[18:30] <rickspencer3> seb128, ack on the blueprint
[18:30] <rickspencer3> I'
[18:30] <didrocks> dobey: ok, I will do without it right now. Is it safe to store the token as a way to identify the computer in desktopcouch?
[18:30] <rickspencer3> ll get it done asap
[18:30] <pitti> good night everyone
[18:30] <rickspencer3> 'night pitti
[18:30] <kenvandine> good night pitti
[18:30] <didrocks> good night pitti
[18:30] <seb128> 'night pitti
[18:30] <seb128> rickspencer3, which one? the 3 I listed?
[18:30] <rickspencer3> seb128, when you are reviewing blueprints with folks tomorrow, can you remind them about HR stuff? we have reviews, etc... coming up
[18:31] <seb128> rickspencer3, ok
[18:31] <rickspencer3> oops, I didn't scroll back
[18:31] <seb128> rickspencer3, you will not be there for the meeting tomorrow?
[18:31] <dobey> didrocks: we already store the token in the keyring
[18:31] <rickspencer3> I'll pick up all 3
[18:31] <rickspencer3> seb128, I will be there
[18:31] <seb128> ok, good ;-)
[18:31] <rickspencer3> but I figure you'll be running it
[18:31] <seb128> I will but feel free to do HR reminders if you want
[18:31] <rickspencer3> that was my subtle way of telling everyone to care about the review stuff
[18:31] <seb128> I can do those as well though ;-)
[18:31] <seb128> hehe
[18:32] <seb128> sorry to ruing the subtility there
[18:32] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-python-telepathy
[18:32] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-opportunistic-apps-stable-release
[18:32] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-touch
[18:32] <didrocks> dobey: yes, but I mean, as a way to associate (here packages list) some data to each computer in desktopcouch registered in ubuntu one, so out of the gnome-keyring in that case
[18:32] <seb128> rickspencer3, ^ summary, those are not tracker as they should right now
[18:32] <seb128> rickspencer3, we need to decided if we have ressources for those and who or if we should drop them
[18:33] <rickspencer3> seb128, ack
[18:33] <seb128> thanks ;-)
[18:33] <rickspencer3> seb128, I think the stable release one is probably captured in the software center one
[18:33] <dobey> didrocks: ah right, we probably need a better way to make that association than an OAuth token then
[18:34] <rickspencer3> but we need to track getting the pocket created and such somewhere as well
[18:34] <didrocks> dobey: can we work together on that, what should/could I do in that regard? (maybe moving the discussion into an ubuntuone related channel?)
[18:35] <dobey> didrocks: perhaps using the uname() value for nodename, and some info from udev?
[18:36] <dobey> didrocks: at least, all modern x86 machines have a machine id that doesn't change until you change the cpu/motherboard
[18:37] <didrocks> dobey: right, but I still need to associate with a name for showing to the user in software-center or ubiquity, that's why I was thinking at linking it to the ubuntu one description
[18:37] <dobey> didrocks: but perhas just the hostname is enough, since i don't know that people naming all their computers the same thing is a corner case we should care about :)
[18:37] <dobey> didrocks: eh, that description field is a bit of a hack. we really shouldn't allow it to be editable
[18:38] <didrocks> dobey: well, that's what people see in ubuntuone-preference. We should do the same for onceconf and for it. But if you need some help so that we can find another way… Just want to have a common path
[18:39] <seb128> rickspencer3, right, let's use that one for the infrastructure changes
[18:40] <rickspencer3> seb128, I think mvo should be assigned to that, and it should rather be on foundations
[18:40] <rickspencer3> what do you think?
[18:40] <seb128> rickspencer3, +1
[18:42] <seb128> rickspencer3, touch, let me read the whiteboard
[18:42] <rickspencer3> I think it's an OEM services project
[18:43] <rickspencer3> I pinged bfiller, will discuss later today with him
[18:43] <seb128> ok
[18:43] <seb128> I was going to suggest oem or dx
[18:43] <seb128> I think bratsche_ has some action items for the gtk changes
[18:43] <dobey> didrocks: yeah, but i think we should change the way that works
[18:43] <seb128> or at least he said he would have a look
[18:44] <didrocks> dobey: ok, I'll go with the hostname and get the duplication with uuid.getnode() for now. Will be great if we can synchronise that with devices shown in ubuntu one. Thanks in any case :)
[18:45] <dobey> didrocks: i won't be working on the client stuff this cycle really. i'm rotating to our operations team. but we should probably have some discussion in #ubuntuone or somewhere about how to improve this experience
[18:46] <didrocks> dobey: oh ok, I'll try to get that somewhere and then will propose this to #ubuntuone. Thanks a lot!
[20:14]  * didrocks waves goodnight
[20:16] <kenvandine> good night didrocks
[20:16] <rickspencer3> tremolux, hey
[20:16] <rickspencer3> g'night didrocks
[20:17] <rickspencer3> bon nuit ;)
[20:17] <tremolux> rickspencer3: hey Rick!
[20:17] <tremolux> see ya didrocks
[20:17] <rickspencer3> tremolux, this ppa is acting really weird for me in software-center
[20:17] <rickspencer3> ppa:nisshh/ppa
[20:18] <rickspencer3> could you please check out if it works for you?
[20:18] <rickspencer3> It seems like I can add it, but I can't get it to show up
[20:18] <tremolux> rickspencer3: yep
[20:18] <tremolux> rickspencer3: hmm, ok, I'll try it
[20:22] <tremolux> rickspencer3: is that the testdrive ppa?
[20:22] <rickspencer3> no
[20:22] <rickspencer3> it's something called pytask
[20:22] <rickspencer3> somebody made it with quickly today
[20:23] <rickspencer3> I added the PPA with add-apt-repository
[20:23] <rickspencer3> and apt-get knows about pytask
[20:23] <rickspencer3> but software-center doesn't seem to
[20:23] <tremolux> rickspencer3: hmm, it's not showing up for me either  :-/
[20:24] <rickspencer3> there is a bug somewhere, would be good to know where
[20:24] <tremolux> rickspencer3: yes, let me dig around to see what's going on
[20:24] <rickspencer3> tremolux, could it be because of no auth?
[20:24] <rickspencer3> WARNING: The following packages cannot be authenticated!
[20:24] <rickspencer3>   pytask
[20:24] <rickspencer3> I wonder if the lp key server thingy is down or something
[20:25] <rickspencer3> like the key exchange didn't work?
[20:25] <tremolux> rickspencer3: it sounds plausible
[20:25] <rickspencer3> tremolux, I know hardly anything about how this stuff works :/
[20:25] <rickspencer3> fwiw, I installed it fine with apt-get
[20:26] <rickspencer3> except for that warning
[20:31] <tremolux> rickspencer3: yeah, I don't think that auth issue with the package would keep the ppa from showing up
[20:31] <rickspencer3> what do you think is up?
[20:31] <tremolux> not sure, that used to happen if you did not do a 'sudo update-apt-xapian-index', but that makes no difference for me
[20:33] <tremolux> (we've incorporated the apt-xapian-index update in software center anyway)
[20:33] <rickspencer3> tremolux, could you please log a bug, I guess?
[20:33] <tremolux> rickspencer3: I'll have to investigate to find out why there would be an issue with one ppa like this (don't think we've got any other reports of such problems)
[20:33] <tremolux> yep, I will
[20:33] <tremolux> I'll let you know what I find out
[21:33] <fta> slomo, hi, /wrt libvpx, how soon is your "soonish"? :)
[21:33] <slomo> fta: it's waiting in debian NEW and here: https://launchpad.net/~gstreamer-developers/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=lucid
[21:35] <fta> slomo, great. i need it for chromium
[21:35] <slomo> fta: ok, if you have any problems feel free to write me an email
[21:35] <fta> slomo, but as i provide backports down to hardy, i guess it will need some work
[21:46] <Amaranth> dpkg-shlibdeps: error: couldn't find library libdecoration.so.0 needed by debian/compiz-kde/usr/bin/kde4-window-decorator (ELF format: 'elf64-x86-64'; RPATH: '').
[21:46] <Amaranth> *headdesk*
[21:55] <desrt> hmm.  this indicator-applet using 10gigs thing appears to be somehow related to sound
[21:55] <desrt> when rhythmbox is running the sound indicator is using 100% CPU and that's when indicator-applet is leaking...
[23:24] <crimsun> desrt: should have spew in /var/log/user.log, then. If it's pulse spewing ratelimit, first check that you don't have an HDA controller for sound (if you do, err, well...). You might want to try linux-alsa-driver-modules-$(uname -r) from ppa:ubuntu-audio-dev if you do.
[23:25] <crimsun> desrt: namely, the bug there is that the driver incorrectly read one of the ICH registers and so didn't compensate for broken DMA.
[23:48] <TheMuso> ooo can't wait till we get vp8 support into Ubuntu. :)