[00:01] <jasoncwarner> morning bryce, RAOF, TheMuso and robert_ancell
[00:01] <jasoncwarner> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-05-24
[00:01] <jasoncwarner> ready?
[00:01] <RAOF> And rearing to go.
[00:02] <jasoncwarner> :)
[00:02] <cyphermox> o/
[00:02] <jasoncwarner> awesome...
[00:02] <bryce> heya
[00:03] <jasoncwarner> robert_ancell might still be ill, was hoping he was here.
[00:03] <bryce> wow, still?
[00:03] <bryce> poor guy
[00:03] <jasoncwarner> there is a western edition todo to talk about bzr usage (see wiki)
[00:03] <jasoncwarner> bryce: yeah...hope he is all better soon...
[00:03] <TheMuso> Hey folks.
[00:04] <bryce> jasoncwarner, so we're going to switch xorg packaging from git to bzr?
[00:04] <bryce> ;-)
[00:04] <TheMuso> No I think the bzr stuff is for gnome packaging.
[00:04] <jasoncwarner> pitti told me SVN to store it and hg-svn to do your local work
[00:04] <jasoncwarner> no?
[00:04] <jasoncwarner> :)
[00:04] <RAOF> :)
[00:04] <bryce> I'll use the CVS-svn interface
[00:05] <bryce> seriously though, I do hate git
[00:05] <TheMuso> lol
[00:05] <jasoncwarner> Ok...for realz though.
[00:05] <jasoncwarner> lets get through the meeting and then we can discuss when robert feels better :)
[00:06] <jasoncwarner> [TOPIC] X update
[00:06] <RAOF> I think that all our blueprints are approved and ready to go.
[00:07] <RAOF> And bryce has re-targeted our versions-tracking infrastructure at oneiric (thanks!)
[00:07] <bryce> I see xserver 1.11 has _already_ broken api
[00:07] <RAOF> You know what they say - break early, break often!
[00:08] <bryce> yeah I need to rewrite that script in python and have it auto-probe the ubuntu version so I don't have to manually fiddle with it every release
[00:08] <bryce> RAOF, (I don't think they really say that)
[00:08] <TheMuso> IMO it should be break early, break once.
[00:09] <bryce> there's now an x-backports ppa set up in ubuntu-x-swat
[00:09] <RAOF> bryce: Anything more to talk about re: Mesa switching to an SRU-friendly point release policy?
[00:09] <bryce> timo and sarvatt will be filling it in as we go
[00:10] <bryce> oh yeah, I went up to Intel in hillsboro for a meeting with Keith Packard and the graphics team last week
[00:11] <bryce> they're thinking about trying to do point releases of mesa and keeping it stable, in hopes we could pull in point release updates to mesa post-release
[00:11] <bryce> I explained our sru policies wrt point release updates, so guess we'll see how they do
[00:11] <bryce> they were very encouraging of doing more bug upstreaming too
[00:12] <bryce> so this week I've been mostly hammering on my upstreamer tool stuff in arsenal to try to get it more functional
[00:12] <bryce> Intel's development process has changed, too; they're becoming much more distro focused in terms of when they consider hardware support "available"
[00:13] <bryce> so sounds like Gen7 hw (Iron Lake?) will be a smoother transition than Sandybridge was
[00:13] <RAOF> IvyBridge.
[00:13] <bryce> Ivy Bridge, right!
[00:13] <bryce> anyway, I also inquired about getting us some HW
[00:13] <TheMuso> Yeah was reading about IvyBridge and the inclusion of Thunderbolt the other day.
[00:14] <bryce> which turned out that Intel interfaces with pgraner
[00:14] <RAOF> Yeah.  Those chips are due out around the end of the year, and the kernel support for them has landed, as has some mesa bits.  There should be time for solid testing before the distro release season :)
[00:15] <bryce> they said they have to ship to a biz address, so the systems get sent to Lexington and I guess parcelled out from there
[00:15] <bryce> RAOF, anyway I figure either you or I should bug pete about ensuring we're somewhere on the list to get one so we can do gfx testing
[00:16] <RAOF> Yes!
[00:16] <RAOF> It's probably significantly cheaper to ship Lexington → Portland :(
[00:16] <RAOF> (Than Lexington → Hobart)
[00:17] <bryce> heh
[00:17] <jasoncwarner> anything else you guys want to talk about?
[00:17] <RAOF> When can we expect oneiric to not look like arse? :)
[00:18] <jasoncwarner> uhm...uhm....
[00:18] <jasoncwarner> uhm...
[00:18] <RAOF> Heh.
[00:18]  * TheMuso is pondering upgrading to oneiric this week, but not sure how badly things will break. Might try a VM first.
[00:19] <jasoncwarner> Ok...do you guys want to wait for robert before talkign about bzr or do you want to go ahead and talk about it and catch him up?
[00:19] <TheMuso> So I can at least make sure accessibility won't break when I upgrade for real.
[00:19] <bryce> oh, there is one thing...  while we're escaping nvidia/fglrx breakage due to xserver abi breakage, what about the kernel?
[00:20] <bryce> bug #776895
[00:20] <ubot2> Launchpad bug 776895 in fglrx-installer "fglrx 2:8.840-0ubuntu4 fails to build against 2.6.39 kernels, due to missing linux/smp_lock.h" [High,Triaged] https://launchpad.net/bugs/776895
[00:20] <RAOF> Oh, yeah!  fglrx doesn't build without the big kernel lock!
[00:20] <RAOF> Urgh.
[00:20] <TheMuso> Re bzr, I don't mind either way. The vast majority of stuff I package either doesn't have a packaging branch in bzr, or has branches maintained for Ubuntu in Debian vcs.
[00:21] <TheMuso> The latter suiting me just fine.
[00:21] <TheMuso> So whatever is decided, I can work with, if it affects me.
[00:22] <TheMuso> I guess I have a question for you X guys, somethign that doesn't affect me, but people from the community may be asking about. What about bumblebee and oneiric, what will your official position be?
[00:22] <kinouchou> desrt: hello
[00:22] <bryce> TheMuso, might affect us via sponsors queue work and such
[00:22] <RAOF> TheMuso: bumblebee?  (/me googles)
[00:23] <TheMuso> RAOF: A little piece of software to help users with NVIDIA optimus make use of both video chips in a way.
[00:23] <bryce> hybrid graphics eh?
[00:23]  * TheMuso doesn't plan to try it, as I am one of the fortunate ones who can turn on/off whatever video chip I need.
[00:23] <TheMuso> Something like that.
[00:23] <TheMuso> Not as automatic as in Windows, but users can manually choose to run certain apps on the intel or NVIDIA chips.
[00:24] <bryce> TheMuso, I'd like to see us with a more cohesive solution to hybrid graphics before we start officially supporting it
[00:24] <TheMuso> SO I am just thinking ahead about people asking for it etc.
[00:24] <TheMuso> bryce: Right, I thought as much, but I am thinking about what the community may ask for.
[00:24] <bryce> I'm worried there's going to be a lot of different one-off "solutions" which are going to make support complicated in the near term
[00:24] <TheMuso> Again, I don't care, doesn't  affect me, I work around it by using intel only.
[00:25]  * TheMuso nods.
[00:25] <RAOF> So, my position would be that the *correct* solution is Dave Airied's gpu buffer sharing + other work.
[00:25] <bryce> what we're hoping is that these different options will compete and the field will narrow as less good options die off
[00:25] <TheMuso> Right.
[00:26] <bryce> but for oneiric I think our hybrid graphics plans are <undefined>
[00:26] <RAOF> I don't think I'd object to something like bumblebee in the archive, though.
[00:26] <TheMuso> Yeah, undefined is what I thought.
[00:26] <bryce> it would be great to see some community involvement in pushing things like bumblebee forward
[00:29] <TheMuso> Ok cool that satisfies my curosity.
[00:29] <TheMuso> curiosity even.
[00:29] <RAOF> Hm.  Although obviously before bumblebee can be uploaded it'll need to build from source :)
[00:29] <bryce> am I remembering correctly RAOF that you asked Rick for hybrid HW?
[00:30] <RAOF> bryce: Yes, I did.  Well, I ended up asking Pete and then Chris; there's apparently one spare after UDS.
[00:30] <bryce> good deal, maybe you can arrange to take possession at the sprint ;-)
[00:31] <bryce> RAOF, looks like sarvatt has a fix for bug 776895, so that should resolve the kernel breakage.  But I do worry about it generally.
[00:31] <ubot2> Launchpad bug 776895 in fglrx-installer "fglrx 2:8.840-0ubuntu4 fails to build against 2.6.39 kernels, due to missing linux/smp_lock.h" [High,Triaged] https://launchpad.net/bugs/776895
[00:33] <jasoncwarner> I have to step out for a bit...be back later.
[00:33] <RAOF> I wonder whether that will introduce crazy races; dropping the BKL means that fglrx will be subjected to things possibly changing under it.
[00:34] <RAOF> I'm not sure what we can do about the kernel breakage in general, though.
[00:35] <RAOF> Oh, boo.  Evolution no longer starts :(
[00:35] <bryce> hmm
[00:36] <bryce> well, maybe we can make jockey not offer the driver
[00:36] <TheMuso> Are there any current radeon GPUs that are not supported by the open driver yet?
[00:36] <RAOF> Oh, right.
[00:36] <RAOF> TheMuso: I don't believe so, no.
[00:37] <Sarvatt> HD 69xx
[00:38] <TheMuso> ah ok.
[00:38]  * RAOF needs to remember that patches for HD 69xx support being committed is not the same as HD69xx support existing in a release :)
[00:55] <desrt> kinouchou: bonjour!
[00:58] <kinouchou> :)
[00:58] <kinouchou> how are you?
[00:58] <desrt> good, actually.  just woke from a nap which i took because i had a headache.  headache is gone. :)
[00:59] <kinouchou> i have many headache
[01:00] <desrt> you need more naps, clearly
[01:00] <kinouchou> yes
[01:01] <desrt> the bad news is that my girlfriend has stolen my ubuntu.fr pin
[01:01] <desrt> she says that it reminds her of the 80s
[01:01] <kinouchou> :(
[01:02] <kinouchou> I have 2000 ubuntu-fr pin but in France
[01:02] <desrt> where are you now?
[01:03] <kinouchou> at home near Paris
[01:03] <desrt> ah.  it sounded like you were somewhere else.
[01:04] <kinouchou> i say that because I can't give you a new pin
[01:04] <desrt> clearly the solution is for me to come to paris.  see you soon.
[01:05] <kinouchou> yep
[01:06] <desrt> okay.  i've booked my flight.  i arrive in 1 month exactly.
[01:11] <kinouchou> desrt: bonne nuit, i go to sleep
[01:12] <desrt> good night
[01:12] <desrt> see you in 1 month
[01:12] <kinouchou> ok, i wrote in my calendar
[01:13] <desrt> ta
[01:23] <micahg> anyone want to fix librsvg again?
[01:26] <TheMuso> micahg: Whats up with it?
[01:26] <micahg> TheMuso: same problem, one more substitution needed in the postinst
[01:27] <micahg> TheMuso: multiarch dir not being accessed
[01:27] <TheMuso> micahg: If you have a patch, I'm happy to sponsor.
[01:27] <micahg> TheMuso: k, give me a minute
[01:27] <TheMuso> Sure.
[01:31] <andersk> http://web.mit.edu/andersk/Public/ubuntu/librsvg_2.34.0-0ubuntu3_multiarch.debdiff
[01:31] <micahg> andersk: no, that's not right, the non-multiarch path shouldn't be in the second line
[01:31] <andersk> It is in libgdk-pixbuf2.0-0.postinst.
[01:32] <micahg> andersk: you'll get the same error again since the dir doesn't exist
[01:32] <micahg> I'm about to test the fix
[01:32] <andersk> It does for me, since libwmf0.2-7-gtk has /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/io-wmf.so.
[01:33] <andersk> If that’s going to go away, I guess libgdk-pixbuf2.0-0 needs to be fixed again too.
[01:34] <micahg> andersk: yes, but not everyone will have that installed and yes, it's going away with the multiarch transition
[01:37] <andersk> If I remove libwmf0.2-7-gtk, I get an error that /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/*.so doesn’t exist, but at least the entire command doesn’t fail.
[01:38] <andersk> But I assume you’re in the middle of writing something smarter, so I’ll let you go ahead with that.
[01:38] <micahg> yeah, just trying to test
[01:40] <micahg> TheMuso: http://paste.ubuntu.com/612527/, I can give you a bug if you want
[01:41] <andersk> But that will break libwmf0.2-7-gtk, right?
[01:43] <micahg> andersk: probably, but it should be fixed in any case
[01:43] <TheMuso> micahg: If there is a bug for it, it would help to close it, otherwise there is no problem.
[01:43] <micahg> TheMuso: I see one from the old issue, not for the ubuntu3 specific issue
[01:44] <micahg> andersk: well, it shouldn't actually break it, it just won't load the stuff from that library
[01:44] <andersk> libgdk-pixbuf2.0-0.postinst looks in both directories and uses 2>/dev/null to suppress the warning if the older path goes away.
[01:44] <TheMuso> micahg: Ok then don't worry about it, I'll just upload as is.
[01:44] <TheMuso> micahg: So you tested and it worked?
[01:45] <micahg> TheMuso: yeah, let me just check with slangasek about what andersk is asking
[01:45] <TheMuso> Ok.
[01:52] <andersk> I updated my patch to add the 2>/dev/null, if that’s the route you want to take.  I think it makes sense, because this is supposed to do the same thing as libgdk-pixbuf2.0-0.postinst.
[01:55] <TheMuso> Ok so what needs changing in that patch that was patebinned?
[01:55] <TheMuso> Haven't looked much into multi-arch myself just yet.
[01:58] <micahg> andersk: have you tested your version?
[01:59] <andersk> Yeah, just did, it works.
[02:00] <micahg> TheMuso: ok, let's go with his solution, I'd rather 2 checks for this and not suppress errors, but that would diverge from what's currently being done, so it should be discussed
[02:04] <TheMuso> Ok.
[02:05] <TheMuso> So where do I find that patch, or do I misread, and we are leaving it for now?
[02:05] <micahg> http://web.mit.edu/andersk/Public/ubuntu/librsvg_2.34.0-0ubuntu3_multiarch.debdiff
[02:05] <TheMuso> Ok thanks.
[02:11] <TheMuso> andersk: Ok thanks for your patch, the package seems to build ok, uploading now.
[03:23] <TheMuso> c
[05:28] <pitti> Good morning
[05:32] <TheMuso> Hey pitti.
[05:32] <TheMuso> c
[06:44] <braiam> hey pitti!
[06:47] <pitti> hey braiam
[07:19] <didrocks> good morning
[07:20] <pitti> bonjour didrocks
[07:20] <didrocks> guten morgen pitti!
[07:24] <ricotz> pitti, hello
[07:24] <pitti> hey ricotz
[07:24] <ricotz> the gnome-keyring build still fail at the exact same position in the ppa
[07:24] <ricotz> locally it builds fine in a natty pbuilder
[07:25] <pitti> here as well, I build it three or four times on current oneiric
[07:25] <ricotz> i have no idea what is causing this :(
[07:25] <ricotz> pitti, btw, dont forget a dep on libarchive-dev for libtotem-plparser-dev
[07:26] <pitti> ricotz: yes, I added it, and bumped libquvi-dep
[07:26] <pitti> -dev even
[07:26]  * pitti diffed configure.in to see
[07:26] <pitti> just uploaded to sid
[07:26] <ricotz> hmm, you did?
[07:26] <ricotz> i dont see the dep here
[07:27] <pitti> and if http://svn.debian.org was working I could show you..
[07:27] <ricotz> i mean the -dev itself needs to depend on it
[07:27] <pitti> oh, to the -dev
[07:27] <ricotz> this might cause pkg-config to fail, i have been there :(
[07:28] <pitti> why?
[07:28] <pitti> Requires: glib-2.0 gobject-2.0 gio-2.0
[07:28] <pitti> Requires.private: gthread-2.0 libxml-2.0 gmime-2.4 libquvi libarchive
[07:28] <didrocks> hey ricotz
[07:28] <pitti> it's only an internal dependency
[07:28] <pitti> it should only depend on the "Requires" -devs, no?
[07:28] <ricotz> pitti, hmm, for the missing libquiv it fail the last time
[07:29] <ricotz> pitti, see 2.32.4-2
[07:29] <ricotz> didrocks, hey
[07:29] <pitti> that seems like the kind of thing which would cause unnecessary library dependencies in packages which use libtotem-plparser-dev?
[07:29] <pitti> ricotz: anyway, I'm happy to add it if it causes problems
[07:30] <ricotz> the last time it caused a build failure of totem
[07:30] <TheMuso> pitti: Yeah git.debian.org is not working for me, something to do with a read-only filesystem.
[07:31] <pitti> TheMuso: svn works, but websvn isn't back up yet (or might never be again, not sure)
[07:32] <pitti> ricotz: I don't see anythign libarchive-ish in the header files; could that be due to a build system bug? why would totem need libarchive?
[07:33] <ricotz> pitti, oh, meant while the libquvi-dev reference was missing the last time it causes the totem build to fail
[07:33] <ricotz> which i assume could be the same while missing the libarchive-dev now
[07:34] <pitti> ricotz: hm, if it fails now, I'd rather fix that properly, I think
[07:34] <ricotz> if you remove libarchive-dev, what does pkg-config outputs?
[07:35] <ricotz> assuming you already updated totem-pl-parser locally
[07:35] <pitti> argh, meh
[07:35] <pitti> $ pkg-config --cflags totem-plparser
[07:35] <pitti> Package libarchive was not found in the pkg-config search path.
[07:36] <pitti> dear pkg-config, this really sounds broken
[07:36] <pitti> ok, I'll add it then
[07:36] <pitti> thanks for pointing out
[07:36] <ricotz> yes :\
[07:40] <ricotz> you're welcome
[07:43] <pitti> fix uploaded and committed
[08:16] <geser> pitti: try http://anonscm.debian.org/ (see http://lists.debian.org/debian-devel-announce/2011/05/msg00009.html)
[08:17] <geser> TheMuso: ^^ this applies for git.debian.org too
[08:17] <pitti> geser: ah, thanks
[08:17] <pitti> geser: that's a bit of a shame, though, it'll break hundreds of Vcs-Browser: tags in source packages :/
[08:17] <pitti> http://anonscm.debian.org/viewvc/pkg-gnome/ -> empty :/
[08:20] <geser> pitti: not only Vcs-Browser but all Vcs-* tags as the read-only access changed too
[08:44] <Laney> I don't think it's finalised yet
[08:45] <Laney> i.e. I expect the old links to be restored
[08:50] <seb128> hey
[08:50] <pitti> bonjour seb128
[08:50] <seb128> hey pitti, how are you?
[08:51] <pitti> pretty well, thanks!
[08:51] <pitti> how about you?
[08:52] <pitti> have banged on versions.html a little, some less bright orange there
[08:52] <seb128> I've fine thanks
[08:52] <seb128> versions> great
[08:53] <seb128> the "to update" almost fit on one page now ;-)
[08:54] <ricotz> pitti, is the script which is doing this page available somewhere?
[08:54] <ricotz> seb128, hello
[08:54] <pitti> ricotz: lp:~ubuntu-desktop/+junk/versions or something
[08:54] <ricotz> pitti, thanks
[08:56] <seb128> ricotz, it's written at the bottom on the webpage
[08:57] <didrocks> salut seb128!
[08:57] <seb128> lut didrocks, ca va ?
[08:57] <didrocks> seb128: ça va bien, et toi ?
[08:57] <seb128> ca va nickel ;-)
[08:57] <ricotz> seb128, ahh ;), should have scrolled down this far :\
[08:58] <seb128> ricotz, you have a key on your keyboard sending you at the bottom :p
[08:58] <seb128> ricotz, do you want to use it for the ppa or something?
[09:00] <ricotz> seb128, hehe
[09:00] <ricotz> seb128, yes, i was hoping to get a better overview
[09:02] <rodrigo_> morning
[09:02] <didrocks> hey rodrigo_
[09:02] <seb128> hey rodrigo_
[09:03] <seb128> didrocks, can you get bug #779717 reviewed?
[09:03] <ubot2> Launchpad bug 779717 in indicator-multiload "indicator-multiload causes a memory leak in compiz when run under unity" [High,Confirmed] https://launchpad.net/bugs/779717
[09:04] <seb128> it has a valgrind log of a IndicatorObjectEntryProxyRemote::GetPixbuf() leak and some patches
[09:04] <didrocks> seb128: sure
[09:04] <seb128> didrocks, the leak is in unity, the bot picked the wrong component
[09:04] <seb128> didrocks, thanks
[09:05] <pitti> oh nice, Michael found a fix?
[09:05] <pitti> (he's a friend of mine who talked to me about this recently)
[09:05] <seb128> oh, that explains the piware email ;-)
[09:06] <seb128> pitti, he got some patches on the bug at least
[09:06] <seb128> the issue is that dx is so behind on bugs that they probably don't see comments or patches coming
[09:06] <rodrigo_> bonjour didrocks, seb128
[09:07] <rodrigo_> so, seems dns is failing a lot these last few days?
[09:07] <seb128> not here
[09:08] <rodrigo_> hmm, not sure what's up, but I get a lot of disconnections
[09:08] <seb128> didrocks, seems bug #758248 is the same and jay is on it?
[09:08] <ubot2> Launchpad bug 758248 in nux "memory leaking in compiz" [Medium,Triaged] https://launchpad.net/bugs/758248
[09:09] <seb128> didrocks, see comment #32
[09:09] <didrocks> seb128: this is the "most extreme" from it, isn't it?
[09:10] <seb128> not sure but seems there is different leaks
[09:10] <seb128> the fix from jay is in nux, the patches from michael in unity
[09:10] <didrocks> seb128: I think mdz's bug showed other issues in nux
[09:10] <seb128> so worth getting the set reviewed
[09:10] <didrocks> yeah
[09:11] <seb128> njpatel, ^ could be worth reading for you as well
[09:13] <njpatel> seb128, are all the patches on that bug?
[09:14] <seb128> njpatel, #779717 has 2 patches from pitti's friend
[09:14] <seb128> njpatel, the other bug has a comment from jay added yesterday saying he has a fix in nux 0.9
[09:14] <seb128> the set seems worth reviewing in context of one of the sru rounds
[09:15] <didrocks> njpatel: just ensure that the team look at the pending merge, it should be ok then
[09:16] <chrisccoulson_> good morning everyone
[09:18] <didrocks> hey chrisccoulson_!
[09:19] <chrisccoulson_> hi didrocks, how are you?
[09:19] <didrocks> chrisccoulson: I'm fine, thanks, and you?
[09:19] <chrisccoulson> yeah, good thanks
[09:19] <chrisccoulson> i'm just wondering whether to do a dist-upgrade right now. i've not done any updates since i upgraded to oneiric last week
[09:20] <rodrigo_> seb128, just to make sure, updating eog to 3.0.2, so the version should be 3.0.2-0ubuntu1, right?
[09:21] <seb128> hey chrisccoulson, isn't today an uk holiday? ;-)
[09:21] <seb128> rodrigo_, yes
[09:23] <chrisccoulson> seb128, unfortunately not today ;)
[09:24] <seb128> ;-)
[09:26] <chrisccoulson> the amount of packages on https://wiki.ubuntu.com/MozillaTeam/FirefoxUpgradeChecklist/5.0 is really depressing
[09:27] <chrisccoulson> i need to think of a way to kill off the extensions on lucid and maverick
[09:29] <chrisccoulson> hmmm, it seems that globalmenu-extension is broken again in firefox 7
[09:32] <geser> firefox is at version 7 already?
[09:34] <chrisccoulson> geser, yes, on mozilla-central
[09:34] <chrisccoulson> https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+build/2524747
[09:34] <chrisccoulson> 7 is probably what oneiric will get
[09:44] <TheMuso> geser: I was trying to push via ssh, not pull.
[09:57] <seb128> rodrigo_, hey
[09:57] <seb128> ups
[09:57] <seb128> didrocks, hey
[09:57] <seb128> ubuntu.session ->
[09:57] <seb128> RequiredProviders=windowmanager;panel;file-manager;
[09:57] <didrocks> hey seb128 :)
[09:57] <seb128> DefaultProvider-file-manager=nautilus
[09:57] <seb128> can I drop the DefaultProvider-file-manager line and the ;file-manager RequiredProviders?
[09:58] <seb128> it's what is opening a nautilus dialog on login I think
[09:58] <seb128> the new nautilus also has an autostart desktop for that now
[09:58] <didrocks> seb128: sure, but we should ensure what to do for finale
[09:58] <seb128> well that doesn't change
[09:58] <didrocks> hum, so it's autostarted in /etc/xdg/autostart/ ?
[09:58] <seb128> they moved from a component to an autostart
[09:59] <seb128> didrocks, yes, with a conditional start on a gsettings key
[09:59] <didrocks> ok, perfect then :-)
[09:59] <didrocks> doing that now
[09:59] <seb128> so deciding what to do is just deciding on the key value
[09:59] <seb128> didrocks, I'm doing it
[09:59] <seb128> didrocks, don't bother
[09:59] <didrocks> ok, thanks :-)
[09:59] <seb128> I just wanted to check with you I was not overlooking something
[09:59] <didrocks> seb128: you should do it as well for the ubuntu-2d.session
[09:59] <seb128> didrocks, thanks ;-)
[09:59] <seb128> ok
[10:00] <didrocks> the other, I didn't touch to get the upstream experience
[10:00] <didrocks> thanks seb128 :)
[10:10] <cdbs> didrocks: hi, did 3.8.14 get postponed (again) ?
[10:11] <didrocks> cdbs: why again?
[10:11] <cdbs> didrocks: I didn't see a release, did it get released yesterday?
[10:11] <didrocks> cdbs: it was planned yesterday, right, but as I wrote in the desktop team report, it will be later this week
[10:11] <cdbs> hmm
[10:11] <didrocks> cdbs: but it has never been planned before, hene the "again"?
[10:11] <didrocks> hence*
[10:12] <cdbs> didrocks: Well I thought it was, as you had said so :)
[10:12] <didrocks> cdbs: when did I say that? I didn't AFAIK
[10:12] <didrocks> just that it was planned yesterday
[10:12] <didrocks> and I told yesterday that it will be later this week, in the desktop team meeting
[10:13] <cdbs> didrocks: Okay, I really should read the meeting logs or so
[10:13] <didrocks> cdbs: and in the report: https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-05-24
[10:13] <cdbs> this timezone is sucky
[10:13] <didrocks> cdbs: yeah, you should have a look, we tend to put all info there :)
[10:13] <didrocks> at least, try!
[10:13] <didrocks> (I won't sign for completeness there :-p)
[10:14] <didrocks> cdbs: however, I don't know if there is a direct link to always "the latest report"
[10:15] <cdbs> That's not a problem
[10:15] <cdbs> atleast not for me. I can check out regularly, like, every Monday
[10:16] <didrocks> yeah, I'm wondering still if we should have such link, nevermind anyway :-)
[10:30] <didrocks> shankao: hey, so you had some questions on the last gnome-session update?
[10:30] <shankao> hi, after the last gnome-session upgrade, for some reason gnome-session-fallback was not in my system, so the ubuntu-classic option was not selectable
[10:30] <shankao> is maybe a dependency problem?
[10:30] <didrocks> shankao: did you get the latest gnome-panel?
[10:30] <didrocks> shankao: gnome-panel recommends gnome-session-fallback
[10:30] <didrocks> so people upgrading will get it that way
[10:31] <didrocks> new install won't as gnome-panel won't be seeded
[10:31] <shankao> nope, I was upgrading
[10:31] <shankao> I have installed the missing package by hand now
[10:32] <shankao> anyway I can take a deeper look at why it was left this way
[10:32] <didrocks> shankao: gnome-panel 1:2.32.1-0ubuntu7 recommends gnome-session-fallback, so if you install recommends (which is the default), it will be installed
[10:32] <didrocks> so yeah, more clue will be appreciated :-)
[10:33] <shankao> ok, my version is gnome-panel 1:2.32.1-0ubuntu6.5
[10:33] <didrocks> shankao: seems that explains it then :-)
[10:34] <shankao> yep, thanks :)
[10:34] <didrocks> yw!
[10:37] <shankao> umh, seems that version of gnome-panel (ubuntu7) is Dependency wait on vernadsky (i386)
[10:38] <shankao> https://launchpad.net/ubuntu/+source/gnome-panel/1:2.32.1-0ubuntu7/+build/2523117
[10:40] <pitti> jasoncwarner: https://blueprints.launchpad.net/ubuntu/oneiric/+specs?searchtext=desktop-o
[10:45] <geser> didrocks: can you look at the depwait shankao pointed about? gnome-panel depwaits on libedataserverui1.2-dev but there is only libedataserverui-3.0-dev (and libedataserver1.2-dev)
[10:46] <didrocks> geser: I think we rather should work on migrating gnome-panel to 3.0
[10:46] <didrocks> geser: not sure I can do it today, already on other stuff, but will give a look if nobody take it
[10:48] <geser> didrocks: no problem, I just wanted you to know about the depwait as they can get easily unnoticed
[10:48] <didrocks> geser: yeah, it was unnoticed TBH :-) thanks for pointing it shankao, geser!
[10:49] <LetoThe2nd> hello! as of release 11.04, unity seems to crash(segfault) if xinerama is enabled. is this a know issue? or shall i open a bug once i got all information collected?
[10:49] <seb128> didrocks, we should perhaps make gnome-session recommends -fallback until the e-d-s gnome-panel thing is sorted
[10:49] <didrocks> seb128: well, do you think we won't do it for alpha1?
[10:50] <didrocks> for e-d-s/gnome-panel
[10:50] <seb128> didrocks, what, updating gnome-panel? not if that involve going to gtk3 and updating the indicator stack
[10:51] <didrocks> seb128: I can maybe try to build it with libedataserverui-3.0-dev first and se what happens
[10:51] <didrocks> but I really want to first do this unity-2d sortage
[10:51] <pitti> chrisccoulson: do you have a minute to hop into mumble, desktop 1-1?
[10:52] <chrisccoulson> pitti - yeah, i just need to find my headset
[10:52] <chrisccoulson> 1 second
[10:52] <seb128> didrocks,
[10:52] <seb128> $ ldd /usr/lib/libedataserverui-3.0.so.0.0.0 | grep gtk
[10:52] <seb128> 	libgtk-3.so.0 => /usr/lib/libgtk-3.so.0 (0x005af000)
[10:53] <seb128> didrocks, not likely to work with a gtk2 gnome-panel
[10:53] <LetoThe2nd> some more details: three 1080p-displays connected via 2 HD4350 boards, everything working fine when using gnome classic
[10:53] <didrocks> seb128: didn't you want to test gtk2/gtk3 linking to the same process? :-) maybe time to experiment!
[10:53] <seb128> didrocks, that's why debian renamed the e-d-s source to have both gtk2 and gtk3 version in the archive until they go to testing
[10:53] <seb128> didrocks, ;-)
[10:54] <didrocks> seb128: more seriously, recommends for alpha1 sounds good then…
[10:55] <didrocks> we should just drop a note that we will have to revert once g-p ready
[10:56] <seb128> didrocks, do you want me to do it?
[10:57] <chrisccoulson> hmmm, pitti, i have no sound coming from my headset at all :/
[10:57] <didrocks> seb128: no, it's ok, I'll do it by eod :-)
[10:57] <chrisccoulson> i haven't tried using mumble on oneiric before today ;)
[10:58] <pitti> chrisccoulson: nevermind, I'll IRC you later
[10:58] <seb128> didrocks, ok
[10:58] <chrisccoulson> pitti - sorry about that. i'll try and figure out what's wrong with it here
[10:58] <kinouchou> hello seb128 didrocks and fredp
[10:59] <didrocks> hey kinouchou
[10:59] <seb128> chrisccoulson,  you are right; I would be afraid of management asking me to come do a 1:1 on mumble as well, it usually means they want to kick you out or something ;-)
[10:59] <seb128> lut kinouchou
[10:59] <didrocks> seb128:   * debian/nautilus.install:
[10:59] <didrocks>     - install the new autostart desktop entry
[10:59] <didrocks> ahah, so it wasn't installed? :-)
[10:59] <seb128> oh, fredp is there, hey, can you update yelp-xsl to debian? ;-)
[10:59] <pitti> chrisccoulson: basically jasoncwarner and I were wondering what's missing for https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-default-email-client
[11:00] <seb128> didrocks, it wasn't there, they added it to 3.0.2 following my email to the list
[11:00] <fredp> hey kinouchou
[11:00] <pitti> chrisccoulson: it's got a ton of WIs, and the criteria for "yay or nay" seem to be reasonably clear?
[11:00] <fredp> seb128: sure I can
[11:00] <jasoncwarner> hey chrisccoulson...when is our thunderbird meeting? It's today, right?
[11:00] <seb128> didrocks, they didn't have one until now since GNOME3 doesn't start nautilus
[11:00] <chrisccoulson> jasoncwarner, yeah, it's today
[11:00] <didrocks> seb128: ok, nice then :-)
[11:00] <seb128> didrocks, I asked a "what about having one conditional on the gsettings key for those who want to turn it on"
[11:00] <chrisccoulson> pitti - do you know who added all the bugs to that blueprint?
[11:00] <seb128> ;-)
[11:00] <chrisccoulson> is it just users who are trying to get my attention on their favourite bugs?
[11:00] <didrocks> seb128: heh, nice move!
[11:00] <seb128> hey jasoncwarner
[11:01] <jasoncwarner> hey seb128!
[11:01] <pitti> chrisccoulson: no, I don't; they count as WIs, so if some are irrelevant, please unlink them
[11:01] <chrisccoulson> pitti - i didn't add any of them, so i might unlink them all
[11:01] <pitti> jasoncwarner: also, is there any interesting dicussino left in the whiteboard? this calls for some cleanup
[11:01] <didrocks> seb128: should be part of the d-d-l discussion I'm ignoring for time saving :)
[11:01] <chrisccoulson> i think they were just added by users as a way of waving them in my face ;)
[11:01] <seb128> didrocks, no, it was on the nautilus list
[11:02] <jasoncwarner> it would be nice to archive the discussion if possible, but clean up is in order...I don't know if any is really relevant at this point.
[11:02] <didrocks> ok, no way I would discover it then :)
[11:02] <seb128> (so my secret plan to undermine tb by default by adding lot of random bugs to the blocker list is not working...)
[11:02] <chrisccoulson> yeah, the whiteboard is a bit of a mess now
[11:02] <seb128> ;-)
[11:02] <pitti> chrisccoulson: so from my POV the whiteboard and description need cleanup, and if you don't use bugs as WIs, it'll need actual WIs
[11:02] <seb128> bugs as work items--
[11:02] <chrisccoulson> pitti - yeah. i guess the WI's will probably come out of todays meeting
[11:03] <jasoncwarner> seb128: what if we made gmail by default in chrome instead? would that suit you more?  ;)
[11:03] <pitti> seb128: in some particular cases they are quite nice actually
[11:03] <pitti> chrisccoulson: ah, so let's wait until after that then
[11:03] <seb128> jasoncwarner, I'm fine with that ;-)
[11:03] <chrisccoulson> i'm going to remove the bug links unless someone shouts out now :)
[11:03] <seb128> jasoncwarner, I like bold moves ;-)
[11:03] <pitti> chrisccoulson: they really look like normal tbird bugs indeed
[11:03] <seb128> evo to tb is just boring :p
[11:03] <pitti> mutt! *cough*
[11:03] <jasoncwarner> seb128: ha! fair enough!
[11:03] <rodrigo_> didrocks, so, gnome-icon-theme-symbolic is now accepted in main?
[11:03] <jasoncwarner> pitti: emacs
[11:03] <jasoncwarner> pitti: mutt w/ emacs bindings?
[11:04] <jasoncwarner> pitti: just to confuse your muscle memory
[11:04] <didrocks> rodrigo_: yeah, and I promoted it
[11:04]  * didrocks checks with rmadison
[11:04] <rodrigo_> ok, cool!
[11:04] <chrisccoulson> pitti - is there any way of viewing the activity history on a blueprint? (like there is with a bug report)
[11:04] <didrocks> rodrigo_: indeed :)
[11:04] <chrisccoulson> +activity doesn't seem to be valid
[11:04] <pitti> jasoncwarner: actually it'd help to reduce my daily two hours that I spend on email -- I'd just accidentally delete them all :)
[11:04] <pitti> chrisccoulson: no, I don't think there is
[11:05] <jasoncwarner> pitti: lol
[11:05] <chrisccoulson> ok, cleaned :)
[11:11] <pitti> rodrigo_: hm, seems the control-center thread on d-d pretty much died down -- are you aware of a practical solution to this now?
[11:11] <rodrigo_> pitti, the public/private lib thing?
[11:11] <pitti> rodrigo_: there was a faint compromise proposal about upstream allowing distros to add well-defined and specific panels, but not arbitrary ones; that would work for us, WDYT?
[11:12] <pitti> rodrigo_: that, and adding new panels in general
[11:12] <rodrigo_> yes, there's still discussion internally about making it private
[11:12] <pitti> rodrigo_: I'm wondering in the context of https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-system-config-printer-vs-gnome-3-control-center which still needs a decision about "integreate s-c-p into g-c-c" vs. "add a stub to launch s-c-p in separate window"
[11:12] <rodrigo_> but patching that should be easy for us, just a few lines of Makefile.am patching
[11:13] <pitti> rodrigo_: ok, so that's what we're going to do for now?
[11:13] <rodrigo_> pitti, yes, I need to talk with the 2 redhat guys working on g-c-c and s-cp, to see if they plan to merge functionalities
[11:13] <rodrigo_> pitti, well, if the decision is to make it private, yes, if not, we'll do thw whitelist thing
[11:15] <rodrigo_> pitti, about printing, the biggest thing that I was told is missing in the g-c-c panel was sharing, which will be done in the 'Sharing' panel
[11:15] <rodrigo_> pitti, so, I'm waiting to see if we really need s-c-p at all
[11:15] <rodrigo_> not sure what other functionalities we would be missing
[11:16] <pitti> rodrigo_: ah, I thought tkamppeter mentioned quite a lot of other things as well, such as driver download, printer configuration in general, etc.
[11:16] <rodrigo_> hmm, yes, that might be useful indeed
[11:25] <seb128> pitti, the g-c-c, printing, etc outcome was
[11:25] <seb128> - we will make the api public again if upstream doesn't
[11:26] <seb128> - we will allow python panels for g-c-c
[11:26] <seb128> - we will integrate s-c-p to the g-c-c and hide the upstream one
[11:27] <pitti> seb128: ^ +1 on that; I don't think we'll get the upstream one to be as good as s-c-p in just one cycle
[11:27] <seb128> right
[11:27] <seb128> especially that they said no to things like downloading of non opensource drivers
[11:27] <seb128> they don't want to support those
[11:28] <rodrigo_> well, that's still in discussion
[11:28] <rodrigo_> the downloading of drivers
[11:28] <seb128> rodrigo_, well sorry but I don't see all the missing feature to be sorted and coded back this cycle
[11:28] <pitti> rodrigo_: s-c-p can be visually embedded and still run as a separate (python) process then?
[11:28] <seb128> they will need argrement first, then design, then coding
[11:28] <rodrigo_> seb128, oh no, not saying that
[11:28] <seb128> need agreement
[11:29] <seb128> rodrigo_, so the plan for this cycle is still to use s-c-p then ;-)
[11:29] <rodrigo_> pitti, we need to write a loader to embed it
[11:29] <rodrigo_> seb128, yes
[11:29] <seb128> pitti, it's https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-system-settings
[11:29] <pitti> rodrigo_: that will require s-c-p to move to gtk3 and g-i, right?
[11:29] <rodrigo_> pitti, if we just embed it, no
[11:30] <pitti> rodrigo_: ah, so loader != in-process?
[11:30] <seb128> pitti, see "Plan of action:" on this spec
[11:30] <rodrigo_> pitti, using GtkSocket/Plug
[11:30] <seb128> - [rodrigo-moya] work on getting a python loader:
[11:30] <rodrigo_> that was moved to a X window embedder iirc
[11:30] <pitti> cool, thanks for the heads-up
[11:30] <rodrigo_> a python loader would need indeed to have things ported to gtk3
[11:35] <lool> Hmm now my laptop will suspend when I close the lid, but I couldn't find any setting for this in the Power control-center applet nor any dconf key for it under org.gnome.power-manager
[11:36] <didrocks> lool: that's a long discussion on planet gnome and ML :)
[11:36] <lool> there is not even a dconf setting for it?
[11:36] <pitti> rodrigo_: FYI, I replaced the "python loader" WI in https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-system-settings with a link to the existing bug 787694, to not have it counted twice
[11:36] <ubot2> Launchpad bug 787694 in gnome-control-center "GNOME 3 System Settings: Allow Python Programs (or general programs) as embedded capplet" [High,Confirmed] https://launchpad.net/bugs/787694
[11:37] <didrocks> lool: http://afaikblog.wordpress.com/2011/02/03/on-laptop-lids-and-power-settings/ FYI
[11:37] <seb128> pitti, why did we start using bugs rather than work items for those specs? that seems a bit out of workflow and confusing
[11:37] <lool> I have the laptop on my desk most of the time, and I regularly close the lid when I walk away or write down something on top of it; if it suspends, it shuts down wifi etc.
[11:37] <rodrigo_> pitti, ok
[11:37] <didrocks> lool: not sure if there is a system, this blog post seems to intend there shouldn't be
[11:37] <seb128> pitti, especially that you don't get emails about the blueprint bug changes
[11:37] <lool> didrocks: geez
[11:37] <lool> didrocks: thanks for the pointer
[11:37] <seb128> not about people adding or deleting bugs
[11:38] <pitti> seb128: well, we can also invalidate the bug and use a whiteboard item, I'm not that fussed either way; the WI tracker will treat them pretty equally
[11:39] <pitti> seb128: but bugs have a richer state, i. e. you can attach patches, link upstream bugs, etc.; this is one where this could matter
[11:39] <seb128> ok
[11:40] <seb128> it's just that the printing blueprint is the only one I'm subscribed to from an email reading perspective, I just noticed that's because workitems got handled as bugs
[11:40] <seb128> but anyway I'm not working on it so if people doing the work know what they have to do fine with me ;-)
[11:42] <pitti> rodrigo_: ^ as you'll get mail for both, please keep or change it to your liking
[11:47] <rodrigo_> keep the bug you mean?
[11:47] <rodrigo_> pitti, I'm fine with whatever you decide, so just tell me what I should do :-)
[11:48] <pitti> rodrigo_: use the bug or a whiteboard line as WI
[11:49] <pitti> I don't mind much, I just used the bug as it was already there
[11:49] <rodrigo_> pitti, ok, I'll use the bug then
[11:49] <pitti> so its status as a WI will auto-update itself
[12:43] <bcurtiswx> good morning
[12:59] <seb128> pitti, gtksourceview3 could be synced in updated in Debian (just pointing it in case you want another easy update to do in Debian)
[12:59] <seb128> in -> if
[13:12] <pitti> didrocks: if you have a couple of minutes today, would you mind reviewing https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-quickly ?
[13:15] <didrocks> pitti: yeah, will do (still have the tab opened)
[13:16] <pitti> merci
[13:16] <didrocks> mais de rien :-)
[13:23]  * rodrigo_ lunch
[13:43] <pitti> seb128: yup
[13:44] <pitti> seb128: oh, versions claims the upstream versino of that is at 1.8.5..
[13:44] <seb128> pitti, will fix that
[13:54] <mterry> Anyone interested in swapping with me on my patch pilot day next Monday?  That's a US Holiday.  pitti?  rodrigo_?
[13:55] <pitti> mterry: sure, mine is on June 1st if that's better for you?
[13:55] <mterry> pitti, yeah, thanks
[13:55] <pitti> mterry: so, May 30, right?
[13:55] <mterry> right
[13:55] <pitti> changing my cal then
[13:55] <mterry> pitti, awesome
[13:56] <pitti> I get to fly early!
[13:59] <mterry> heh
[14:01] <andreasn> pitti, meeting?
[14:01] <seb128> pitti, mterry: I updated the gcalendar to reflect your swapping
[14:01] <pitti> andreasn: uh, what? which?
[14:01] <pitti> seb128: cheers
[14:02] <seb128> pitti, thunderbird I guess
[14:02] <seb128> hey andreasn ;-)
[14:02] <andreasn> yup
[14:02] <seb128> what is the meeting about? where is it? ;-)
[14:03] <mterry> seb128, thanks
[14:04] <seb128> yw
[14:23] <seb128> desrt, didrocks: btw nautilus 3 (in oneiric) has an EmptyTrash() dbus method, I tried with d-feet it does what it should
[14:23] <seb128> so unity, applets, etc can use that
[14:24] <didrocks> seb128: excellent! thanks or the notice
[14:24] <didrocks> yeah, for less code
[14:25] <seb128> we need to check what it means in a world where nautilus is not always running though (i.e GNOME3)
[14:26] <seb128> chrisccoulson, andreasn: what is the meeting about? reconfirming the requirement decided at UDS?
[14:26] <didrocks> seb128: we will run it for the unity session I guess
[14:26] <didrocks> but yeah, better to confirm :)
[14:26] <seb128> didrocks, right, we should confirm if that's the design intend
[14:26] <chrisccoulson> seb128, pretty much. we're in #thunderbird-unity
[14:27] <seb128> oh ok, let me join, I've opinions on the topic ;-)
[14:28] <seb128> what was the CD space conclusion?
[14:28] <chrisccoulson> seb128 - it probably isn't going to fit
[14:29] <chrisccoulson> the latest thunderbird (and firefox also) have grown in size quite a bit
[14:29] <seb128> :-(
[14:32] <seb128> rodrigo_, there?
[14:44] <pedro_> didrocks, salut, is there anybody working on our side on bug 767095 ? it has a gnome-panel task open for natty but no one assigned to it
[14:44] <ubot2> Launchpad bug 767095 in gnome-panel "1 pixel icons in notification-area-applet when compiz is the windows manager" [High,Confirmed] https://launchpad.net/bugs/767095
[14:44] <pedro_> didrocks, or is that more like a dx bug to fix?
[14:45] <seb128> pedro_, it's a compiz issue
[14:45] <didrocks> pitti: if you have some time just to confirm: https://code.launchpad.net/~didrocks/pkgbinarymangler/dh_translation_support_update_po/+merge/62297
[14:45] <didrocks> pedro_: right, it's a compiz issue
[14:45] <seb128> pedro_, smspillaz is working on it
[14:45] <didrocks> pedro_: it's the top priority for smspillaz now (after discussing with njpatel)
[14:46] <didrocks> hey btw :)
[14:46] <pedro_> ok just wanted to know if it's being tracked, since it's getting a lot of comments
[14:46] <pedro_> thanks didrocks seb128
[14:46] <didrocks> yw
[14:51] <desrt> seb128: very cool information.
[14:56] <pitti> didrocks: queued
[14:57] <pitti> seb128: hm, upgrading gtksourceview from 3.0.0 to 3.0.2 loses all hilighting in gedit :(
[14:58] <seb128> weird
[14:58] <pitti> uh, downgrading -common fixes it; wth?
[14:58] <mterry> didrocks, heyo, can you approve the desktop-o-quickly spec when you get a chance?
[14:59] <didrocks> mterry: yeah, I told before I'll review before eod
[14:59] <mterry> didrocks, oh, sorry.  Didn't know
[14:59] <pitti> python still works, C is broken
[15:00] <didrocks> mterry: no worry, will do it! ;)
[15:01] <seb128> pitti, http://git.gnome.org/browse/gtksourceview/commit/?id=84e2e77babfacfaccd5805405f51785b59ebe508
[15:02] <seb128> I'm wondering if that has to do with it
[15:02] <seb128> but I don't see why it would be broken
[15:02] <seb128> (reading the git history to see what changed)
[15:02] <pitti> I eliminated the new files in -common
[15:02] <pitti> trying this patch
[15:03] <seb128> pitti, is only C highlighting broken?
[15:03] <seb128> pitti, you can mention it on #gedit on the GNOME IRC
[15:03] <pitti> seb128: yes, python works; haven't tried others yet
[15:03] <rodrigo_> seb128, yes
[15:03] <pitti> perl works, too
[15:04] <pitti> bash too
[15:04] <seb128> rodrigo_, the thunderbird guys will have questions for you on e-d-s addressbook creation, what code is responsive to create the e-d-s store and the u1 one, how would that work in the tb case
[15:04] <rodrigo_> seb128, ah, ok
[15:04] <pitti> seb128: reverting above git commit on c.lang doesn't do it either, unless it's cached somewhere
[15:04] <seb128> pitti, ok, that's likely C specific, http://git.gnome.org/browse/gtksourceview/commit/?id=92311794113013127ca2c42d14d91b67b0558370 is quite some change as well
[15:05] <pitti> hm, doesn't apply any more
[15:05] <pitti> seb128: anyway, you gave me enough pointers, thanks!
[15:05] <seb128> pitti, np, I asked on #gedit in case
[15:05] <seb128> I will let you know if they reply
[15:06] <seb128> chrisccoulson, ^ btw (rodrigo pinged about e-d-s questions)
[15:06] <chrisccoulson> thanks
[15:06] <seb128> let have the discussion here when you or the tb guys are interested
[15:11] <pitti> seb128: hah, http://git.gnome.org/browse/gtksourceview/commit/data/language-specs/c.lang?h=gnome-3-0&id=43d9529fc42f29382e8ad640678ed83f38a7070f breaks it
[15:11] <pitti> which is supposed to only fix indentation, but apparently doesn't
[15:13] <Omega> chrisccoulson: You could go through the emails lp sends you to figure out who did it.
[15:13] <chrisccoulson> Omega, lp doesn't send out e-mail for those (or i haven't got one for it)
[15:14] <chrisccoulson> in any case, i know now, as the person mailed me in private
[15:14] <Omega> I get an e-mail everytime someone changes a blueprint I subscribe to.
[15:14] <Omega> with the diff
[15:14] <Omega> But alright
[15:30] <fta> didrocks, hi, does unity in oneiric has the fix for the pixbuf leaks?
[15:30] <didrocks> fta: no, tomorrow should have a new SRU coming in natty, it will be uploaded in oneiric as well
[15:31] <fta> didrocks, ok, thanks
[15:32] <fta> didrocks, i hope unity in oneiric will soon move faster than the natty SRUs :P
[15:32] <didrocks> fta: tell that to the dx team :)
[15:33] <fta> didrocks, i already blogged about it last week
[15:34] <fta> but they're not reading, obviously
[15:34] <fta> (ivory tower syndrome?)
[15:34] <didrocks> fta: I don't think so, I'm just getting tired to be pinged for things I try to act on but have no power…
[15:35] <fta> didrocks, it was not toward you, but toward the dx team
[15:35]  * fta hugs didrocks ;)
[15:35] <didrocks> well, I'm the one pinged ten times a day for it :/
[15:35]  * didrocks hugs fta back ;)
[15:36] <fta> chrisccoulson, fyi, chromium 13 now has the global menu enabled by default, as complete as possible
[15:40] <robbiew> \o/ I can use Oneiric on my laptop now....thnx desktop team!
[15:41]  * dobey updates and logs out/in to see what robbiew is joyous about
[15:42] <robbiew> dobey: heh
[15:42] <robbiew> well..I'm joyous b/c I can use my laptop again
[15:42] <robbiew> still VERY rough ;)
[15:42] <dobey> so "use" is more like "boots and lets you log in" ? :)
[15:45] <fta> booh. lots of (gtk-update-icon-cache:10236): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
[15:46] <fta> wasn't that fixed yesterday??
[15:47] <seb128> fta, what librsvg2-common and libgdk-pixbuf... do you have?
[15:47] <fta> seb128, 2.34.0-0ubuntu4 & 2.23.3-0ubuntu3
[15:48] <fta> oh, after the upgrade, the file is there and not empty
[15:48] <seb128> ok, dunno then
[15:48] <seb128> ok
[15:48] <fta> it complained during the upgrade
[15:49] <seb128> ok, you probably still had the old version
[15:49] <seb128> should be fixed now
[15:57] <dobey> hrmm, still pretty broken :-/
[16:19] <fta> are the giant sticky notifications in evo3 here to stay??
[16:20] <fta> http://people.ubuntu.com/~fta/evo3.png  http://people.ubuntu.com/~fta/evo3-giant-sticky-error.png
[16:20] <dobey> gah
[16:20] <dobey> my eyes
[16:21] <fta> indeed
[16:22] <dobey> i still don't get why people think putting a giant, unthemable, ugly, error message, inside the window, is better than opening a dialog
[16:22] <mdeslaur> argh, we're still going to get the stupid "summary and folder mismatch" errors in evo3?
[16:23] <dobey> mdeslaur: i haven't seen any of those in a very very long time
[16:24] <mdeslaur> dobey: actually, I don't think I've seen them in natty yet...my mother in law's lucid does it every other week though
[16:25] <fta> 1st time i get it (oneiric), and i've been using evo for years
[16:26] <dobey> fta: yeah, when i said very long time, i meant it; i've been using evo for probably 10 years now
[16:27] <dobey> or more than that even
[16:27] <dobey> mdeslaur: hrmm, using pop/imap on gmail and she uses the web UI (or a phone or something else) a lot as well?
[16:28] <pitti> didrocks: followed up with a question in https://code.launchpad.net/~didrocks/pkgbinarymangler/dh_translation_support_update_po/+merge/62297
[16:29] <mdeslaur> dobey: no, nothing that complicated. She just has a simple pop3 account configured in it...she likes to empty out her trash multiple times a day...and about once every few weeks, it does that with the trash folder
[16:29] <dobey> ah
[16:29] <mdeslaur> I've been using evo for years and years also
[16:30] <mdeslaur> I suspect she may have multiple evo instances running concurrently though, she does that
[16:31] <dobey> mdeslaur: unless a different user, that's not possible; it's still a single process
[16:32] <dobey> mdeslaur: but maybe something to do with POP configuration. as POP can be quite weird in some cases
[16:32] <dobey> mdeslaur: probably because it's not configured to delete messages off the server when evo pulls them through POP.
[16:32] <fta> i have 3 accounts (1 local, 2 imaps) in case it matters
[16:32] <mdeslaur> dobey: I've seen that error happen to me occasionally with malformed email containing weird characters
[16:33] <dobey> mdeslaur: i can see that error happening in the case where POP is used more like IMAP than POP
[16:33] <mdeslaur> anyway, it's not important...I just saw the error message in fta's screenshot, and it gave me chills, that's all
[16:33] <mdeslaur> dobey: nope, her pop3 setup deletes from the server
[16:33] <dobey> ah ok
[16:33] <dobey> weird then
[16:34] <dobey> anyway, yeah; evolution is scary huge, i don't know why the developers aren't working on actually breaking it up
[16:34] <didrocks> pitti: answered
[16:34] <dobey> and making a good mail UI
[16:37] <cyphermox> mdeslaur: IIRC we got these errors in Natty initially, then I fixed it (or somebody else did) as a cherry-pick or whatever, but it seems to happen again
[16:38] <mdeslaur> cyphermox: it hasn't happened to me in a long time...which is nice, as in lucid it happened a lot
[16:39] <cyphermox> yeah
[16:39] <cyphermox> I think it was found early enough
[16:39] <cyphermox> it's still early enough, I really need to focus on releasing NM 0.9 now, so I'll get back to evo once that's done
[16:40] <mvo> pitti: I will readd the 91_keep_fd patch to vte if you don't mind. the required parts of the api to replace it are not exposed in the python2 api so this I need to have until gdebi-gtk is ported to gtk3
[16:52] <pitti> mvo: oh, sure
[16:52] <pitti> mvo: sorry about that
[16:52] <mvo> pitti: no problem, its a pretty ugly patch so I understand the urge to get rid of it :)
[16:53] <pitti> mvo: is there some particular difficulty with the porting, or just a manpower issue? want me to have a look at it?
[16:55] <mvo> pitti: no particular problem really more lack of time, it should actually realy easy as the gui is pretty simple. i may give it a try tomorrow morning to warm up on this topic. I'm sure I have many question then for you
[16:55] <mvo> pitti: I started with softare-centwer, but that is a magnitude bigger
[16:55] <rodrigo_> bbiab
[16:56] <didrocks> pitti: do you prefer to discuss here about the update-po issue?
[16:57] <pitti> mvo: so if you _want_ to port gdebi and learn about it, that's fine, and I'm happy to assist you; if you don't really want to do it, then I can have a go at porting it
[16:57] <pitti> didrocks: yeah, was about to
[16:57] <didrocks> pitti: the think is that unity-2d has no POTFILES.in, and only this target. (and yeah, it merges po in gmo file as well)
[16:57] <pitti> didrocks: it's now actually a debian policy issue and a packaging bug if you build the source, clean it, and you still have a diff
[16:57] <pitti> didrocks: and it's not just extra generated files, it actually will modify the original source files
[16:58] <didrocks> pitti: let me see if it's just generating .mo files or touching existing .po files
[16:58] <mvo> pitti: great I give it a go then and ask for either help or takeover, depening on how it goes . thanks a lot for the offer to help with it
[16:58] <pitti> didrocks: if only we knew the upstream of unity-2d to add a new Makefile target to build the pot only :)
[16:59]  * pitti hugs mvo, np
[17:00] <didrocks> pitti: well, I proposed them to switch to intltool first or use GETTEXT_PACKAGE, but they are relunctant to it
[17:00] <didrocks> pitti: a target for updating the pot file would be possible (there is the script called update-unity-2d-pot)
[17:01] <didrocks> just a pity to have to dh_override…
[17:01] <didrocks> I was thinking that update-po would have been more generic, but yeah, it's generating the .gmo
[17:01] <pitti> didrocks: if "make -C po ${GETTEXT_DOMAIN}.pot works, we can also use that
[17:01] <pitti> didrocks: that sounds like a safe target to try in dh_translations
[17:02] <didrocks> pitti: they are not using GETTEXT_DOMAIN as well
[17:05] <didrocks> pitti: I'm trying to convince them to use GETTEXT_DOMAIN
[17:08] <didrocks> pitti: just curious, this target also create the .pot file, isn't it? so it's again the debian policy if it's called automatically?
[17:09] <pitti> didrocks: creating an additional file is still better than modifying existing source; and the clean rule could actually remove it again, too
[17:09] <didrocks> pitti: right, so that + adding the clean target
[17:09] <pitti> but merging po files by default is too much, I'm afraid
[17:10] <didrocks> pitti: trying to do some diplomacy right now to push that change upstream :)
[17:10] <didrocks> I knew the review was useful!
[17:14] <pitti> heh
[17:14]  * pitti waves good night, 'nuff for today
[17:14] <pitti> see you tomorrow!
[17:14] <cyphermox> night pitti
[17:15] <didrocks> pitti: see you!
[17:15] <seb128> 'night pitti
[17:19]  * cyphermox lunch
[17:22]  * mvo pushes a not immediately crashing lp:~mvo/gdebi/gtk3 and goes for lunch
[17:22] <mvo> eh, dinner
[17:24] <mvo> pitti: feel free to work on this if you want, I won't touch it anymore today, I had to comment some drag-n-drop stuff (and some other stuff is not working too). but amazing how much the script did already
[17:48] <bcurtiswx> seb128: Thx for the sponsorship
[17:51] <seb128> bcurtiswx, you're welcome
[17:51] <seb128> bcurtiswx, there was some issues in your merge request but I fixed those, you didn't drop the git backport from the vcs or the serie for example, not sure how you built it
[17:54] <bcurtiswx> seb128: I forgot until the end to merge it back with ~ubuntu-desktop and I must have missed those in my final check. Thx for catching them.
[18:18] <seb128> if someone feels like doing simple updates gucharmap file-roller and yelp should be easy
[18:25] <didrocks> have a good evening everyone
[20:21] <bcurtiswx> What tools would best help me port from gtk2 to gtk3?
[20:22] <seb128> bcurtiswx, your favorite editor?
[20:23] <bcurtiswx> seb128: :( where would i ( the noob ) start?
[20:23] <highvoltage> I guess vimtutor is always a good place to start.
[20:23] <seb128> bcurtiswx, https://live.gnome.org/DevGnomeOrg/Gnome3PortingGuide
[20:27] <bcurtiswx> Haha. I use vim for all my editing, I'm quite good with that. I will start with seb128's site. If I try to compile will it stop at all functions it doesn't recognize as maybe a starting point? Maybe a compiler option?
[20:27] <seb128> bcurtiswx, https://live.gnome.org/GnomeGoals/RemoveDeprecatedSymbols/GTK%2B
[20:27] <seb128> set -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED
[20:28] <seb128> cyphermox, btw the evo stack has 3.0.2 versions if you want to do the updates
[20:29] <cyphermox> yup
[20:29] <cyphermox> seb128: but do we want to go up more than that, to say, 3.1.1?
[20:30] <seb128> no, we want to land the stable 3 first and shake out instability then go the upgrades
[20:30] <cyphermox> ok
[20:30] <cyphermox> then 3.0.2 it is
[20:30] <seb128> i.e we don't want to mix issues due to the upgrades and due to the unstable versions
[20:30] <cyphermox> I *think* I'm almost done bringing up NM 0.9, just a matter of a few more hours
[20:30] <cyphermox> sure
[20:31] <seb128> oh, nice
[20:31] <seb128> well do nm first, no hurry for evo
[20:31] <seb128> though the stable updates might be easy, i.e just a dch run
[20:33] <cyphermox> yeah. I'll get to it right after. hopefully as soon as tomorrow morning
[20:33] <cyphermox> the merge with Debian for NM 0.9 was... interesting ;)
[20:34] <seb128> lol, somewhat that's not a surprise ;-)
[20:34] <cyphermox> nope. I was dreading that task, knowing it would be huge, even with all the other steps I took to manually bring the packaging as close as possible
[20:41] <bcurtiswx> Hmm bzr branch lp:debian/empathy is at 2.30.3-2. Should i not be using that?
[20:43] <seb128> james_w, ^ do you know?
[20:43] <seb128> bcurtiswx, it's what debian unstable has
[20:43] <seb128> not sure if they import experimental
[20:44] <bcurtiswx> I can do it by other means but I was taught to use that
[20:45]  * micahg was under the impression that unstable was the default branch for Debian like the dev release is for us
[20:46] <james_w> bcurtiswx, you want to merge from experimental?
[20:46] <bcurtiswx> I am rebasing empathy and was going to use that
[20:48] <bcurtiswx> james_w: But yea experimental has the most recent empathy
[20:49] <james_w> bcurtiswx, did you try lp:debian/experimental/empathy?
[20:50] <ricotz> bcurtiswx, there is a  empathy package in the gnome3 ppa
[20:50] <bcurtiswx> james_w: Nope but I will.
[20:50] <ricotz> bcurtiswx, there is also a branch
[20:50] <bcurtiswx> ricotz: I am going to use that to rebase with debian.
[20:51] <ricotz> bcurtiswx, alright
[20:52] <bcurtiswx> Seems debian doesn't have 3.0.2 though. Only 3.0.0 so should i try debians version for rebase then update from there?
[20:53] <seb128> that's usually the best way to do it
[20:53] <seb128> rebase on what debian has and do the minor update over it
[20:53] <seb128> the minor update is usually trivial, i.e just updating the changelog and maybe refreshing some patches after it
[20:55] <bcurtiswx> Ok. Experimentals got 3.1.1 as most recent . Can i use lp:debian/experimental/empathy somehow to get 3.0.0?
[20:55] <bcurtiswx> I
[20:55] <bcurtiswx> Am searching now
[20:56] <seb128> the stable update is probably in the debian history yes
[20:56] <seb128> you just need to get the right commit
[20:58] <geser> bcurtiswx: try checking out rev 52 of that branch, that should give you 3.0.0-1 (https://code.launchpad.net/~ubuntu-branches/debian/experimental/empathy/experimental)
[20:59] <highvoltage> /win 15
[21:26] <bcurtiswx> Debian uses location and map and AFAIK that uses geoclue. Do we follow suit or does there need to be some kind of design decision?
[21:26] <bcurtiswx> For empathy
[22:02] <seb128> time to call it a day, 'night everybody
[22:02] <kinouchou> bonne nuit seb128
[22:02] <seb128> 'nuit kinouchou ;-)