[03:07] <robert_ancell> TheMuso, can you sponsor glib for me from bzr?  Also consider adding an endorsment to https://wiki.ubuntu.com/RobertAncell/CoreDevApplication/ so I can stop bothering you for sponsoring :)
[03:08] <TheMuso> robert_ancell: Ok I'll see what I can do. Feeling a little lousy today so not sure if I want to trust myself with uploads when not at 100%, but I'll take a look.
[03:09] <robert_ancell> TheMuso, np.  It's a trivial patch adding a missing include (the build servers freak out on 64 bit platforms as there is an undefined function (i.e. defaults to returning int) being converted to a pointer)
[03:09] <TheMuso> ah ok
[03:09] <robert_ancell> so my build box built it ok on i386, couldn't catch that one before release :)
[03:10] <TheMuso> robert_ancell: The patch is not in the repo
[03:10] <robert_ancell> pushing now...
[03:11] <TheMuso> thanks
[03:12] <TheMuso> got it
[03:12] <TheMuso> yeah this is trivial enough.
[03:13] <TheMuso> robert_ancell: Do you use bzr builddeb to build the package?
[03:13] <robert_ancell> yes
[03:14] <robert_ancell> bzr buildeb everywhere!
[03:15] <TheMuso> hrm interesting. I am surprised the build process succeeded then.
[03:16] <robert_ancell> TheMuso, why?
[03:18] <TheMuso> robert_ancell: I would think that if builddeb packaged up the package without the patch, the build would have failed.
[03:19] <robert_ancell> TheMuso, oh, no I hadn't tried to build with this patch (the change was made on my lucid box)
[03:31] <TheMuso> ah ok
[03:32] <TheMuso> Right, I am using lucid witgh a maverick chroot.
[03:33] <TheMuso> Test buildnig on amd64.
[03:33] <TheMuso> gah typing
[03:34] <robert_ancell> TheMuso, using pbuilder?  Mine didn't seem to work right
[03:36] <TheMuso> robert_ancell: Using sbuild.
[03:37] <robert_ancell> never heard of that
[03:37] <TheMuso> Ah ok. Its an alternative to pbuilder, and uses LVM snapshots for chroots.
[03:38] <robert_ancell> handy
[03:42] <TheMuso> Very much so. It gives me chroots to test in, as well as chroots to build in.
[03:42] <TheMuso> When using sbuild/schroot, you have a snapshot made of your existing chroot for building/testing, and when you finish, the chroot is destroyed, with no change made to the source chroot.
[03:42] <TheMuso> And its easy to update the source chroot when you need to.
[03:43] <TheMuso> robert_ancell: build succeeded and uploaded.
[03:43] <robert_ancell> TheMuso, thanks!
[03:43] <TheMuso> np
[03:44] <TheMuso> Will comment on your application ASAP.
[03:45]  * robert_ancell ->lunch
[04:35] <eeejay> so lucid is a dvd?
[04:37] <TheMuso> eeejay: no
[04:37] <TheMuso> eeejay: at least afaik
[04:38] <eeejay> TheMuso, cdimage.ubuntu.com is showing me a dvd, weird
[04:39] <TheMuso> hrm that is weird.
[04:39]  * TheMuso looks.
[04:39] <kklimonda> http://releases.ubuntu.com/releases/10.04/
[04:40] <TheMuso> eeejay: right, try releases.ubuntu.com
[04:40] <eeejay> ah, ok
[04:40] <eeejay> weird, didn't know there were dvds too
[04:40] <eeejay> thought i was phished for a second
[04:41] <TheMuso> heh
[08:06] <didrocks> good morning
[08:08] <RAOF> Good morning didrocks
[08:08] <didrocks> hey RAOF, how are you?
[08:10] <RAOF> didrocks: Tired :)
[08:10] <RAOF> Jetlagged is probably a better description.
[08:11] <pitti> hey RAOF, good morning didrocks
[08:11] <didrocks> hello pitti
[08:12] <RAOF> Hey pitti.
[08:17] <pitti> didrocks: how's maverick?
[08:18] <didrocks> pitti: good to me, once I've fight with my nvidia card to enforce it to use nouveau and not vesa :)
[08:21]  * RAOF perks up.
[08:22] <RAOF> My nvidia netbook looks like it might almost have finished the dist-upgrade, some two hours after I started it.
[08:22] <TheMuso> Hey RAOF. I can certainly join the jetlagged club.
[08:23] <RAOF> Good thing Robbie factored in a “UDS hangover” week :)
[08:23] <TheMuso> I rarely get jetlagged, but it has to do with the time I flew out of Europe I think.
[08:23] <RAOF> I think that if
[08:23] <RAOF> I didn't have to spend *another* 9 hours on the Singapore→Melbourne flight I would have been ok :)
[08:28] <TheMuso> Yeah me too, although I still had to sleep on the Singapore to Sydney leg.
[08:32] <RAOF> I didn't manage to do that.  Perversely, while the Singapore→Melbourne A380 was more comfortable generally, the Heathrow→Singapore 747 was more comfortable to sleep in.
[08:32] <TheMuso> heh
[08:33] <TheMuso> I have found that as well, for some reason I can sleep better on the 747.
[08:46] <robert_ancell> RAOF, it took you 9 hours to get to Melboune from sydney?
[08:47] <RAOF> robert_ancell: That *would* be a feat.  No, that was *Singapore* → Melbourne.
[08:47] <robert_ancell> oh, that makes more sense :)
[08:58] <seb128> hey robert_ancell RAOF
[08:58] <RAOF> Hey seb
[08:58] <didrocks> hey seb128, how are you?
[08:58] <seb128> lut didrocks
[08:58] <seb128> good! you?
[08:59] <seb128> hum, update done, restart, brb
[09:02] <seb128> re
[09:02] <didrocks> seb128: I'm fine thanks. Pondering if I upload or not the evo merge (there is just a new version on debian unstable and I merged from experimental yesterday) :)
[09:02] <seb128> didrocks, new version being "upload to unstable"?
[09:02] <seb128> robert_ancell, drop directfb, it was useful for the debian installer only
[09:02] <seb128> robert_ancell, they moved it to use x11 now
[09:02] <pitti> hey seb128
[09:02] <didrocks> seb128: little changes in evolution and e-d-s, just not "upload to unstable"
[09:03] <seb128> hey pitti
[09:04] <seb128> didrocks, you can upload what you want, anybody running maverick now can deal with small issues
[09:04] <didrocks> seb128: I should mention as well that even the unstable debian version (and my merge) makes the ui freeze with my current .evolution when clicking on an email :/ I don't have that issue with a clean .evolution directory. Don't know if it's only for me…
[09:04] <seb128> I'm amazed some people run maverick already
[09:04] <seb128> didrocks, ok, still good for maverick to upload ;-)
[09:05] <didrocks> seb128: ok, hope my merge is good, evolution is not that fun to merge TBH, especially when upstream changed a lot their code/plugins as well debian for the packaging :-)
[09:05] <didrocks> uploading now, will do evolution-mapi and evolution-exchange later
[09:05] <seb128> yeah, I know ;-)
[09:05] <seb128> those are probably direct syncs
[09:06] <didrocks> the delta is small, but I didn't review them yet. I should rather do some blueprints/paperwork now
[09:06] <seb128> ok, have fun
[09:06] <didrocks> thanks :)
[09:07] <robert_ancell> seb128, cool, just wanted to check if anyone else was using it
[09:07] <seb128> robert_ancell, if they do they will complain soon enough
[09:07] <robert_ancell> :)
[09:08] <seb128> robert_ancell, but previous time I checked with people on IRC it was only the installer
[09:08] <seb128> robert_ancell, running maverick already?
[09:08] <seb128> robert_ancell, is it stable enough to be used?
[09:09] <robert_ancell> seb128, running it on my netbook.  Seems fine so far but I don't think there's been many changes yet
[09:11] <didrocks> it runs fine there (running from yesterday), nothing noticeable to me, appart from some nvidia hellness
[09:12] <seb128> you guys are crack addicts ;-)
[09:12] <seb128> I will upgrade a vm today so I can test some of the merges I do
[09:12] <RAOF> didrocks: That was nvidia, not nouveau, right?  Nouveau just worked for my netbook.
[09:12] <RAOF> seb128: Hah!  You, with your testable-in-VM merges :)
[09:13] <didrocks> RAOF: right, but the fallback to say "hey, you can't use anymore your silly nvidia driver" fallback to vesa. I had to run update-alternative by hand to say I really want nouveau
[09:13] <seb128> RAOF, lol
[09:13] <seb128> good point ;-)
[09:13] <seb128> the good thing is that you guys will complain if I break something
[09:13] <seb128> ie no complain means I didn't break gconf yesterday? ;-)
[09:14] <robert_ancell> later all
[09:15] <RAOF> didrocks: Ok.  I know why that is.  Hurray for nvidia replacing important parts of the X stack?
[09:15] <didrocks> seb128: well, I have some strange encoding with the trigger on gconf, but I'll have a deeper look later
[09:15] <seb128> didrocks, encoding error you mean?
[09:16] <RAOF> didrocks: The one where a schema install fails with a message like “??????????? gnome-whatever-something-or-other ????????????????????? stuff ??????????????”
[09:17] <didrocks> seb128: what RAOF said ^^
[09:17] <seb128> ok
[09:17] <seb128> it's likely a simple schemas translation issue
[09:19] <seb128> RAOF, serie goal != target milestone btw
[09:20] <seb128> RAOF, not sure if you confused both, it seems you set the target milestone for your specs
[09:20] <RAOF> seb128: I did set the target milestone.  Gah, sorry.
[09:21] <seb128> RAOF, that's ok, you can't set the serie anyway, just suggest and somebody need to accept it
[09:21] <seb128> RAOF, I'm settings the series so no need to bother with those
[09:21] <RAOF> Thanks.
[10:07] <seb128> re
[10:08] <seb128> is there anybody around who fancy doing some testing for things still blue on http://people.canonical.com/~ubuntu-archive/pending-sru.html?
[10:11] <didrocks> I can do some on lucid with my netbook, like simple-scan and glib (evince, xsane and poppler are mine, so I can't "vote")
[10:12] <didrocks> (imapx has a really impressive speedup btw)
[10:12] <seb128> didrocks, imapx? is that new evo?
[10:12] <didrocks> seb128: yes, the new evo imap protocol
[10:13] <seb128> pitti, bug #33288, should it be flagged verification-done?
[10:13] <ubot2> Launchpad bug 33288 in poppler (Ubuntu Lucid) (and 2 other projects) "Evince doesn't handle columns properly (affects: 28) (dups: 9) (heat: 248)" [Medium,Fix committed] https://launchpad.net/bugs/33288
[10:13] <didrocks> seb128: got all my emails in less than 10 minutes when it takes more than one hour
[10:13] <seb128> nice
[10:13] <didrocks> the bad thing is that you have to resynchronize your whole account, you can't switch from imap to imapx without this
[10:14] <pitti> seb128: I'd like to see some more tests with other documents; it was an enormous patch
[10:14] <seb128> pitti, ok
[10:49] <seb128> didrocks, no need to bother changing breaks or conflicts etc for versions before lucid
[10:49] <seb128> didrocks, since we don't support upgrades from before lucid now, we can drop those deltas
[10:50] <didrocks> seb128: I was wondering if I keep that or not, but ok, I'll remove it in next upload
[10:51] <didrocks> seb128: do you make a blueprint on the wiki for default app selection (I'm thinking about desktop and UNE) as there are some random pieces into it?
[10:52] <seb128> didrocks, did we previous cycle? let me check
[10:52] <seb128> didrocks, yes
[10:52] <seb128> didrocks, see https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/DefaultsApps
[10:52] <didrocks> seb128: thanks, I'll base on that
[11:00] <chrisccoulson> didrocks -a re you tracking the chromium change on the same blueprint?
[11:00] <chrisccoulson> i think rickspencer3 was talking about having one specific for chromium yesterday
[11:00] <didrocks> chrisccoulson: no, only the seed on UNE one, I guess all the other should go to the new one
[11:00] <didrocks> chrisccoulson: did you create it? do you want me to do it?
[11:01] <chrisccoulson> didrocks - feel free to do that, i've still got all this hardy work to do
[11:50] <pitti> mvo: do you know why /var/cache/apt/srcpkgcache.bin comes back even without having any deb-src? (it wastes 13 MB)
[12:00] <chrisccoulson> hey pitti
[12:00] <pitti> hey chrisccoulson, how are you?
[12:00] <chrisccoulson> pitti - i'm good thanks, how are you?
[12:01] <pitti> I'm great, thanks
[12:01] <chrisccoulson> are you still processing the SRU queue in your new role, or should i pester somebody else about it? ;)
[12:01] <pitti> chrisccoulson: it's sticky, so I'll have a look every now and then, but not that often any more
[12:02] <pitti> I hope cjwatson and jdong can help out a bit, as well as slangasek
[12:02] <chrisccoulson> pitti - ok, no worries
[12:02] <seb128> there is already some people complaining it seems
[12:02] <chrisccoulson> thanks
[12:02] <chrisccoulson> hey seb128
[12:02] <seb128> we need new people to step in ;-)
[12:02] <seb128> hey chrisccoulson
[12:02] <Laney> maybe the SRU team should call for new members
[12:20] <mvo> pitti: the name is actually misleading, it contains a cache of the content of sources.list, pkgcache.bin contains a cache for the content of the lists/ directory. it should be possible to just set this via "dir::cache::srcpkgcache to "" and its gone
[12:20] <mvo> pitti: the performance hit should be (for most cases) very small
[12:20] <pitti> mvo: \o/
[12:20] <pitti> mvo: danke
[12:20] <mvo> pitti: is this for the livefs?
[12:21] <pitti> mvo: that perhaps, too; I'm currently investigating how small a small installation can be
[12:21] <mvo> pitti: its actually a very good point, I wonder how much it still matters nowdays, I will talk to david about it
[12:21] <pitti> and those two cache files are 26 MB
[12:21] <pitti> (in my test chroot anyway)
[12:21] <mvo> you could get rid of both, but without pkgcache.bin it will always have to build that cache in memory
[12:21] <mvo> if size really matter that may be a worthwhile trade-off
[12:21] <pitti> my chroot is 476 MB now, and I identified a few relatively easy additional savings which can bring it down to 406 MB
[12:21] <mvo> but srcpkgcache.bin should not matter in most cases
[12:22] <pitti> (with xfce, custom kernel, small seed, etc.)
[12:23]  * mvo celebrates commit r777 in software-center trunk
[12:23]  * pitti -> lunch
[13:00] <didrocks> Is anybody aware of a way to add an environment variable to a desktop file like Exec=FOO=bar command? (I tried to escape it, using quotes…). I only see a wrapper as a way to do it right now.
[13:01] <soren> didrocks: bash -c "foo=bar dostuff"
[13:01] <soren> didrocks: perhaps.
[13:01] <didrocks> soren: let's have a try :)
[13:01] <soren> s/bash/sh/, probably.
[13:02] <seb128> didrocks, what soren said I would do too
[13:03] <didrocks> soren: yeah, that work. Still better than a wrapper :)
[13:03] <didrocks> soren: thanks
[13:03] <soren> didrocks: Sure.
[13:04] <didrocks> ok, I think I will set CLUTTER_VBLANK to none for netbook-launcher, the new clutter has a lot of regression on different hw making une unusable for them and this trick seems to fix for them without having negative impact on netbook-launcher
[13:04] <seb128> didrocks, or delay the clutter update for now?
[13:04] <didrocks> seb128: oh, I mean, with clutter 1.2, the one in lucid (I'm speaking about an SRU)
[13:04] <seb128> doesn't seem something we need to update now
[13:04] <seb128> oh ok
[13:05] <didrocks> I receive a lot of bug mail :)
[13:36] <didrocks> chrisccoulson: I've just made a first quick iteration on WI for chromium (https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-chromium), feel free to add more
[13:39]  * rickspencer3 looks
[13:39] <rickspencer3> didrocks, may I rename the blueprint?
[13:39] <rickspencer3> "Chromium for UNE"?
[13:40] <pitti> hey rickspencer3, good morning
[13:40] <rickspencer3> hi pitti
[13:40] <rickspencer3> good afternoon
[13:40] <didrocks> rickspencer3: sure, this is surely a better name :) I was thinking about getting a true support model for it, but it's probably better stating "on UNE"
[13:40] <chrisccoulson> thanks didrocks, will have a look in a bit
[13:40] <chrisccoulson> hey rickspencer3
[13:40] <rickspencer3> hi chrisccoulson
[13:41] <rickspencer3> hope you are well today
[13:41] <chrisccoulson> rickspencer3, yeah, i'm good thanks. how are you today?
[13:41] <rickspencer3> doing well
[13:41] <rickspencer3> slept until almost 5am today
[13:41] <rickspencer3> and went to bed at 9pm, so getting over jetlag
[13:42] <rickspencer3> didrocks, chrisccoulson we should ask jcastro to get us in touch with evan from Google asap
[13:42] <rickspencer3> so we can coordinate the Chromium on UNE blueprint
[13:42] <rickspencer3> seb128, I talked to the shotwell guys yesterday
[13:42] <didrocks> rickspencer3: that will be good, right
[13:42] <rickspencer3> they are psyched to be chosen for default on Ubuntu
[13:43] <rickspencer3> since robert_ancell already has a relationship with them, I was thinking he could be the main liason
[13:43] <chrisccoulson> rickspencer3, yeah, i don't envy your long trip ;)
[13:44] <rickspencer3> chrisccoulson, "twenty twenty twenty four hours to go ... I want to be sedated"
[13:44] <rickspencer3> ;)
[13:44] <chrisccoulson> didrocks - for the desktop-maverick-une-app-selection blueprint, we probably need to do a bit more than seed chromium and remove firefox
[13:44] <chrisccoulson> ideally, we also need to get the webkit version of yelp in, split spidermonkey from xulrunner, drop xulrunner and make couchdb depend on spidermonkey
[13:44] <chrisccoulson> else it won't fit on the CD ;)
[13:45] <chrisccoulson> it's pretty much double the size of firefox right now
[13:45] <kenvandine> chrisccoulson, yay!
[13:45] <didrocks> chrisccoulson: I was thinking that would go to the chromium spec, but it there are some bit feel free to add workitem for the xulrunner and couchdb thing (just added a "ensure it works" for now) :)
[13:45] <didrocks> so, that means we have to update to last yelp on maverick? (the one in lucid isn't using webkit IIRC)
[13:46] <rickspencer3> seb128, chrisccoulson I was thinking about chromium ...
[13:46] <rickspencer3> do they have patches that we should take into the distro?
[13:46] <chrisccoulson> didrocks - yeah, we'll need to the latest version of yelp so that we can drop xulrunner from UNE
[13:46] <rickspencer3> like if they made sqllite faster, don't we want a generally faster sql lite?
[13:46] <chrisccoulson> else we're going to struggle to find the space
[13:46] <chrisccoulson> i don't know what seb128 feels about that ;)
[13:46] <didrocks> chrisccoulson: and for couchdb, do you think it's also possible?
[13:46] <rickspencer3> kenvandine, chrisccoulson in terms of couchdb, I think we should do whatever we can to get futon off the CD
[13:47] <chrisccoulson> didrocks - couchdb is only using spidermonkey, so i could split up the xulrunner package
[13:47] <rickspencer3> it's a waste of space, and U1 team is taking over slip cover for desktopcouch management
[13:47] <didrocks> chrisccoulson: sweet, I'm feeling a little bit better now considering cd space so :)
[13:47] <seb128> hey rickspencer3
[13:47] <didrocks> rickspencer3: really? slip cover FTW \o/
[13:47] <seb128> sorry I was working on a gtk update
[13:48] <kenvandine> rickspencer3, futon isn't really the problem though, not sure if it can be split out
[13:48] <seb128> reading backlog
[13:48] <kenvandine> but we can look
[13:48] <rickspencer3> I thought futon required xulrunner, and all this
[13:48] <kenvandine> no
[13:48] <kenvandine> it is  more
[13:48] <kenvandine> the views inside the db
[13:48] <chrisccoulson> rickspencer3, is it futon that requires spidermonkey?
[13:48] <rickspencer3> or is xulrunner for the actual json parsing?
[13:48] <kenvandine> use spidermonkey
[13:48] <seb128> rickspencer3, robert_ancell for shotwell liaison++
[13:48] <rickspencer3> seb128, thanks, I'll tell him it was your idea
[13:48] <kenvandine> hehe
[13:49] <rickspencer3> kenvandine, in any case, Futon is not useful, so if it takes up space, let's get it out of there
[13:49] <kenvandine> yeah
[13:49] <seb128> rickspencer3, lol, thanks, you can tell him we agree on the idea rather ;-)
[13:50] <seb128> chrisccoulson, I'm not sure how short on CD space UNE is right now
[13:50]  * didrocks adds a WI to rickspencer3: "update Quickly tutorial to user slip cover"
[13:50] <seb128> chrisccoulson, but I agree with you plan of action for it
[13:50] <rickspencer3> kenvandine, chrisccoulson, didrocks, pitti, ArneGoetje, did you guys calculate your WI throughput yet?
[13:50]  * rickspencer3 hint hint hint
[13:50] <didrocks> seb128: well, more or less like the desktop right now considering CD space, not a lot of free space
[13:51] <seb128> we can drop langpacks for now
[13:51] <seb128> and deal with xulrunner split a bit later
[13:51] <kenvandine> rickspencer3, will do :)
[13:51] <pitti> rickspencer3: sorry, not yet; what's the divisor? i. e. how many weeks of development should we assume?
[13:51] <didrocks> rickspencer3: I didn't have all my WI set for maverick yet, should be ok this evening, I hope
[13:51] <seb128> didrocks, the maverick wis are for thursday you have time
[13:51] <rickspencer3> pitti, we need a weekly calculation, as each iteration has different number of weeks
[13:51] <rickspencer3> for A2, it's 6 weeks
[13:51] <seb128> didrocks, today you should have this number and your list of specs
[13:52] <rickspencer3> also, don't forget the .75 multiplier to account for 10.04.1
[13:52] <pitti> rickspencer3: I got 81 WIs done in lucid; I just wonder how many weeks I should assume for development; it's certainly much less than 26
[13:52] <didrocks> rickspencer3: seb128: the thing for lucid WI is that I only get those on January, not for the whole lucid cycle
[13:52] <pitti> rickspencer3: but that number of weeks should be by and large the same for everyone?
[13:53] <rickspencer3> pitti, about the same
[13:53] <chrisccoulson> rickspencer3, i haven't done anything with WI's yet, i'm trying to get all this mozilla work done so i can make a start on maverick
[13:53] <seb128> didrocks, it's a number of item by work week, you should be able to adapt with your number of weeks
[13:53] <rickspencer3> I guess you had 8 weeks of full on development
[13:53] <rickspencer3> chrisccoulson, true, you are a special case
[13:53] <didrocks> ok, will do that and adapt from your number guys
[13:53] <pitti> rickspencer3: it's much more than 8, though; I started before UDS with some things, and I did some cleanup stuff post-beta
[13:53] <rickspencer3> pitti, actually, I guess 12
[13:53] <pitti> a lot of folks did WIs after beta, in fact
[13:53] <rickspencer3> pitti, ack, so it's idosyncratic
[13:53] <seb128> didrocks, see https://wiki.ubuntu.com/DesktopTeam/10.10/WorkItemProcess
[13:54] <rickspencer3> what I really want is everyone to do their own estimates based on evidence from Lucid
[13:54] <rickspencer3> I'm not sure there is a "one size fits all" calculation
[13:55] <pitti> rickspencer3: 16 weeks seems realistic for me, so I have about 5/week
[13:55] <rickspencer3> pitti, ok but mulitply by .75 to account for 10.04.1
[13:55] <rickspencer3> so 4/week
[13:55] <pitti> don't count on that for maverick, though :)
[13:55] <baptistemm> hello
[13:56] <seb128> hey baptistemm
[13:56] <rickspencer3> then by .2 to account for being on rotation
[13:56] <pitti> rickspencer3: times 0.2 for the rotation :)
[13:56] <rickspencer3> so about 1 per week
[13:56] <baptistemm> hi seb128
[13:59] <seb128> didrocks, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-une-app-selection
[13:59] <seb128> didrocks, gthumb -> eog I guess
[13:59] <didrocks> seb128: fixed, thanks
[14:00] <seb128> didrocks, thanks
[14:00] <didrocks> seb128: can you accept https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-oneconf for maverick, please?
[14:00] <didrocks> rickspencer3: FYI, I've add the quickly-GC integration to Quickly blueprint to avoid over brain breakage for two WI on another blueprint
[14:01] <rickspencer3> didrocks, sounds fine
[14:01] <seb128> didrocks, done
[14:01] <rickspencer3> we'll pick that up in A3 or so
[14:01] <rickspencer3> I think Quickly itself is a higher priority than the GC integration
[14:01] <rickspencer3> didrocks, sound ok?
[14:01] <didrocks> rickspencer3: agreed. The API is already there, but apart from the that, the rest can wait
[14:01] <seb128> didrocks, I think you need a ":" on each wi line btw<
[14:02] <seb128> pitti, ^ does the lines need to have a ":"?
[14:02] <pitti> yes
[14:02] <pitti> to separate description from status
[14:02] <didrocks> seb128: pitti: ok
[14:02] <seb128> I was not sure if none was equivalent of TODO
[14:02] <seb128> so checking
[14:02] <seb128> pitti, thanks
[14:06] <kenvandine> seb128, can you accept this for maverick?
[14:06] <kenvandine> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-social-api
[14:07] <kenvandine> seb128, or do you want to do that after all the work items are listed?
[14:08] <seb128> kenvandine, I can do that now
[14:08] <kenvandine> thx
[14:08] <seb128> you're welcome
[14:09] <seb128> ok, I'm out for a bit, will read backlog when I'm back
[14:10] <kenvandine> later seb128
[14:17] <kenvandine> rickspencer3, i suppose in calculating our WI rate we should round down to be conservative?
[14:17] <kenvandine> fractions aren't very useful for targets
[14:17] <rickspencer3> kenvandine, yes please
[14:19]  * kenvandine thinks it is going to be hard to get everything done with this number :)
[14:19] <kenvandine> well... everything i want to do :)
[14:23] <rickspencer3> kenvandine, exactly
[14:23] <rickspencer3> choose wisely
[14:23] <kenvandine> :)
[14:23] <rickspencer3> don't forget the main stream user
[14:23] <kenvandine> i know
[14:23] <rickspencer3> it's critical that we hit their expectations for quality
[14:24] <nigelb> seb128: I haz nautilius hook for you, bug 581812.  Just let me know if any corrections need to be made
[14:24] <ubot2> Launchpad bug 581812 in nautilus (Ubuntu) "Apport hook for nautilus (affects: 1)" [Wishlist,In progress] https://launchpad.net/bugs/581812
[14:32] <didrocks> my number of set WI is a little bit lower than what my "magical number" enables me for alpha2, but I feel the WI are a little bit longer to tackle and I'll be more busy with unity
[14:50] <rickspencer3> seb128, no desktop team meeting today, right?
[15:13] <seb128> rickspencer3, correct
[15:13] <seb128> nigelb, ok, thanks
[15:23] <LaserJock> didrocks: is webfav going to be used at all in Maverick?
[15:24] <didrocks> LaserJock: that's a good question, not used right now in unity if it's <hat you mean
[15:24] <didrocks> what*
[15:25] <LaserJock> didrocks: right, do you think such functionality will be required?
[15:26] <LaserJock> I was just thinking with FF -> Chromium what would happen to webfav if we kept it in Universe
[15:27] <LaserJock> I'm assuming a similar Chromium extension could be done
[15:27] <didrocks> LaserJock: TBH, I have no clue about Chromium extension but I think this can be done easily
[15:29] <LaserJock> from what I've seen poking around, they're easier to make than FF extensions
[15:29] <LaserJock> I'm just thinking about things that might be targets for Maverick for non-Unity
[15:31] <didrocks> LaserJock: that can be a good things to do, this is more discoverable than the drag & drop
[15:40] <nigelb> seb128: bug 582253 for gedit .  If you can ack your satisfaction, I'll get the folks to branch and request merge :)
[15:40] <ubot2> Launchpad bug 582253 in gedit (Ubuntu) "Apport hook for gedit (affects: 1)" [Wishlist,In progress] https://launchpad.net/bugs/582253
[15:40] <nigelb> Also, if you have any more, I'll get someone to do it
[15:41] <seb128> nigelb, sorry just back from UDS and having a zillion things to do
[15:41] <seb128> I've no time for reviews this week
[15:41] <seb128> try subscribing sponsors
[15:41] <nigelb> No problem.  I think :)
[15:41] <nigelb> I know
[15:41] <nigelb> you on'y want the nondefault gconf right?
[15:41] <LaserJock> didrocks: what was the reason for Banshee over Rhythmbox?
[15:42] <didrocks> LaserJock: nothing is decided yet, but having an app for video+music and a better user interface on netbook was considered. I think the session was recorded
[15:44] <LaserJock> didrocks: so banshee = rhythmbox + totem?
[15:44] <didrocks> LaserJock: more or less, not sure we will just hide totem or not install it if banshee fits for UNE
[15:45] <fagan> LaserJock: not really
[15:46] <seb128> nigelb, either way is fine I guess
[15:46] <fagan> banshee has a problem with ipods at the moment so its a regression from rhythmbox as a music player
[15:46] <seb128> LaserJock, on UNE? the reason was to try their netbook interface
[15:46] <nigelb> seb128: awesome, I'll work to get it in :)
[15:46] <seb128> LaserJock, they have a system which allows creating different frontends and they did a netbook specific one
[15:47] <LaserJock> seb128: ah, cool
[15:47] <seb128> didrocks, totem has a different usecase I doubt we want to uninstall or hide it
[15:47] <jcastro> fagan: someone's working on libgpod support, there's a branch somewhere
[15:47] <LaserJock> I just wondered as I normally felt Banshee to be a bit heavier on my netbook
[15:47] <didrocks> seb128: it was written in the POV, but I guess we will figure out, that's why I put it as optional
[15:47] <seb128> don't talk about jcastro when he's around, he will always try to find good argument for it :p
[15:48] <fagan> jcastro: but its a lot of work to fix it.
[15:48] <didrocks> heh :)
[15:48] <LaserJock> but a netbook-specific UI would be quite interesting
[15:48] <didrocks> jcastro has an hilight on banshee, I can't believe it /o\
[15:48] <jcastro> heh
[15:48] <fagan> I like banshee though and its better than totem because it at least has library management
[15:49] <fagan> its just the ipod stuff is a deal breaker
[15:49] <seb128> those are totally different softwares, you can't compare those
[15:49] <jcastro> I'm no expert but I'm going to guess libgpod bindings for banshee would be easier than rewriting the entire rb UI for UNE
[15:49] <LaserJock> so if I just click on a video file in nautilus, what will come up?
[15:49] <seb128> totem
[15:49] <seb128> totem is a viewer, you want to view things on double click
[15:49] <LaserJock> hmm, so then we'd have 2 video players?
[15:49] <seb128> we don't open f-spot either on double click on an image
[15:49] <seb128> as you have f-spot and eog yes
[15:50] <seb128> one is a collection manager the other a viewer
[15:50] <seb128> there is a different usecase for each
[15:50] <fagan> wow did we forget to remove eog when f-spot got a viewer?
[15:50] <seb128> if you want to quickly preview something you downloaded you don't want to start your library
[15:51] <seb128> fagan, no, it was a decision, we did add an edit button to the eog toolbar
[15:51] <LaserJock> ok, but for UNE both fspot and eog are being removed
[15:51] <seb128> having small viewers is good
[15:51] <fagan> seb128: that was for lucid what was the maverick decision on it?
[15:51] <LaserJock> I just wondered if the same thing was happening with banshee
[15:51] <seb128> use shotwell
[15:51] <seb128> which has both modes, a manager and a viewer one
[15:51] <fagan> seb128: for eog I mean
[15:52] <fagan> so shotwell for everything?
[15:52] <seb128> yes
[15:52] <fagan> oh great
[15:52] <seb128> LaserJock, right, because shotwell has a viewer mode, banshee doesn't
[15:52] <fagan> seb128: actually it kinda does
[15:53] <fagan> it doesnt import it into the library when it plays a movie
[15:53] <seb128> still it start your manager software
[15:53] <seb128> which will start autosyncing things etc
[15:54] <fagan> seb128: it wouldnt be too hard to make a mode that turns that stuff off when it plays a video
[15:54] <seb128> totem does youtube and bbc playing too
[15:54] <seb128> + subtitles in movies
[15:54] <seb128> + dvd
[15:54] <seb128> + video cds
[15:54] <fagan> the bbc plugin is broken
[15:54] <seb128> no it's not
[15:55] <fagan> the bbc block it now
[15:55] <seb128> no they don't
[15:57] <seb128> fagan, I'm playing some bbc content right now there
[15:57] <rickspencer3> seb128, is there a shotwell specific blueprint?
[15:57] <seb128> rickspencer3, not that I know about, would be good to have though
[15:57] <fagan> Oh yeah now I know what was blocked it was unofficial apps that used it
[15:57] <rickspencer3> seb128, ok, I'll make it, thoughts on assignee?
[15:58] <rickspencer3> oh, never mind
[15:58] <seb128> fagan, anyway banshee is not a video player, it doesn't subtitles, tracks, dvds, etc
[15:58] <rickspencer3> we already discussed that :/
[15:58] <seb128> rickspencer3, robert_ancell? ;-)
[15:58] <LaserJock> so the primary reason for rhythmbox -> banshee for UNE is that banshee has/will have a netbook-friendly skin
[15:58] <LaserJock> ?
[15:59] <seb128> yes
[15:59] <seb128> we will try the netbook ui
[15:59] <LaserJock> cool
[15:59] <seb128> switching depends on whether it's really better or not
[15:59] <fagan> seb128: I get that. I just thought that its a lot easier than including two but I suppose if there is functionality regressions we cant.
[15:59] <seb128> fagan, those are different softwares with different goals
[16:00] <fagan> true
[16:00] <LaserJock> is the zoho thing supposed to replace OO.o or maybe just be more pushed towards?
[16:01] <fagan> LaserJock: have you ever waited for OO.o to open on a netbook ? :)
[16:01] <seb128> LaserJock, not replace it by default no
[16:01] <fagan> it takes a while
[16:01] <seb128> LaserJock, but it's a valid alternative you might want to use
[16:01] <LaserJock> so what does that say for our "one app for each task" motto?
[16:02] <LaserJock> are we wanting to provide both local and web apps for UNE where possible?
[16:02] <didrocks> LaserJock: well, the use case is really different between local and web apps, I think it's still valid for the featured apps
[16:04] <LaserJock> I would think the use case would be basically the same, "I want to work/share docs"
[16:05] <didrocks> you still can't work in the plane or in the train if you use web apps
[16:05] <LaserJock> no?
[16:05] <LaserJock> I thought that's what offline modes were for :-)
[16:06] <LaserJock> ala google gears
[16:06] <didrocks> google gears isn't supported anymore IIRC
[16:06] <didrocks> but a replacement will come
[16:06] <fagan> it isnt didrocks
[16:06] <didrocks> (not sure about that, but just something I heard)
[16:06] <fagan> didrocks: the replacement is html5
[16:07] <fagan> its all in the html5 spec for the gears replacement
[16:07] <LaserJock> right, I'm just saying most web apps I use have some sort of offline mode
[16:07] <LaserJock> certainly not all though, for sure
[16:08] <LaserJock> so is offline/online a use case distinction for UNE, or Ubuntu in general?
[16:08] <LaserJock> this is some of the confusing bit about shipping webapp clients
[16:17] <didrocks> hum, maybe hilight them on featured apps in a special case, I don't have any idea right now TBH and more paperwork to do… :)
[16:31] <didrocks> rodrigo_: is there a way to ask to the ubuntuone syncdaemon (or other or reading desktopcouch) to know if the current computer is associated with ubuntuone and retreive the name associated to it?
[16:31] <rodrigo_> didrocks, yes, let me find it
[16:33] <kenvandine> rodrigo_, hey... question about json-glib, do you know if there is an easy way to read in json and dump it into a hash or something?
[16:33]  * kenvandine thinks json-glib should provide some data types that are at least similar to how you envision json data :)
[16:35] <rodrigo_> kenvandine, a GHashTable you mean?
[16:35] <ccheney> fagan: yea about 10s last time I used a netbook :-\
[16:35] <kenvandine> rodrigo_, something like that
[16:36] <kenvandine> rodrigo_, i noticed for tracker they basically gave up on json-glib and wrote their own functions for doing it
[16:36] <rodrigo_> kenvandine, no, it doesn't, it provides types for the json types
[16:36] <fagan> ccheney: thats faster than ive seen
[16:36] <rodrigo_> kenvandine, well, should be easy to add that to json-glib
[16:36] <fagan> ccheney: on my friends on ssd netbook it took an age
[16:36] <kenvandine> rodrigo_, that is what i was thinking :) it would make way more sense
[16:36] <rodrigo_> didrocks, see /usr/bin/ubuntuone-client, it gets the info from the u1 server
[16:36] <rodrigo_> kenvandine, yes
[16:37] <didrocks> rodrigo_: thanks, I'll have a look there
[16:37] <kenvandine> i found json-glib rather painful to deal with
[16:37] <rodrigo_> didrocks, if you have more questions, ask dobey
[16:37] <kenvandine> converting json to a GList isn't really useful
[16:37] <rodrigo_> kenvandine, oh, really? I find it quite ok
[16:37] <didrocks> rodrigo_: ok, I will, thanks
[16:37] <kenvandine> rodrigo_, i think like a python hacker
[16:37] <rodrigo_> kenvandine, ah :)
[16:37]  * kenvandine hugs simplejson
[16:37] <kenvandine> :)
[16:38] <kenvandine> json.loads(jsonstring) returns a dict :)
[16:38] <dobey> que?
[16:38] <kenvandine> so nice
[16:38] <ccheney> fagan: hmm maybe netbook ssd are actually slower than netbook hd, not sure, i ran it on a dell mini 10v with hd late last year
[16:38] <fagan> ccheney: it shouldnt be. The read time is a hell of a lot faster
[16:39] <rodrigo_> kenvandine, so, you'd like a json_object_new_from_hash/_to_hash, or something like that?
[16:39] <kenvandine> yeah
[16:39] <ccheney> fagan: or perhaps the netbook was a pre-atom system that used even slower cpu, not really sure why it would have been so slow, unless OOo has slowed down more since last fall
[16:39] <kenvandine> rodrigo_, don't you think that makes more sense?
[16:39] <rodrigo_> kenvandine, for a python hacker, I guess :)
[16:39] <kenvandine> hehe
[16:39] <kenvandine> :)
[16:39] <rodrigo_> kenvandine, but you'd have to be converting back and forth
[16:39] <fagan> ccheney: the machine I was testing on was a 1.6ghz atom with 160GB 5400speed HD
[16:39] <kenvandine> why?
[16:39] <rodrigo_> kenvandine, shouldn't be slow, so yeah, looks ok
[16:39] <kenvandine> rodrigo_, just for the parsing case
[16:39] <ccheney> fagan: ah then OOo must have gotten slower :(
[16:40] <dobey> kenvandine: why not just write your code in python then? :)
[16:40] <fagan> ccheney: dont know but I presume when more features are added it gets a little slower
[16:40] <kenvandine> dobey, cause i am creating libgwibber in C so we can get bindings for other languages
[16:40] <rodrigo_> kenvandine, cool, and adding introspection?
[16:41] <kenvandine> yup
[16:41] <dobey> oh
[16:41] <rodrigo_> cool!
[17:20] <seb128> pedro_, hey
[17:20] <seb128> pedro_, had a nice flight back?
[17:20] <pedro_> hello seb128!, oh well sort of, flight was good , theperson next to me wasn't :-P
[17:21] <pedro_> seb128, how's everything going for you?
[17:21] <seb128> oh? what happened?
[17:21] <seb128> pedro_, good thanks
[17:22] <seb128> pedro_, we could use some confirmation on GNOME sru waiting if you have time this week
[17:22] <seb128> ie for things like glib, glibmm, etc
[17:22] <seb128> just confirming your lucid still works fine since you are running those
[17:23] <pedro_> seb128, I'm planning on review sru items by tomorrow , I've installed the libraries already to at least test them for a day or so
[17:23] <pedro_> seb128, yeap will do ;-)
[17:23] <seb128> pedro_, thanks
[17:24] <pedro_> my pleasure ;-)
[17:38] <ccheney> heads up wrt bug 525807 it seems compiz is causing problems for various other apps other than just OOo, apparently totem, wine, and possibly other apps have same issue
[17:38] <ubot2> Launchpad bug 525807 in openoffice.org (Ubuntu) (and 2 other projects) "[upstream] [3.2.1] OOo Slideshow and Fullscreen modes - not full screen under compiz (affects: 60) (dups: 3) (heat: 326)" [Medium,Triaged] https://launchpad.net/bugs/525807
[17:40] <ccheney> compiz and OOo upstream are working together to try to get this fixed asap for it, not sure about the other projects
[18:49] <seb128> re
[18:49] <seb128> ccheney, is the issue a compiz one?
[18:50] <ccheney> seb128: its an issue of compiz dropping a workaround that apparently several apps didn't realize they were using, so now those apps don't work correctly
[18:50] <seb128> ccheney, seems easy to add the workaround back?
[18:50] <ccheney> seb128: apparently the workaround itself can cause issues so upstream compiz doesn't want to add it back, it would probably be easy enough for lucid though
[18:51] <ccheney> seb128: at least long term compiz devs want to apps to fix their issues
[18:52] <ccheney> i believe the OOo issue will at least be fixed for Gnome with 3.2.1 but apparently maybe not for KDE, at least without reverting the compiz change for now
[18:52] <seb128> what sort of issues would it create in lucid?
[18:52] <ccheney> upstream OOo is planning on fixing it completely for 3.3 (Ubuntu 11.04)
[18:53] <ccheney> seb128: i'm not sure one of the compiz developers is on the thread, he could probably tell you better than i could
[18:54] <ccheney> i doubt there would be any regressions at least since it was previously doing the workaround
[18:55] <ccheney> seb128: apparently it may cause a problem with totem but what that problem was not disclosed on the OOo bug report by Amaranth
[18:56] <ccheney> Amaranth: ping see seb128 ^ :)
[18:56] <Amaranth> Right, our workaround doesn't work as well as the totem one
[18:57] <Amaranth> So some apps that just want to start maximized instead get started fullscreen
[18:57] <Amaranth> For totem this makes it show the regular UI and the fullscreen UI at the same time and it gets rather confused
[18:57] <Amaranth> err, as well as the metacity one
[18:57] <seb128> Amaranth, can you summarize the issue, the workaround and the fix for applications we need to do?
[18:58] <seb128> Amaranth, is the bug a compiz one or one in different softwares?
[18:59] <seb128> ups
[18:59] <Amaranth> In the past apps that wanted to go fullscreen would just position themselves to 0,0 and resize the window to the size of the screen. Compiz and metacity prevent them from doing this as they aren't allowed to cover the panels. Metacity has a workaround to detect apps trying the old way and mark them as fullscreen. We tried to port that workaround but it doesn't work as well.
[18:59] <Amaranth> Well, the problem is it works too well.
[19:00] <Amaranth> So sometimes if you were watching a video in totem and had it maximized or fullscreen when you quit totem tries to start again maximized and compiz interprets this as a legacy app trying to go fullscreen.
[19:00] <Amaranth> This happens randomly with other apps but totem seems to be the worst
[19:01] <seb128> hum ok
[19:01] <seb128> so openoffice and some others don't do fullscreen switching as they should?
[19:02] <Amaranth> Mainly openoffice and WINE
[19:02] <seb128> do we known which ones are in this case in a standard installation?
[19:02] <seb128> ccheney suggested that totem and others are buggy too before?
[19:02] <Amaranth> Other apps either do it right or are too old/unused to really matter.
[19:02] <Amaranth> totem isn't buggy, the bug is in the workaround in compiz which is why we disabled it
[19:02] <ccheney> Amaranth: if i understood what was said in the bug report apparently totem still has issues and wine too?
[19:02] <ccheney> Amaranth: or were those the ones that didn't work before the workaround was disabled?
[19:03] <Amaranth> Totem has issues if we enable the workaround. WINE and OOo have issues if we don't enable it.
[19:03] <ccheney> eg https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/525807/comments/40
[19:03] <seb128> ok, so summary from Amaranth suggests oo.o are wine are buggy
[19:03] <seb128> ok, let's fix openoffice then
[19:03] <seb128> wine too if somebody wants to work on it
[19:03] <ccheney> Amaranth: did i misunderstand comment 40?
[19:04] <seb128> seems if we don't have ton of buggy softwares it's the best way
[19:04] <Amaranth> WINE may never do it properly unless they move the workaround in to WINE itself as on Windows apps still go fullscreen by moving to 0,0 and resizing to fill the screen
[19:04] <seb128> could we special case wine in compiz?
[19:04] <Amaranth> OOo will go fullscreen properly in 3.2.1 when using the GTK+ backend
[19:04] <ccheney> and 3.2.1 will be in 10.04.1
[19:04] <seb128> ok
[19:04] <seb128> seems we are good then
[19:04] <seb128> thanks Amaranth, ccheney
[19:05] <ccheney> np :)
[19:05] <Amaranth> I'm not sure we could, I don't know how WINE marks its windows
[19:05] <Amaranth> I believe it sticks the Windows app title in WM_NAME at least instead of just "wine"
[19:07] <seb128> ok
[19:08] <Amaranth> btw, I hope to have some compiz 0.9 packages by the end of the week
[19:09] <seb128> oh nice
[19:10] <seb128> does compiz 0.9 bring anything nice out of being a rewrite?
[19:10] <Amaranth> seb128: Yes, automatic handling of max texture size limitations
[19:10] <Amaranth> seb128: So no more dealing with that junk
[19:11] <Amaranth> seb128: And (once plugins are written/ported to handle it properly) the ability to run without any compositing at all.
[19:11] <ccheney> WIN!
[19:11] <seb128> how active is the compiz team nowadays?
[19:11] <Amaranth> You can at least do move, resize, etc without compositing now. Just need something for alt-tab basically
[19:11] <Amaranth> I think at this point it's mostly just SmSpillaz doing active development
[19:12] <ccheney> Amaranth: so compiz would work well inside VMs at that point, i think?
[19:12] <Amaranth> ccheney: Sure, just no compositing
[19:12] <ccheney> ok
[19:12] <Amaranth> It's also possible to do XRender compositing too but someone needs to write the plugin
[19:30] <seb128> jcastro, hey
[19:30] <seb128> jcastro, had a good flight back?
[19:30] <seb128> jcastro, https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-app-indicator your formatting is wrong
[19:30] <seb128> jcastro, you need to start with "Work items:"
[19:30] <seb128> jcastro, also I'm not sure [] works, just put nothing and it will default to the spec assignee for those
[19:32] <seb128> jcastro, also is the banshee item still revelant or should it be dropped in favor of the new indicator sound?
[19:34] <jcastro> ah ok
[19:34] <jcastro> I can fix that up
[19:34] <jcastro> and update the banshee one to reflect sound indicator
[19:34] <seb128> jcastro, thanks
[19:34] <jcastro> ok so we can put notes and stuff up top, and then do "Work items:"?
[19:34] <seb128> pitti, danke for doing some SRU work ;-)
[19:35] <seb128> jcastro, yes, work items start on "Work items:" and end on empty line
[19:35] <seb128> jcastro, you can put whatever you want before or after those
[19:35] <pitti> seb128: it needs some catchup..
[19:35] <pitti> seb128: I rejected your older gtk upload, keeping the newer one
[19:36] <seb128> pitti, oh thanks, I was going to do that before and got sidetracked
[19:37] <seb128> pitti, I will try to do some pinging around for SRUs tomorrow, with some luck I might get other people to review those and help you to get them to stick less to you over time ;-)
[19:37] <pitti> \o/
[19:38] <seb128> pitti, btw dunno if you saw my ping yesterday but please write something on robert-ancell wikipage for main uploads ;-)
[19:38] <pitti> seb128: I saw, will do (I have it open in the browser)
[19:38] <seb128> ok thanks
[19:38] <seb128> will be good to have him on the "upload" side rather than on the "need sponsoring" one ;-)
[19:39] <seb128> then we just need to push chrisccoulson a bit harder to apply too
[19:39] <seb128> ;-)
[19:39] <chrisccoulson> heh :)
[19:39] <chrisccoulson> i created my wiki page today, but i've not filled much of it in yet
[19:39] <seb128> \o/
[19:39] <chrisccoulson> only my name ;)
[19:39] <seb128> I guess it's a good start!
[19:40] <didrocks> seb128: got the banshee netbook ui working before going off for tonight. No "import your music" dialog by default though :/
[19:40] <jcastro> speaking of, didrocks, do I have any work items wrt. banshee/UNE?
[19:41] <jcastro> what was the plan with that?
[19:41] <seb128> didrocks, how does it look like?
[19:41] <didrocks> jcastro: just those on https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-une-app-selection
[19:41] <didrocks> can do a screenshot, one sec
[19:41] <pitti> good night everyone!
[19:41] <seb128> didrocks, you are impressive this week ;-)
[19:41]  * seb128 hugs didrocks
[19:41] <didrocks> good night pitti
[19:41]  * didrocks hugs seb128
[19:41] <seb128> 'night pitti
[19:41]  * pitti hugs everyone
[19:41]  * seb128 hugs pitti
[19:43]  * didrocks hugs pitti
[19:44] <tremolux> 'night pitti!
[19:49] <didrocks> so, first launch of the netbook ui: http://people.canonical.com/~didrocks/banshee/netbook-ui-first-launch.png
[19:49] <didrocks> then, if you click to the button to switch to classical ui and switch back: http://people.canonical.com/~didrocks/banshee/netbook-ui-library.png
[19:50] <seb128> nice
[19:52] <didrocks> the first launch is an empty panel, not optimal, but we will figure it out
[19:52] <Laney> we'll probably upload 1.7.0 with the meego interface enabled soon fyi
[19:54] <didrocks> Laney: sweet
[19:55] <Laney> hyperair: ^^^^^^^
[19:57] <bl8> Laney: the compilation error we saw together should be fixed now in banshee git master
[19:58] <didrocks> Laney: is there any changes to the netbook interface in 1.7.0?
[19:59] <Laney> didrocks: not sure, build it from debian and have a look if you like
[19:59] <Laney> or upstream of course
[19:59] <Laney> bl8: cool, shall cherry pick (or just wait for 171 if it's imminent?)
[19:59] <bl8> didrocks: you can "touch /etc/meego-release" for additional MeeGo specific customizations
[20:00] <didrocks> Laney: will you update soon into maverick? otherwise, I can just have a quick upload for enabling it in the current version
[20:00] <didrocks> bl8: is there a documentation about bits that I can put in?
[20:00] <Laney> didrocks: I have to port the f-spot patches but after that
[20:01] <bl8> Laney: Banshee 1.7.1 should be out in a week or so : http://banshee-project.org/about/calendar/
[20:02] <didrocks> ok, I'll let on you Laney so for enabling that into maverick :)
[20:02] <Laney> awesome
[20:04] <didrocks> bl8: if you have tips and tricks on how to costumize the interface, I'm interested in any pointers
[20:04] <bl8> didrocks: the code just checks if that file is there, and if yes some stuff is changed here and there. Mostly UI from what I can see
[20:04] <didrocks> oh, let me see
[20:06] <didrocks> bl8: ok, I see, I was first thinking it was something we can control easily with parameters
[20:09]  * didrocks waves goodnight
[20:11] <rickspencer3> night didrocks
[20:11] <rickspencer3> bon nuit
[20:11] <rickspencer3> coffee time for me
[20:16] <rickspencer3> tremolux, hiya
[20:25] <tremolux> rickspencer3: hey Rick, what's up?
[20:27] <Amaranth> hrm, I can't seem to get dpkg-buildpackage to make this compiz package non-native...
[20:27] <Laney> there's usually some output indicating what happened
[20:28] <Amaranth> well, it says the directory compiz-0.8.99 doesn't match compiz-0.8.99+gitblahblahblah
[20:30] <rickspencer3> tremolux, just checking in
[20:30] <rickspencer3> do you know what you need to do this week?
[20:30] <tremolux> rickspencer3: yep, work items  :)
[20:31] <tremolux> rickspencer3: btw, did you get my status report yesterday?
[20:31] <rickspencer3> tremolux, sweet
[20:31] <rickspencer3> tremolux, I did
[20:31] <tremolux> rickspencer3: ok cool
[20:31] <rickspencer3> we usually stick those on the wiki for our team meetings
[20:32] <rickspencer3> but we didn't have one today, so cool that you sent it
[20:32] <tremolux> rickspencer3: sounds good
[20:32] <tremolux> rickspencer3: yeah, I actually looked for the wiki but didn't see it
[20:32]  * tremolux just realized I prolly should have cc'd seb128
[20:33] <mvo> hey Amaranth and Laney
[20:33] <Amaranth> hey mvo
[20:33] <Amaranth> arg still it won't build a .diff.gz
[20:34] <Amaranth>  dpkg-source -b compiz-0.8.99+git20100518+54deec1
[20:34] <Amaranth> dpkg-source: info: using source format `1.0'
[20:34] <Amaranth> dpkg-source: info: building compiz in compiz_0.8.99+git20100518+54deec1-0ubuntu1.tar.gz
[20:34] <Amaranth> but I already have a compiz_0.8.99+git20100518+54deec1.orig.tar.bz2
[20:34] <Amaranth> I've never had it give me this much trouble before
[20:35] <Laney> hiya mvo
[20:36] <Amaranth> oh, it doesn't like the bz2
[20:36] <Laney> never tried it with bz2 before
[20:36] <Laney> but source format 3.0 supports it so it should work
[20:36] <Laney> (if you're using 3.0 of couse)
[20:37] <Amaranth> I guess I should look in to how 3.0 (quilt) works, seeing how we're using quilt for compiz patches
[20:40] <Amaranth> wait, I can just modify the source and build and it'll update the patches? that can't be how this works...
[20:42] <Laney> it's not
[20:44] <Amaranth> oh, I see
[20:44] <Amaranth> I keep using quilt to manage patches during development but dpkg-source applies them at build time instead of quilt
[20:44] <Amaranth> eh, why not
[21:07] <Amaranth> yay it builds
[21:35] <ccheney> Amaranth: 3.0 is very nice once you get used to how it works
[21:57] <Amaranth> There, now all the patches I've ported to 0.9 also have proper DEP-3 tags
[21:58] <Amaranth> Just need to port a couple more patches and I'll have core packaged completely
[21:59] <Amaranth> ccheney: So far the main gotcha is that it automatically applies the patches when extracting the source and doesn't remove them when cleaning
[21:59] <ccheney> Amaranth: yea you can use a flag to avoid the unpack if you want, but it doesn't remove them on cleaning thats true
[21:59] <ccheney> Amaranth: you can use quilt pop to do that though
[22:00] <ccheney> Amaranth: er not unpack, to avoid applying the patches i mean
[22:00] <Amaranth> yeah, I just have to remember to quilt pop -a
[22:00] <ccheney> yea
[22:01] <ccheney> i'm still getting used to it on OOo, but it is much easier to deal with packaging with it along with multiple source file support
[22:01] <ccheney> OOo has around 5 source tarballs now, heh
[23:31] <TheMuso`> Good morning.
[23:34] <RAOF> Good morning
[23:41] <TheMuso`> RAOF: How are you feeling this morning? Somewhat less tired? :)
[23:41] <RAOF> Yup.  And less sick, to boot!
[23:41] <RAOF> Hows about you?
[23:41] <TheMuso`> Much better thanks. I had a bit of a headache, and got hot/cold flushes yesterday, and have developed a cough. Everything but the cough has gone.
[23:42] <TheMuso`> DIdn't help that I didn't sleep well Monday night, which probably helped trigger most of this.
[23:42] <TheMuso`> At least a panadol put a cap on the headache.
[23:46] <crimx> nautilus removing the location text/button switch button is crap.. having to ctrl-l/esc to toggle it is annoying! they should put the button back!
[23:59] <rickspencer3> Hi RAOF, TheMuso
[23:59] <TheMuso> Hey rickspencer3.
[23:59] <RAOF> rickspencer3: Good morning