[01:49]  * TheMuso eyes his 4GB RAM disk, and suspects that QT is not going to have enough room to build...
[01:50] <TheMuso> 86% full atm.
[02:37] <RAOF> You've got some swap, right? :)
[02:50] <TheMuso> Yup, but it failed anyway due to no tmpfs disk space left. So rebuilding on actual HD now,.
[02:51] <TheMuso> Doesn't help that I am also running a VM.
[02:52] <TheMuso> But its times like this when having lots of RAM and a powerful system is totally justified.
[03:06] <TheMuso> Ok so that compiler error I got earlier was not due to no disk space left...
[03:06] <TheMuso> Damn, there goes that plan for today...
[04:44]  * TheMuso discovered that 1) QT 4.7.3 doesn't seem to die with a compile error like it did earlier, and I only needed to drop one patch from our package to build a 4.7.3 package for testing.
[04:44] <TheMuso> s/like it did earlier/like QT 4.7.2 did earlier./
[04:53] <cdbs> cyphermox: Hi, it seems there are many issues with the new nm
[04:53] <cdbs> cyphermox: It doesn't connect to Ad hoc WiFi networks, what do I need to provide to help debug this?
[05:33] <pitti> Good morning
[05:41] <TheMuso> Good morning pitti.
[06:00] <TheMuso> Is it me, or is the metacity/compiz keybinding to move windows around with alt + left mouse click broken?
[06:00] <pitti> works here with compiz
[06:00]  * TheMuso is running oneiric in a vm with GNOEM classic, running metacity atm.
[06:00] <pitti> but we got a new metacity yesterday
[06:00] <TheMuso> Tried the same with unity/compiz earlier with no luck.
[06:00] <TheMuso> Right.
[06:00]  * TheMuso will try with compiz again.
[06:00] <pitti> I noticed that since yesterday or so my windows don't have close/min/max buttons any more, though
[06:02] <TheMuso> Well compiz is not rendering properly in virtualbox, actually thigns aren't being cleared once rendered... Probably due to the version of virtualbox being used.
[06:02] <TheMuso> no big deal, only using the VM to get a11y sorted before I switch on bare metal.
[06:05] <TheMuso> Well it seems that unity 2D now has some keyboard navigation, at least for the launcher.
[06:20] <cdbs> robert_ancell: LightDM in oneiric is okay enough to install, I hope? :)
[06:23] <micahg> cdbs: it's been working for me
[06:24] <cdbs> hmm
[06:41] <robert_ancell> cdbs, should be
[06:41] <RAOF> Works here.
[06:56] <cdbs> sudo aptitude install lightdm
[06:56] <cdbs> whoops
[06:56] <cdbs> wrong window :(
[07:01] <TheMuso> lol
[07:03]  * TheMuso crosses fingers that these a11y patches don't bring the QT compilation to a screaming halt.
[07:04]  * Tm_T fights against the sudden urge to ask "QuickTime?"
[07:05] <TheMuso> No, QT as in the toolkit.
[07:06] <Tm_T> ah, Qt (:
[07:06] <TheMuso> As in the mother beheamouth qt4-x11.
[07:06] <Tm_T> I actually knew what you meant, I just like to tease with that bit wrong capitalization
[07:07] <TheMuso> Screw capitalization.
[07:07] <TheMuso> When such a package takes 2 hours to build on a quad core desktop CPU at 3.0Ghz, with 8GB RAM, I don't give a crap as to how its supposed to be written.
[07:07]  * Tm_T huggles TheMuso
[07:07]  * RAOF wonders whether the two openjdk builds he fired off thsi morning will finish today.
[07:07] <TheMuso> RAOF: Ok you win. :)
[07:08] <TheMuso> Tm_T: :)
[07:08] <Tm_T> I'm used to build Qt and/or KDE (and apps) so I have some experience on watching compilation a day or two
[07:08] <TheMuso> I just hope didrocks knows what he is getting himself into.
[07:09] <TheMuso> However, the good side is that the a11y patches apply cleanly to the latest Qt in natty/oneiric so...
[07:15] <didrocks> good morning
[07:15] <TheMuso> Good morning didrocks.
[07:16] <didrocks> hey TheMuso, how are you?
[07:17] <TheMuso> didrocks: Not too bad thanks, yourself?
[07:17] <didrocks> TheMuso: I'm good thanks :)
[07:17]  * TheMuso has QT a11y patches, and is currently building QT to test them out with the at-spi bridge...
[07:18] <didrocks> bryce: RAOF: in oneiric, there is a delay between typing and being able to use the trackpad. Not sure if it's done at the X level or not. The delay is a little bit long and quite annoying to use :/
[07:18] <RAOF> didrocks: Oh, that feature of gnome-settings-daemon is back? :)
[07:18] <didrocks> TheMuso: oh? nice! do you want me to backport that to Qt just after alpha1? I need to remerge Qt with debian
[07:18] <didrocks> RAOF: ok, it's really GNOME then :)
[07:18] <didrocks> let me check in g-c-c
[07:19] <didrocks> yeah, I disabled it now
[07:19] <TheMuso> didrocks: Would like to give them a hammering first. I am also still waiting on one more commit that isn't yet in the public Qt repo. One upside though is that they all apply cleanly against 4.7.3.
[07:19] <RAOF> syndaemon also provides that behaviour, but I think it got rolled into g-c-c
[07:19] <didrocks> well, I like that the trackpad is disabled when typing, just that the timing is a little bit too long at the end :/
[07:20] <didrocks> RAOF: probably the gsettings migration changed the default
[07:20] <cdbs> good morning didrocks and friends
[07:20] <didrocks> TheMuso: that's an excellent news! Are you in touch with the Qt guys about those?
[07:20] <didrocks> hey cdbs!
[07:21] <didrocks> TheMuso: and consequently, the a11y state in Qt will be ok then?
[07:22] <pitti> hey didrocks
[07:22] <TheMuso> didrocks: I am in contact with the folks at Nokia doing Qt a11y. They are hoping to have Qt a11y almost if not completely done by September, so I guess all we can do is get the patches in, watch for any updates, and keep testing and filing bug reports.
[07:23] <didrocks> guten morgen pitti
[07:23] <didrocks> TheMuso: agreed, keep me in touch please when you are happy with those (even if it's just partial right now), so that I can post alpha1 merge with debian and integrate them in oneiric
[07:24] <TheMuso> didrocks: Will do.
[07:24] <didrocks> thanks!
[07:25] <TheMuso> didrocks: Oh and I hope you have some CPU cycles, QT on my desktop takes a couple of hours to build.
[07:25] <cdbs> Gnome-power-manager seems to be building with GTK2 symbols
[07:25] <didrocks> TheMuso: same here, it was quite a surprise the first time :-)
[07:27] <didrocks> TheMuso: your pyatspi change looks good, I'm promoting to main then! Thanks for your patience :)
[07:28] <TheMuso> didrocks: np thanks. Will adjust seeds/deps after alpha 1.
[07:29] <didrocks> perfect
[07:30] <didrocks> no auto rebuild of the CD? (I wanted to see with gnome-panel out the result)
[07:30] <didrocks> !topic
[07:31] <ubot2> Please read the channel topic whenever you enter, as it contains important information. To view it at any time after joining, simply type /topic
[07:31] <didrocks> oupss :)
[07:32] <pitti> didrocks: we do have daily cron jobs
[07:34] <didrocks> so it failed,
[07:35] <didrocks> pitti: your change in debian/watch in debian, not sure debian wants to track with uscan unstable version (last time we discussed that with them, they were quite opposed to it)
[07:36] <pitti> didrocks: I didn't change that
[07:36] <pitti> but there was a syntax error, causing it to not scan properly at all
[07:36] <didrocks> pitti: ok, I was just puzzled by the commit message then: "Fix syntax to actually catch latest version" :)
[07:36] <didrocks> was just in case, sorry for the noise :-)
[07:37] <pitti> e. g. 2.28 is current, but it only saw 2.20 because the ) was misplaced
[07:37] <pitti> didrocks: no worries -- always good to have reviews :)
[07:37] <didrocks> :)
[07:43] <rodrigo_> morning
[07:47] <didrocks> hey rodrigo_
[07:50] <rodrigo_> hi didrocks
[07:56] <didrocks> unity really got a higher score that I would expect for such a big change: http://blog.nizarus.org/2011/05/unity-or-not-unity
[07:57] <didrocks> the number of voter is high enough to be representative I think (in addition that people voting are those visiting planet.ubuntu.com for most)
[07:57] <didrocks> so most technical users, those who can be relunctant to the change
[07:58] <didrocks> funny enough, if you only read the comments, you would believe that everyone is against it :-)
[07:59] <cdbs> didrocks: Most of the people who voted 'unity' voted and left
[08:00] <cdbs> didrocks: Those who use gnome-shell or gnome-classic have a habit of commenting everywhere
[08:00] <didrocks> cdbs: yeah, clearly show that people comments only if they are not happy
[08:00] <cdbs> didrocks: I have some really good experience with handling those commenters on OMG! Ubuntu! (where I'm one of the writers)
[08:00] <didrocks> well, it's more general than that, you rarely tell when you are happy with someone, you just express your opinion when you disagree :)
[08:01] <didrocks> cdbs: I'm used to that in the French ubuntu forum since 2004 ;)
[08:01] <didrocks> but following the evolution with people commenting in the unstable version (and keeping testing) was really instructive
[08:02] <didrocks> and I saw that people against unity at start was getting to like after after approx. 2 days of real test and usage
[08:02] <didrocks> and then, they couldn't switch back
[08:02] <didrocks> so again, everything is a question of habits
[08:02] <pitti> yesterday I saw an article on heise open
[08:03] <pitti> they said that unity's goal was to address new Linux users, but in her eyes it fails to do that; while for an experienced (keyboard, etc.) user it's quite nice
[08:03] <pitti> fails because the workflow is too different from windows, and without keyboard navigation it's too clumsy to find/open apps, etc.
[08:04] <pitti> it takes a long time to find chat in the dash (if you don't know about the messaging indicator, etc.)
[08:04] <pitti> so, matter of education indeed
[08:04] <didrocks> however, I got at the ubuntu party a lot of remarks that it was "hard" to switch between applications
[08:04] <RAOF> Certainly the dash is a horrible interface for *browsing* applications at the moment.
[08:04] <didrocks> I think not hiding the launcher by default when you screen is big enough would just help to solve that issue
[08:04] <pitti> but IMHO you can only get so far trying to make it easy for people who don't want to learn anything about how a komputah works
[08:05] <didrocks> RAOF: yeah, we need to add some metadata
[08:05] <didrocks> pitti: agreed
[08:05] <pitti> my wife loves unity, but she's been a heavy keyboard user for years
[08:06] <didrocks> yeah, so switching application/getting into the dash is not complicated for her
[08:06] <pitti> she got used to unity in no time, but then again she also does LaTeX etc., so she's a bad test case
[08:06] <didrocks> heh :-)
[08:06] <pitti> and well, I did explain the windows key to her
[08:06] <pitti> without that I think it'd be pretty hard
[08:07] <pitti> we really need something to point out this wonderful key
[08:07] <didrocks> we can use 3D glasses for that :-)
[08:07] <didrocks> with an arrow pointing to your keyboard :p
[08:07] <didrocks> ok, we need to know what kind of keyboard you have ;)
[08:08] <didrocks> but more seriously super key == showing the launcher, I really think we should get it always visible
[08:09] <didrocks> (even if I did most of the intellihide code and it will hurt my personal feeling, I think it makes no sense on big screen to hide it)
[08:15] <pitti> that still doesn't point out where the dash is, and how to get the typahead, etc.
[08:15] <pitti> that's where the efficiency comes from (or from win+number), not from seeing the launcher
[08:15] <pitti> the launcher is already visible at the start, so people know that there is one
[08:18] <geser> so unity should have a tutorial displaying all features when started for the first time?
[08:21] <didrocks> pitti: opening the dash at the first login. You can maybe notice the bfb being "pressed" and then unpressed once closed
[08:21] <RAOF> That's a last-ditch workaround for not being discoverable, though.
[08:21] <RAOF> didrocks: Starting with the dash open seems like a pretty good idea; the first thing you'll want to do when you log in is to *start* something, after all.
[08:22] <didrocks> and we can display whatever wew want in the dash, so it can even add "welcome to ubuntu 11.10" for instance
[08:22] <didrocks> we*
[08:35] <rodrigo_> need to go the dentist :-( , so bbl
[08:36] <pitti> rodrigo_: ugh, good luck
[08:39] <didrocks> see you rodrigo_
[08:42] <mvo> hm, is it just me or is compiz leaking memory on natty (with intel). it was up to 3gb virtual this morning, compiz --replace resulted in a modest 600mb (virt)
[08:43] <didrocks> mvo: yeah, there is a known issue. The current SRU in -proposed should fix the biggest one
[08:43] <mvo> sweet, I give it a go
[08:43] <didrocks> mvo: it's in nux
[08:44]  * mvo install that now
[08:46] <pitti> funny, the other Michael (mh21) also brought that up and debugged it a while ago
[08:47] <pitti> mvo: are you using the multiload indicator by any chance?
[08:47] <pitti> because that triggers the bug very nicely
[08:47] <didrocks> yeah, the multiload indicator was triggering it a lot
[08:48] <pitti> as it updates its icon a dozen times a second
[08:48] <mvo> pitti: yeah
[08:48] <mvo> pitti: I use it and love it (and sponsored it into oneiric)
[08:49] <pitti> yeah, I newed it yesterday, I like it, too :)
[08:49] <didrocks> mvo: if it fixes it, can you confirm it here: bug #758248
[08:49] <ubot2> Launchpad bug 758248 in nux "memory leaking in compiz" [Undecided,Fix committed] https://launchpad.net/bugs/758248
[08:50] <didrocks> jay is pretty confident it fixes it
[08:50] <didrocks> (I kept the bug seperated as the fix that was done seemed unrelated to me)
[08:50] <pitti> didrocks: is that mh21's patch?
[08:50] <pitti> as he got the leak with the multiload indicator, so that ought to fix it
[08:51] <mvo> pitti: aha, it was you, thanks \o/
[08:51] <didrocks> pitti: mh21's patch is in unity, let me check we included it. I think we did
[08:51] <pitti> ah
[08:51] <didrocks> pitti: in that case, I have to readd the bug # then to the list
[08:53] <didrocks> yeah, it is :)
[08:53] <didrocks> mvo: so install the new unity as well
[08:53] <didrocks> then, I'll add the bug to the target (wasn't done), add the test case
[08:53]  * didrocks told the dx team 10 times to set the bugs as fix committed when merging contributor's branch
[08:56] <RAOF> Hm.  Indicator-multiload is pretty cool, but only exists because the launcher doesn't have the icon API that it deserves :)
[08:56] <didrocks> mvo: updated to bug #779717. can you give some feedback if fixed please?
[08:56] <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
[08:56] <mvo> I like it because its a easy way to see if something goes rouge (e.g. my devel code)
[08:56] <mvo> didrocks: yes, will do
[08:57] <didrocks> thanks :)
[08:57] <didrocks> "goes rouge"? turning to French? :)
[08:58] <pitti> or when your package build in the background finishes, and it's time to stop wasting time with email :)
[09:00] <mvo> :)
[09:12] <pitti> mvo, didrocks: FWIW, I set the icons to 200 px and 100 ms update interval, and virt/res stay constant; so this one seems fixed to me
[09:12] <didrocks> pitti: excellent news :-)
[09:12]  * didrocks needs to install it as well
[09:13] <pitti> well, this is oneiric, not natty-proposed
[09:13] <pitti> same code, but different toolchain/environment, so I won't v-done the bug
[09:14] <didrocks> yeah, let's wait on mvo :)
[09:16] <seb128> hey desktopers
[09:16] <seb128> \o/ pitti \o/ (debian updates)
[09:16] <pitti> hey seb128
[09:16] <seb128> hey pitti
[09:16] <pitti> seb128: cheers ;)
[09:17] <seb128> so the new gnome-keyring is supposed to fix the "several application prompt for password on autologin"
[09:17] <didrocks> salut seb128!
[09:17] <pitti> seb128: I didn't get that bug, but 3.0.3 works fine here
[09:17] <seb128> which is nice because that was a frequent complain and something I said we would work on this cycle :p
[09:17] <seb128> pitti, do you use autologin?
[09:17] <pitti> no, I can't
[09:17] <pitti> ecryptfs
[09:17] <seb128> ok, so it's normal you don't get the bug
[09:17] <seb128> the keyring is pam unlocked for you
[09:18] <pitti> ah, unlocking the whole keyring
[09:18] <didrocks> oh, there is a solution for that issue now?
[09:18] <pitti> so, try it out :)
[09:18] <seb128> didrocks, it's fixed in 3.0.3
[09:18] <didrocks> nice :-)
[09:18] <seb128> didrocks, the unlocking was meant to be serialized there was just a bug
[09:19] <didrocks> oh, I was thinking it was a deeper issue than this one
[09:19] <seb128> so each application trying to access the keyring was triggering a prompt rather than having just one and the others serialized and unlocked with it
[09:20] <seb128> rodrigo_, hi
[09:20] <seb128> rodrigo_, you need a mir for clutter-gtk, gnome-games is depwait on it
[09:23] <didrocks> clutter-gtk was in main before (with netbook-launcher), isn't it?
[09:24] <seb128> didrocks, https://launchpad.net/distros/ubuntu/+source/clutter-gtk suggests not
[09:24] <seb128> did it change source name or something?
[09:24] <didrocks> seb128: possibly, let me check
[09:24] <didrocks> seb128: I'm pretty sure clutk was dep on it
[09:25] <didrocks> clutter changed a lot with soname in source name or not
[09:25] <seb128> https://launchpad.net/ubuntu/+source/clutter-gtk/0.10.2-0ubuntu4
[09:25] <seb128> hum
[09:25] <seb128> indeed, I'm wondering why it's not on the summary screen
[09:25] <fta2> gasp, i've lost all my window buttons. where is the pref now? (what used to be /apps/metacity/general/button_layout)
[09:25] <seb128> that lucid version was in main
[09:25] <didrocks> yeah
[09:26] <didrocks> seb128: I usually rely on https://launchpad.net/ubuntu/+source/clutter-gtk/+publishinghistory
[09:26] <seb128> well usually https://launchpad.net/ubuntu/+source/clutter-gtk is handy
[09:26] <seb128> it has the distro serie, version and component
[09:26] <seb128> not sure why it lacks hardy < < natty
[09:26] <didrocks> weird that lucid/maverick isn't there
[09:26] <didrocks> yeah
[09:27] <didrocks> deleted
[09:27] <didrocks> renamed to clutter-gtk-0.10
[09:27] <seb128> "renamed to clutter-gtk-0.10"
[09:27] <seb128> oh ok
[09:27] <didrocks> :-)
[09:27] <seb128> bah, I tried clutter-gtk-1.0
[09:27] <seb128> loose :p
[09:27] <seb128> tried -0.8 as well
[09:27] <didrocks> clutter versionning :-)
[09:27] <seb128> I though it had been renamed but I tried the wrong ones before asking
[09:27] <seb128> didrocks, thanks
[09:28] <didrocks> seb128: yw
[09:28] <seb128> so let's repromote it
[09:29] <seb128> didrocks, can you sponsor the e-d-s and evo update? those are minor version updates so should be easy
[09:29] <didrocks> seb128: sure
[09:30] <didrocks> I have some spare time while my bug script is launched in debugging mode (got some relevant only one hour after testing)
[09:34] <seb128> didrocks, thanks
[09:34] <didrocks> seb128: fixed the versionning and uploaded
[09:34] <seb128> we might be down to less than one screen of updates to do today ;-)
[09:34] <didrocks> \o/
[09:37] <pitti> mvo: hm, I'd really like to drop aptdaemon's lintian recommends; it pulls in dpkg-dev, which pulls in build-essential, pulling in g++, binutils, tons of perl stuff, and what not :/
[09:37] <pitti> intltool-debian, gettext, etc
[09:38] <pitti> mvo: I suppose it only does very few checks which are fatal? perhaps we can do them manually instead through lintian?
[09:38] <pitti> mvo: want me to look into this?
[09:42] <pitti> hm, it's actually quite a long list, but spending 10 MB for this is a bit heavy; perhaps we can install lintian when the user actually adds a third party repo
[09:43] <mvo> pitti: yeah, its not actually using that many, its fine to reimplement them manually its just going to be a bit tedious to maintain that in parallel with lintian
[09:43] <pitti> /usr/share/aptdaemon/lintian-fatal.tags.Ubuntu has 34 tags
[09:43] <pitti> mvo: so I guess it might be easier to install lintian on demand
[09:43] <pitti> ?
[09:43] <mvo> yes, that is probably better
[09:45] <pitti> can I give that as a WI to Gary or you?
[09:45] <mvo> didrocks: stable memory usage for me as well now
[09:46] <mvo> didrocks: 621m  53m  22m S    3  1.4   0:40.44 compiz  (according to top)
[09:46] <pitti> I have roughly the same numbers
[09:46] <didrocks> mvo: excellent! think about updating the bug status :)
[09:48] <seb128> pitti, btw not sure if you read the backlog from yesterday but I started cleaning gdm
[09:48] <pitti> seb128: I saw, thanks! just didn't get to working on it yet
[09:48] <seb128> the vcs is half done cleaning patches, merging with debian
[09:49] <seb128> pitti, no hurry
[09:52] <jasoncwarner> morning morning morning...how is everyone?
[09:52] <seb128> hey jasoncwarner, I'm fine, how are you?
[09:53] <pitti> hey jasoncwarner
[09:53] <seb128> what's new on your side of the world? ;-)
[09:53] <jasoncwarner> pretty good seb128 and pitti. Just enjoying having the family from the states here...
[09:53] <jasoncwarner> seb128: it's cold. people didn't tell me it got this cold!
[09:53] <seb128> oh right, so they liked .au? ;-)
[09:54] <jasoncwarner> seb128: yeah, they kept laughing at the size of the town and stuff. though, they did enjoy themselves
[09:54] <jasoncwarner> how is everything going in the world of oneiric? :) should I update my main machine yet? ;)
[09:54] <mvo> yes!
[09:54] <pitti> looking funny, but working
[09:55] <jasoncwarner> mvo: always the pot stirrer ;)
[09:55] <pitti> if you enjoy gnome-screensaver looking like gnome-shell, gdm looking like the IT crowd intro, and general GNOME looking themeless :)
[09:55] <mvo> heh :) its working pretty well for me so far, but its indeed looking funny so maybe better to wait until the theme lands
[09:55] <jasoncwarner> pitti: well, perhaps I'll just update my test machine then !
[09:56] <pitti> it's totally broken in kvm, though
[09:56] <pitti> unity-2d, too
[09:57] <seb128> jasoncwarner, if you install gnome-theme-standard and turn the gsettings to show-desktop-icons it's ok
[09:58] <didrocks> hey jasoncwarner
[09:58] <jasoncwarner> morning didrocks
[10:02] <chrisccoulson> hey jasoncwarner, how are you?
[10:02] <RAOF> You crazy people with stuff that can be usefully tested in kvm!
[10:03] <pitti> RAOF: there's lots of X parts which can :)
[10:03] <jasoncwarner> hey chrisccoulson....
[10:03] <pitti> these just don't tend to be the ones which break, of course
[10:03] <RAOF> pitti: Yeah.  The protocol's not exactly the fastest-moving of targets :)
[10:04] <RAOF> chrisccoulson: Why must seamonkey packaging be hatefully arcane? :)
[10:04] <chrisccoulson> RAOF, because nobody maintains it ;)
[10:04] <chrisccoulson> it's not that different to the firefox packaging though is it?
[10:05] <chrisccoulson> RAOF, are you volunteering to maintain it? ;)
[10:05] <pitti> hey chrisccoulson
[10:05] <RAOF> No, it's just the final bit of today's patch-piloting.
[10:05] <chrisccoulson> hi pitti, how are you?
[10:05] <pitti> chrisccoulson: I'm great, thanks!
[10:05] <chrisccoulson> RAOF, i bet i know which one ;)
[10:05] <pitti> chrisccoulson: played a bit with distribution.ini stuff, and learned some bits
[10:05] <chrisccoulson> pitti - cool :)
[10:05] <RAOF> Apparently seamonkey is a pile of crash on natty and oneiric, and is relatively easily fixable.
[10:06] <RAOF> Or would be if seamonkey built on oneiric :)
[10:06] <pitti> chrisccoulson: seems I need to take up some of your time at some point, though; I have a few options which I'd like to discuss
[10:06] <chrisccoulson> RAOF, yes. i would really just switch the current seamonkey to gcc-4.5 in oneiric
[10:06] <pitti> chrisccoulson: I need to run out for some errnads, and finally send the meeting reminder, but perhaps this afternoon?
[10:06] <chrisccoulson> i wouldn't bother investing any time in fixing seamonkey to build on the new toolchain ;)
[10:06] <pitti> seb128: you forgot to remind me :)
[10:07] <chrisccoulson> pitti - sure, no problem :)
[10:07] <chrisccoulson> RAOF, there is a community guy providing PPA builds of seamonkey atm. i think i'm going to approach him this week and ask him if he wants to look after seamonkey in the distro
[10:08] <chrisccoulson> i don't really have time to look after it, and i never use it anyway
[10:08] <seb128> pitti, oh, right, it's meeting reminder day!
[10:08] <RAOF> It's clear that *somebody* uses it, as the crash bug has a bunch of duplicates.  Having someone actually maintain it would be pretty rad, though.
[10:08] <seb128> pitti, I got used to you having the email sent before I woke up for a few weeks ;-)
[10:08] <pitti> seb128: I thought about it this morning, and then forgot :/
[10:09] <chrisccoulson> RAOF, yeah, i reckon the number if users is probably in to double figures ;)
[10:09] <seb128> hey chrisccoulson
[10:10] <chrisccoulson> hi seb128, how are you?
[10:10] <seb128> I'm fine thanks
[10:10] <seb128> how are you?
[10:10] <chrisccoulson> seb128 - very, very tired. my daughter kept me awake nearly the whole night
[10:10] <chrisccoulson> dosing up on caffeine now though ;)
[10:10] <seb128> :-(
[10:10] <seb128> is she sick?
[10:11] <seb128> or she just didn't want to sleep?
[10:11] <chrisccoulson> i think her last few teeth are coming through. she kept waking up crying every 40 minutes or so overnight
[10:11] <chrisccoulson> and by the time my eyes started to close each time, she would wake up again ;)
[10:12] <chrisccoulson> the annoying thing is that she is full of beans this morning. it's like she had a full nights sleep ;)
[10:14] <soren> chrisccoulson: How old is she?
[10:14] <chrisccoulson> soren - she's about 2 weeks older than 18 months now
[10:14] <seb128> lol
[10:15] <seb128> chrisccoulson, so coffee time for you? ;-)
[10:15] <chrisccoulson> yeah :)
[10:15] <pitti> bbl
[10:20]  * mvo hugs chrisccoulson in sympathy
[10:20]  * chrisccoulson hugs mvo
[10:21] <soren> chrisccoulson: Ok. I was just wondering since it was around that time my daughter starting waking up at very regular (short!) intervals like that. We'd go pick her up and she'd calm down pretty quickly, but then wake up again ~30 minutes later. Turned out to be her ears. We had a grommet put in and two days later she'd sleep through the night.
[10:22] <soren> chrisccoulson: Teething sounds very plausible too, I just couldn't live with myself not having told you this if it actually turned out to be your daughter's ears too. :) Sleep deprivation is dreadful.
[10:22] <chrisccoulson> soren, oh, interesting. thanks! i'm pretty sure it's my daughters teeth at the moment though, as she's dribbling quite excessively during the daytime
[10:24] <soren> chrisccoulson: The key indicator that put us on to the ears was the fact that she'd calm down very quickly when she sat up. Apparently pressure builds up when they lie down, but is quickly relieved.
[10:27] <chrisccoulson> soren - oh, i probably wouldn't have realised that. are her ears ok now?
[10:27] <soren> chrisccoulson: Totally.
[10:28] <soren> chrisccoulson: A quick visit to the ear-node-throat doctor, a couple of days of waiting and that's been it. Never had problems since.
[10:28] <soren> Heh..
[10:29] <soren> s/node/nose/
[11:31] <rodrigo_> hey seb128
[11:31] <rodrigo_> seb128, so, the clutter-gtk thing you mentioned, do we still need a MIR=
[11:31] <rodrigo_> ?
[11:32] <seb128> rodrigo_, no, thanks
[11:32] <rodrigo_> seb128, ok
[11:32] <seb128> rodrigo_, good morning btw ;-)
[11:32] <seb128> how are you?
[11:32] <rodrigo_> seb128, good afternoon already :)
[11:32] <seb128> is your teeth issue getting better?
[11:32] <seb128> tooth
[11:32] <rodrigo_> seb128, now better, after seeing the dentist, just with one tooth less :)
[11:32] <seb128> ok
[11:33] <rodrigo_> and can't speak very well right now, but at least there's no more pain so far :)
[11:34] <seb128> rodrigo_, well, if you can write on IRC that should be enough ;-)
[11:35] <rodrigo_> yeah :)
[11:36] <rodrigo_> seb128, oh, btw, was looking last night about the gnome-menus patch you told me to disable, but I'm not sure which one you mean
[11:36] <rodrigo_> seb128, in lp:~rodrigo-moya/ubuntu/oneiric/gnome-menus/3_0_0_release
[11:38] <seb128> rodrigo_, sorry that's a call in the postinst that do it
[11:38] <seb128> the list is in the debian directory, it's not a patch
[11:38] <rodrigo_> seb128, ah, ok
[11:39] <rodrigo_> ok, disabling that then before uploading
[11:39] <seb128> thanks
[11:39] <seb128> rodrigo_, don't worry about the gnome-games build failure on armel, that's because pygtk didn't build yet, I will retry the build in a bit
[11:39] <seb128> it built on amd64 and i386 at least ;-)
[11:40] <rodrigo_> seb128, ok, cool
[11:40] <seb128> rodrigo_, we are almost down at the bottom of the GNOME3 updates stack ;-)
[11:40] <rodrigo_> yeah, not many big packages remaining, right?
[11:40] <seb128> not really
[11:40] <seb128> gdm sort of
[11:41] <seb128> it's being worked on the vcs, it's half done
[11:41] <rodrigo_> and empathy
[11:41] <rodrigo_> ah, cool
[11:41] <seb128> that's blocked on kenvandine's telepathy-approver work
[11:41] <seb128> otherwise non default install things
[11:41] <seb128> epiphany-browser, cheese
[11:41] <rodrigo_> ok
[11:42] <seb128> that an a bunch of 3.0.2 updates
[11:42] <rodrigo_> yeah, I did a couple last night
[11:42] <rodrigo_> well, just one, file-roller, the other I didn't finish it
[11:42] <seb128> gucharmap, yelp, g-p-m are to do
[11:43] <seb128> gdl anjuta gnome-bluetooth
[11:43] <rodrigo_> yeah, I'll do some of those as soon as I upload gnome-menus
[11:44] <rodrigo_> seb128, ok, so for gnome-menus, we want to remove the gnome-menus.postinst file?
[11:45] <rodrigo_> http://pastebin.com/KstXqe7j
[11:45] <rodrigo_> that's the diff from my branch with current trunk
[11:46] <seb128> rodrigo_, no, just l8 in your diff
[11:46] <seb128> that's the wrapper call which is building the list of things to ignore
[11:46] <rodrigo_> ah, ok, so just disabling gnome-menus-blacklist
[11:47] <seb128> right
[11:48] <rodrigo_> ok then, building and uploading
[12:01] <pitti> seb128: I'll try a full git head update of RB; it also converts to the newer libnotify, q
[12:01] <pitti> oops
[12:02] <pitti> seb128: ... and to gsettings
[12:06] <pitti> seb128: question: for a gsettings schema which we didn't install before, what causes the gconf->gsettings migration to happeN?
[12:06] <pitti> if "nothing", is the answer "we only really support upgrades from natty to oneiric final, not incremental"?
[12:06] <pitti> didrocks: ^ perhaps you know as well
[12:08] <didrocks> pitti: ~/.local/share/gsettings-data-convert as a list of already converted schemas
[12:08] <didrocks> (by .convert file name it seems)
[12:08] <pitti> didrocks: ah, and we run the converter at each session start?
[12:09] <ricotz> seb128, hi, is colord on your list yet?
[12:09] <didrocks> pitti: /etc/xdg/autostart/gsettings-data-convert.desktop
[12:09] <pitti> didrocks: cheers
[12:09] <didrocks> so yeah :)
[12:09] <didrocks> yw
[12:10] <rodrigo_> hmm, changing tar.gz to tar.bz2 in debian/wacth fails with: bzr: ERROR: Unable to find the needed upstream tarball: gnome-bluetooth_3.0.1.orig.tar.gz
[12:10] <rodrigo_> is there any other place that needs changing?
[12:10] <rodrigo_> fails = it downloads the correct tar.bz2, but then tries to look for the tar.gz, it seems
[12:10] <didrocks> rodrigo_: did you try uscan --verbose
[12:10] <pitti> rodrigo_: hm, not a 3.0 source?
[12:10] <rodrigo_> didrocks, no, trying
[12:10] <rodrigo_> pitti, maybe, let me check
[12:11] <didrocks> possibly it's the previous bzr bd copying an invalid symlink in build-area/, ensure about that as well
[12:11] <rodrigo_> pitti, it's a 3.0 source
[12:11] <didrocks> (got trapped a lot)
[12:11] <pitti> rm -r ../build-area/ might help indeed
[12:11] <rodrigo_> -- In debian/watch, processing watchfile line:
[12:11] <rodrigo_>    http://ftp.gnome.org/pub/gnome/sources/gnome-bluetooth/([\d\.]+)[]/ 	gnome-bluetooth-(.*)\.tar\.bz2
[12:11] <rodrigo_> Unmatched [ in regex; marked by <-- HERE in m/^(?:(?:http://ftp.gnome.org)?\/pub\/gnome\/sources\/gnome\-bluetooth\/)?([\d\.]+)[ <-- HERE ]/?$/ at /usr/bin/uscan line 1556, <WATCH> line 3.
[12:12] <rodrigo_> same with build-area removed
[12:18] <geser> rodrigo_: [] isn't a valid regex ( you start a character class, add ']' to it but never closes the character class)
[12:18] <rodrigo_> http://ftp.gnome.org/pub/gnome/sources/gnome-bluetooth/([\d\.]+)[]/ \
[12:18] <rodrigo_>         gnome-bluetooth-(.*)\.tar\.bz2
[12:19] <fta2> May 31 11:21:08 cube udevd[25783]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
[12:19] <rodrigo_> I guess the [] is wrong?
[12:20] <rodrigo_> yes, using [0-9] there seems to work
[12:20] <geser> rodrigo_: yes, simply remove it
[12:23] <seb128> re
[12:23] <seb128> rodrigo_, gz -> bz2 there?
[12:23] <seb128> rodrigo_, gnome stopped doing gz
[12:23] <seb128> oh, seems you were on that already ;-)
[12:23] <seb128> (sorry I was at lunch)
[12:24] <rodrigo_> seb128, yes, already fixed, thanks :)
[12:24] <seb128> ricotz, no and it's not going to be, check with tkamppeter he's the one who cares about those
[12:24] <seb128> pitti, check /usr/share/GConf/gsettings
[12:24] <seb128> pitti, the .convert in that directory are what describe what keys to map and how
[12:25] <seb128> pitti, the conversion is run once as pointed by didrocks
[12:25] <seb128> pitti, "we only really support upgrades from natty to oneiric final, not incremental"? <- yes
[12:25] <seb128> we can't really force them to happen again without overwriting user tweaks
[12:26] <didrocks> seb128: it doesn't erase the gconf settings isn't it?
[12:26] <ricotz> seb128, alright
[12:26] <didrocks> so we can remove the file I pointed and restart the session to test it (for ourself)
[12:26] <didrocks> am I right?
[12:27] <seb128> didrocks, well, it would overwrite values you wrote in the gsettings config with the old gconf value?
[12:28] <didrocks> seb128: yeah, it's just for testing the migration locally (like the background one which is a fail)
[12:28] <seb128> didrocks, the background one can't be migrating with those scripts
[12:28] <didrocks> not sure what we should do for that one, if we can't specify an uri, we should just provide a new default
[12:28] <seb128> they changed the semantic from a path to an uri
[12:28] <didrocks> yeah, but there is an invalid try right now, isn't it?
[12:28] <seb128> didrocks, no, that was fixed in oneiric, it doesn't try to migrate
[12:29] <didrocks> oh ok, didn't see that upload
[12:29] <seb128> it's just that the default is a gnome background and not one we have
[12:29] <seb128> didrocks, it was in gsettings-desktop-schemas 3.0.2
[12:29] <didrocks> btw, I added this morning a note to the pad that we should have a look at our default and reset them in gsettings world
[12:29] <didrocks> like not unactivating mouse trackpad on typing
[12:30] <didrocks> seb128: thanks, looking
[12:32] <didrocks> seb128: are you sure? we are still on 3.0.1-1
[12:32] <seb128> didrocks, http://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=81e581e67962ecf290f886afd2fbf5767f1970ad
[12:32] <seb128> it's in 3.0.1 sorry about that
[12:32] <seb128> g-d-s is one version behind GNOME ;-)
[12:33] <didrocks> gnome-terminal as well :-)
[12:33] <didrocks> it's a pity to not be able to keep user's desktop background :/
[12:33] <seb128> we should do it
[12:34] <rodrigo_> didrocks, we could do a filename to uri conversion
[12:34] <didrocks> I agree, that's detail that I guess our user are very attached to
[12:34] <seb128> didrocks, see https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-gtk3-gnome3
[12:34] <seb128> [rodrigo-moya] Get custom background images to stay on upgrade (key migration or gsd patching to get the old path and transform it to an uri):
[12:34] <seb128> rodrigo_, you signed for it when we discussed it recently ;-)
[12:35] <rodrigo_> right my "we could do" meant "I'm going to do it" :-)
[12:35] <seb128> didrocks, it will just be some code rather than a .convert
[12:35] <didrocks> nice :-)
[12:35] <didrocks> yeah
[12:35] <seb128> that's a small gnome-settings-daemon patch I guess
[12:36] <didrocks> seb128: not patching /usr/bin/gsettings-data-convert rather?
[12:36] <seb128> could be, I've no strong opinion on it, I will let rodrigo_ figure what's best ;-)
[12:37] <didrocks> we should migrate back as well show_desktop
[12:37] <seb128> not sure about this one
[12:37] <rodrigo_> haven't thought much about it yet, but I guess we could just g-d-s-convert do the key conversion and then do the conversion to an uri in g-s-d
[12:37] <seb128> btw do you have any idea how to make it on by default in unity but not gnome?
[12:37] <didrocks> if we are going to show it by default in unity/unity-2d but not on other, maybe it would be nice to keep what the user eventually tweaked?
[12:38] <seb128> rodrigo_, that seems a clever way to deal with it, check if that's a path and transform it to an uri if needed
[12:38] <didrocks> seb128: gsettings supported multi layer last time I talk to desrt
[12:38] <didrocks> not sure it's documented
[12:38] <seb128> didrocks, well it was on by default I doubt many users turned it off ;-)
[12:38] <didrocks> by we can redo the "on session" stuff
[12:38] <didrocks> right, visible in no ui
[12:39] <seb128> that and also most users are fine with nautilus managing their desktop
[12:39] <didrocks> some did, as we have a bamf bug on this, but yeah :-)
[12:39] <seb128> they just put nothing there if they want to keep it clean
[12:39] <didrocks> (the previous menu application, even after quitting is kept if nautilus doesn't get the focus)
[12:39] <seb128> didrocks, either dconf or using ShowOnlyIn=Unity in the autostart and teach gnome-session about Unity sessions
[12:40] <didrocks> seb128: I still think it would be nice to not enforce that? I need to give it a deeper thought and discuss with desrt
[12:40] <didrocks> we still have the same issue with metacity (for unity-2d)
[12:41] <seb128> enforce what?
[12:41] <seb128> nautilus is a not desktop in the xdg dir not a required component
[12:41] <didrocks> they are using some keys to decide to remove the decoration for example (they should use the dbus interface=
[12:41] <seb128> unity-2d and unity would be "Unity" sessions
[12:41] <seb128> but again a topic where I've no strong opinion
[12:41] <seb128> whatever is easier and give us what we need ;-)
[12:42] <didrocks> yeah, I'll definitively try to think about it in the coming days
[12:43] <seb128> if you have items that need thinking or work just write those on the blueprint
[12:43] <seb128> we will figure how to deal with them over time
[12:43] <Tommeh> Annnnd back to Gnome3.
[12:43]  * didrocks updates
[12:43] <Tommeh> I wish I could find out why Unity keeps freezing on me.
[12:44] <Tommeh> Clearly something weird going on - I can't interact with Unity at all, but the mouse cursor is still working. I can switch to a VT and the dist-upgrade I had running in my terminal window completed despite the window not updating.
[12:45] <Tommeh> Absolutely *random*. Sometimes I could just be switching applications/workspaces.
[13:05] <Tommeh> $ uname -r
[13:05] <Tommeh> 3.0.0-0300rc1-generic
[13:05] <Tommeh> See if we have the same problems with 3.0-rc1 then.
[13:21] <chrisccoulson> pitti - you can delete sources without deleting binaries can't you?
[13:22] <chrisccoulson> i'm going to upload a new thunderbird version this week with it's own language packs (like firefox), but these are currently provided by a separate source package (thunderbird-locales, which should be killed afterwards)
[13:22] <pitti> chrisccoulson: technically it should be possible, yes, but we don't usually do this
[13:22] <pitti> we need to kill NBS packages anyway
[13:23] <chrisccoulson> pitti - in my case, the binaries are being provided from a new source package
[13:23]  * rodrigo_ lunch
[13:23] <pitti> chrisccoulson: that's fine; they'll supersede the older binaries
[13:23] <chrisccoulson> cool, thanks
[13:23] <pitti> chrisccoulson: they need to have a higher version number, of course
[13:24] <chrisccoulson> yeah, they'll have a higher version number
[13:24] <pitti> chrisccoulson: and then the old source needs to be changed to not build the binaries any more, to avoid future version conflicts
[13:24] <chrisccoulson> pitti - i'd like to just remove the old source entirely afterwards (i'm going to replace all of its binaries)
[13:24] <pitti> that's fine
[13:27] <alex3f> mvo: why is there a .candidate property for a package?
[13:29] <mvo> alex3f: thanks for mering back!  in the apt cache, for each package there is a "installed" and "candidate" apt.Version  object. both may be None. e.g. if a package is not installed and no longer downloadable it has no candidate
[13:30] <alex3f> what use has a package without a candidate in the cache?
[13:30] <mvo> alex3f: I added the test to ensure its not crashing if that is the case
[13:30] <mvo> alex3f: not a log of use really, but there are case when that might happen so we need to protect against it
[13:32] <alex3f> isn't posible to have more than one candidate?
[13:32] <alex3f> or the newest version is considered the candidate for installation?
[13:32] <mvo> alex3f: its possible to have many versions, but only one version is the candidate
[13:32] <mvo> alex3f: yeah, normally the newest but apt pinning can be used to alter that
[13:36] <alex3f> I have added __contains__ and __getitem__ to PackageInfo class, I should add a get_candidate method or a candidate property for the package?
[13:37] <alex3f> I'm thinking about wrapping around the candidate to access directly section, summary and description; I'm not sure if this is right
[13:38] <mvo> alex3f: hm, I think its better to have a version_list instead, that can intially be just one entry (the candidate) and then a version that has summary/description/section
[13:39] <mvo> alex3f: does that make sense?
[13:39] <cdbs> rodrigo_: The latest upload of gnome-power-manager to oneiric, does it fix the loading of g-p-m in Unity?
[13:41] <alex3f> mvo: it makes sense, but we should also keep care of the version; maybe a dictionary, having the version as key is better than a list?
[13:42] <mvo> dict is fine with me, as long as there is a clear candidate or default
[13:42] <alex3f> mvo: each package in PackageInfo should have two lists: installed and available (candidates); at least this is something I'm sure PackageKit can offer, for every repo backend
[13:42] <alex3f> yes, a candidate property, currently pointing to the apt.Cache candidate is doable
[13:42] <mvo> alex3f: can there be multiple installed versions for the same name?
[13:42] <alex3f> mvo: yes, 1 sec
[13:43] <mvo> alex3f: oh, woah. ok.
[13:43] <alex3f> for example: multiple kernels installed
[13:44] <alex3f> mvo: or the version is considered part of the name?
[13:44] <mvo> alex3f: in debian they have a different name in this case, do other systems handle this differently?
[13:44] <alex3f> I'm not sure, I'm looking at this right now: http://www.packagekit.org/gtk-doc/introduction-ideas-filters.html
[13:45] <mvo> alex3f: I just want to make sure we don't overdo it :) could you ask in #PackageKit please?
[13:45] <alex3f> yes
[13:45] <mvo> alex3f: if its not needed we can have "property installed, property candidate, list-of available"
[13:45] <mvo> thanks!
[14:00] <andreasn> anyone have screenshots of Nautilus 3.0 using the ubuntu theme?
[14:07] <cdbs> there's no Ubuntu theme for GTK3 yet
[14:07] <cdbs> though its being worked upon
[14:07] <cdbs> andreasn: ^^^^^
[14:07] <andreasn> cdbs, ah
[14:08] <cdbs> kenvandine: Any status on the Ambiance GTK3 theme with Unico?
[14:09] <lucazade> cdbs andreasn http://dl.dropbox.com/u/1338581/varie/Schermata.png
[14:09] <cyphermox> good morning!
[14:09] <andreasn> thanks!
[14:10] <pitti> hey cyphermox, how are you?
[14:10] <lucazade> still requires a lot of work code.launchpad.net/~lucazade/+junk/ambiance-gtk3
[14:11] <cyphermox> hey pitti, doing ok
[14:11] <cyphermox> would be better had evo not ftbfs
[14:11] <pitti> heh
[14:11] <pitti> lucazade: wohoo
[14:11] <cdbs> oh hai lucazade! awesome work!
[14:11] <cyphermox> ah, i know where I screwed up
[14:11] <lucazade> tnx :D
[14:12] <cdbs> cyphermox: I withdraw my message on 'nm not working' . NM 0.8.9997 is working perfectly
[14:12] <cyphermox> oh sweet, because I hadn't seen your "not working" message
[14:12] <cyphermox> you do need to restart NM or reboot for the applet to properly speak to NM, at least for VPNs
[14:12] <didrocks> cyphermox: I fixed it
[14:13] <cyphermox> didrocks: ok, thanks
[14:13] <didrocks> the evo update
[14:13] <cdbs> cyphermox: yeah, a proper reboot was needed
[14:13] <didrocks> yw :)
[14:13] <cdbs> cyphermox: moreover
[14:13] <pitti> at which point will the version number go to 9 - 1e-N ?
[14:13] <cyphermox> just the e-d-s build-depends?
[14:13] <cdbs> cyphermox: it seems there's something wrong with the dependencies on nm packages
[14:13] <didrocks> cyphermox: also the versionning was bad, isn't it? (look at the merge req)
[14:13] <cdbs> cyphermox: they allow you to install network-manager 0.8.9997 with 0.8.4 versions of libnm-*
[14:13] <didrocks> cyphermox: right, now, with the new configure.ac, we have to update evo to latest e-d-s everytime
[14:13] <cyphermox> cdbs: no
[14:14]  * cdbs cross checks
[14:14] <cyphermox> cdbs: it allows libnm-glib2/libnm-util1 to not be removed because other apps still use it
[14:14] <cdbs> cyphermox: okie, that's what confused me
[14:14] <cyphermox> unless you enjoy being told you're not online by evo, empathy, etc ;)
[14:17] <cyphermox> didrocks: right
[14:18] <cyphermox> didrocks: I was almost tempted to do (e-d-s) (>= ${binary:Version}) even if that's still somewhat incorrect, but at least then the e-d-s parts would follow the evo version
[14:22] <cdbs> quit
[14:36] <alex3f> mvo: can you please have a look at: http://bazaar.launchpad.net/~alexeftimie/software-center/backend-refactor/revision/1814?remember=1814&compare_revid=1812
[14:39] <mvo> alex3f: that looks good, would be even better to have some more tests :)
[14:40] <alex3f> mvo: please don't merge it yet
[14:41] <seb128> hum
[14:42] <mvo> alex3f: ok :)
[14:43] <seb128> hey mterry
[14:43] <seb128> mterry, did you try to build indicator-applet with gtk3? (just asking before starting on it)
[14:43] <mterry> seb128, hello!
[14:43] <pitti> hey mterry
[14:43] <mterry> hi, pitti!
[14:43] <kenvandine> mterry, did seb128 talk to you about ido for gtk3?
[14:43] <mterry> seb128, indicator-applet...  no I don't think so
[14:44] <mterry> kenvandine, he mentioned it wasn't done yet?  But not besides that
[14:44] <fta2> mterry, "DEBUG: DuplicityInstance.vala:575: duplicity (22856) exited with value 31"  what's error 31?
[14:44] <kenvandine> mterry, if not... do you think you can pick it up and finish it?
[14:44] <jibel> cyphermox, hi, about 790604 my point is that eth0 is configured in /etc/network/interfaces on a default install and that was not the case before.
[14:44] <jibel> bug 790604
[14:44] <ubot2> Launchpad bug 790604 in network-manager "after installation, nm reports eth0 as a not managed network device" [Medium,Incomplete] https://launchpad.net/bugs/790604
[14:44] <mterry> fta2, gpg failed
[14:44] <cyphermox> jibel: ah, thanks for clarifying
[14:44] <mterry> kenvandine, sure!  I'm doing libbamf now, can do ido after
[14:44] <kenvandine> mterry, lp:~ken-vandine/ido/gtk3-port-wip/
[14:44] <kenvandine> thx
[14:45] <jibel> cyphermox, and only with alternate images not desktop
[14:45] <cyphermox> jibel: you aren't using preseeding are you?
[14:45] <seb128> mterry, ok, I will have a look to indicator-applet since we got the new gnome-panel on gtk3 in
[14:45] <mterry> fta2, you can see list in /usr/share/pyshared/duplicity/log.py
[14:45] <kenvandine> mterry, i was making it gtk3 only, but you should do the magic to make it dual buildable
[14:45] <mterry> seb128, I saw that go by
[14:45] <mterry> kenvandine, yeah
[14:45] <kenvandine> mterry, thx!
[14:45] <jibel> cyphermox, no preseeding, boot the latest alternate and answer to the questions.
[14:46] <seb128> mterry, I will push you next to land your dual build of indicators with gtk2 and gtk3 in oneiric :p
[14:46] <seb128> though I'm trying to get dx guys to do review to start on that
[14:46] <kenvandine> seb128, but after ido right?
[14:46] <cyphermox> jibel: ok. well, this isn't done by NM so the bug probably belong more in debian-installer, but I'll take a look, I think I know where this might be
[14:46] <kenvandine> some of them will depend on ido
[14:46] <seb128> kenvandine, right, though those are done, they have merge requests
[14:46] <kenvandine> ok
[14:46] <jibel> cyphermox, I agree nm is the symptom not the cause.
[14:46] <seb128> kenvandine, mterry did session and messages and applications iirc
[14:47] <kenvandine> cool
[14:47] <kenvandine> great progress :)
[14:47]  * kenvandine needs to prepare for a meeting, bbiab
[14:47] <fta2> mterry, well, i guess deja-dup is not what i'm looking for after all. it's too desktop oriented.
[14:48] <jibel> cyphermox, but you know I'm just a user, I'll leave the diagnosis to your expertise :-)
[14:48] <mterry> seb128, yeah, working on appmenu, but yak-shaving libbamf first
[14:49] <mterry> fta2, it is rather desktop oriented.  What were you trying to do?
[14:49] <cyphermox> jibel: sure, no problem. if you still have that system in the same state though, could you attach the logs from /var/log/installer ?
[14:49] <jibel> cyphermox, sure, I'll update the report
[14:52] <fta2> mterry, backup various stuff between a few machines toward my servfarm, but i don't want to depend on having a display (those auth prompts stopping the backups), nor do i need all those hidden excludes you're passing to duplicity.
[14:53] <mterry> fta2, yeah, sounds like a bad match then.  Maybe you want to use duplicity directly?
[14:56] <fta2> mterry, yep, probably. i've installed deja-dup on 2 boxes, none of which were able to backup a single file, even locally. on the 1st, it's just sitting there doing nothing (and you said in the bug i filed it's too early in the cycle for you to care) and the 2nd seems to start but after a few hundreds files, it re-asks for a password, and restart, in loop (the logs show the cryptic err31)
[14:58] <mterry> fta2, not that I don't care, but that I'm not entirely surprised, as 19.1 was a bit of a UI rewrite.  that second one is interesting.  That's without a DISPLAY?
[14:59] <fta2> mterry, nope, all local, on the desktop i'm currently sitting in front of
[15:00] <mterry> fta2, fascinating...  those aren't "too desktop oriented" issues but rather "doesn't work" bugs.  ;)
[15:02] <fta2> i didn't say those desktop were always there, nor that i wanted to backup stuff in $HOME
[15:02] <fta2> +s
[15:03] <fta2> i need to run, i'll revisit this another time
[15:09] <fagan> hey who is the maintainer of nm in ubuntu I cant remember, I just have a little question
[15:09] <kenvandine> fagan, cyphermox
[15:09] <alex3f> mvo: commited some tests, works fine here, ready for review.
[15:09] <cyphermox> fagan: yup
[15:10] <fagan> cyphermox: what changed in 11.10 for internet detection
[15:10] <cyphermox> fagan: in theory, not much. are you seeing issues?
[15:10] <fagan> cyphermox: well u1 isnt detecting that its connected any more
[15:10] <cyphermox> (although on the backend it's different "states" now
[15:10] <fagan> cyphermox: so that might be it could you walk me through it
[15:10] <cyphermox> fagan: are you just rebuilding it?
[15:11] <fagan> cyphermox: what do you mean?
[15:11] <cyphermox> I mean, that's for a new version right, not the one currently in oneiric?
[15:11] <fagan> cyphermox: its the one in 11.10
[15:11] <fagan> cyphermox: it was undated last night from what I remember
[15:11] <fagan> *updated
[15:12] <cyphermox> ah, then that would be it :)
[15:12] <fagan> cyphermox: so could you explain what the whole states change was
[15:13] <cyphermox> sure hold on
[15:13] <fagan> cool
[15:13] <rodrigo_> cdbs, I don't know, what's the problem with g-p-m loading in unity?
[15:13] <cyphermox> it's essentially related to ipv6 support, so instead of just CONNECTED, now you have *_SITE, *_GLOBAL, etc.
[15:13] <cyphermox> fagan: everything is in the documentation here: http://projects.gnome.org/NetworkManager/developers/migrating-to-09/ref-migrating.html#id598508
[15:14] <fagan> cyphermox: cool thanks
[15:18] <cyphermox> fagan: my bad, since you're looking for the global NM state it would more likely be this: http://projects.gnome.org/NetworkManager/developers/migrating-to-09/spec.html#org.freedesktop.NetworkManager ; scroll down to state(); you'll see there are a few new states, so you can tell more easily whether you really have internet access
[15:19] <fagan> cyphermox: oh ok ill link it in our bug
[15:31] <seb128> does anybody here has a current oneiric desktop iso?
[15:32] <seb128> pitti, ?
[15:32] <pitti> seb128: well, "current" as of three days ago
[15:32] <pitti> apt broke the last two
[15:32] <seb128> pitti, ok
[15:32] <seb128> can you "sudo apt-get remove libgnomeui-0" on it when you have a chance to kvm boot it?
[15:32] <pitti> we could actually start a new run now, though
[15:32] <seb128> I just want to check if I overlooked something
[15:32] <seb128> or if it's only tomboy keeping libgnomeui in
[15:33] <pitti> on my system it's a few libs and tsclient
[15:33] <pitti> but tsclient was ditched anyway, right?
[15:33] <pitti> seb128: will do
[15:33] <pitti> nice, python-gnome2 goes along with it
[15:33] <pitti> seb128: booting
[15:34] <seb128> pitti, right, we said we would get ride of tsclient if favor of reminna pending discuss between robert, you and the security team
[15:34] <seb128> not sure if that happened
[15:34] <pitti> we talked about it at UDS dinner
[15:34] <seb128> rodrigo_, we really need to kick the tomboy libgnomeui depends out
[15:34] <pitti> tsclient is gone from the archive, anyway
[15:34] <rodrigo_> seb128, hmm, yeah
[15:35] <pitti> seb128: s/the//; s/libgnomeui depends/ :-P
[15:35] <seb128> pitti, tomboy's
[15:35] <seb128> lol
[15:35] <seb128> or that ;-)
[15:35] <rodrigo_> seb128, it uses it for the PropertyEditor things, right?
[15:35] <seb128> rodrigo_, correct
[15:36]  * bcurtiswx waves to room
[15:36] <seb128> rodrigo_, you know upstream? can you check with them what's going on in that regard?
[15:36] <seb128> hey bcurtiswx
[15:36] <rodrigo_> yes, I'm on #tomboy all day, so yes checking
[15:36] <bcurtiswx> hi seb128
[15:36] <pitti> seb128: gbrainy gnome-orca python-pyatspi tomboy
[15:36] <pitti> seems gbrainy needs libgnome2.24-cil
[15:37] <pitti> unless gnome-games was updated to 3.0 by now?
[15:37] <seb128> we can kick a game out of needed
[15:37] <seb128> pitti, it's not part of gnome-games
[15:37] <pitti> ah
[15:37] <pitti> atspi will move to atspi2, but I don't know about orca
[15:37] <seb128> the atspi to at-spi2 thing should be sorted, didrocks acked the mirs yesterday
[15:37] <rodrigo_> pitti, yes, gnome-games is 3.0 now, but as seb128 says, gbrainy is not there
[15:39] <didrocks> just waiting on TheMuso to change the dep so that it's brought by default
[15:39] <bcurtiswx> debian uses geoclue in empathy (for maps and location awareness), IIRC this was decided to be left out in Natty.  Is there anything that should keep that functionality out of Ubuntu?
[15:39] <bcurtiswx> for Oneiric
[15:39] <seb128> pitti, gnome-orca depends on python-pyatspi (>= 1.22.0) | python-pyatspi2
[15:39] <mterry> Guh, can't install libwnck-dev and libwnck-3-dev at the same time.  :(  No linking against both in the same source package
[15:39] <pitti> seb128: ah, good
[15:40] <seb128> bcurtiswx, still the same reason, we don't want libchamplain on the CD
[15:40] <bcurtiswx> seb128, OK i'll make sure to keep that out in my rebase
[15:42] <bcurtiswx> I will most likely make a empathy build that enables this for anyone who wants to be bleeding edge with empathy
[15:42] <bcurtiswx> for my PPA
[15:48] <pitti> just finished installing today's alternate in kvm
[15:48] <pitti> nice to see the new look of gnome classic!
[15:48] <pitti> didrocks: ^ FTR, good to have it on that CD still -- unity-2d is a no-go in kvm, keeps crashing :/
[15:49] <didrocks> pitti: hum, weird that it happens only on kvm, still working fine there :/
[15:49] <pitti> kvm has a really crappy graphics card, I suppose it's due to that
[15:50] <didrocks> pitti: yeah, I'm pinging the unity-2d guys still, but I have very few hope
[15:50] <didrocks> pitti: do you have a backtrace or should I let unity-2d guys look?
[15:50] <pitti> didrocks: I can get one; I need to go on fixing udev first, though
[15:50] <pitti> unity-2d in kvm is not a dealbreaker for a1
[15:51] <didrocks> pitti: I asked agateau and kaleo to come here
[15:51] <didrocks> can be https://bugs.launchpad.net/unity-2d/+bug/759803
[15:51] <pitti> and I don't have time to debug it myself right now, sorry
[15:51] <pitti> but should be easy to reproduce; kvm -m 1024 -cdrom oneiric-desktop-amd64.iso
[15:52] <didrocks> ok, not sure when you join agateau, but you can grab daily image and try kvm -m 1024 -cdrom oneiric-desktop-amd64.iso
[15:53] <agateau> didrocks: my adsl router is laughing at you
[15:53] <agateau> s/router/modem/
[15:53]  * agateau starts downloading nevertheless
[15:54] <pitti> I'll be able to send an apport bug with backtrace tomorrow or so
[15:54] <didrocks> agateau: that's what happens living in small village :)
[15:54] <agateau> didrocks: I painfully know that :)
[15:55] <Kaleo> hi pitti
[15:55] <Kaleo> pitti: are you hitting https://bugs.launchpad.net/unity-2d/+bug/759803 ?
[15:56] <pitti> Kaleo: yes, that's exactly my environment
[15:57] <seb128> Kaleo, agateau: there is a stacktrace on https://launchpadlibrarian.net/72618869/launcher3.dbg
[15:57] <seb128> it's from one of the duplicates
[16:01] <didrocks> hum, I think I just improved the speed of the unify script by 20x :-)
[16:03] <seb128> didrocks, you rewrote it in C? ;-)
[16:03] <didrocks> seb128: heh, even without that! :-) just avoiding pooling launchpad too much by small optimizations
[16:04] <seb128> ;-)
[16:04] <fta> mterry, back. on my 1st box, it seems the auth popup was invisible (hidden by unity/compiz?)
[16:04] <didrocks> I was tired to wait for too long to get some test result :-)
[16:06] <fta> mterry, and now that i know that the auth it's requesting is about my user gpg key, i know why it looped on the 2nd box, and it seems to work (minus the unexpected desktop exclusions)
[16:06] <mterry> fta, hrm.  That's likely a 19.x-only bug.  I believe that's fixed in trunk (thought I fixed that in time for 19.1)
[16:06] <mterry> (the auth-hidden-dialog)
[16:07] <mterry> fta, thanks for testing again
[16:07] <cyphermox> jibel: your bug should be fixed in the next iso, I'd say. as long as things are built and ready by then, but I'm not worried
[16:07] <agateau> pitti: what is the depth of the kvm video card?
[16:07] <jibel> cyphermox, nice, many thanks!
[16:09] <fta> mterry, it seems it's no longer a really invisible window, but it's still behind all others windows, so it's not directly visible by the user. yet, there's now that blue thing appearing on the unity badge
[16:10] <mterry> fta, ah, that's normal then.  It's a dialog that requests your attention, but intentionally doesn't pop on top of what you're doing
[16:10] <rodrigo_> anyone running tomboy and unity?
[16:12] <didrocks> rodrigo_: not everytime, but sometimes yeah
[16:12] <seb128> rodrigo_, o/
[16:13] <seb128> well I don't autostart tomboy with the session but I use it sometimes
[16:13] <fta> mterry, intentionally? well, it's blocking the action, and it appears behind the deja-dup settings dialog where i just pressed "back up now". at least in that case, i expect to see the password dialog in front of everything
[16:14] <mterry> fta, ah, that's a 19.1-ism.  I tend to agree.  I can change that for non-automatic backups (like you did)
[16:15] <rodrigo_> didrocks, seb128: does tomboy icon show up on the unity panel when it's running?
[16:16] <seb128> rodrigo_, only when there is an ui open
[16:16] <seb128> (known design weak point in unity for "services")
[16:16] <rodrigo_> seb128, when there is a tomboy window open you mean?
[16:16] <seb128> yes
[16:16] <rodrigo_> ok
[16:16] <seb128> either a note on the main dialog
[16:17] <seb128> rodrigo_, why?
[16:17] <rodrigo_> seb128, tomboy devs were asking, and can't run unity here
[16:18] <didrocks> it's mainly working until you close the main window or if you quit from the launcher (as it doesn't quit the service)
[16:27] <pitti> jasoncwarner, Sweetshark, bryceh, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, cyphermox, mterry, rodrigo_, seb128, tkamppeter, pedro_: meeting reminder in 3 minutes
[16:27] <cyphermox> yup
[16:27] <tkamppeter> hi
[16:28] <Sweetshark> .
[16:30] <pedro_> hello
[16:30]  * kenvandine waves
[16:31] <pitti> meeting time
[16:31] <pitti> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-05-31
[16:31] <pitti> what a hectic day..
[16:31] <tremolux> howdy everyone
[16:31] <didrocks> hey
[16:32] <seb128> hi
[16:32] <pitti> so, let's start with the regular stuff
[16:32] <pitti> kenvandine: anything noteworthy wrt. partners/indicators/etc?
[16:32] <pitti> how's the GTK 3 port coming along?
[16:33] <chrisccoulson> hi!
[16:33] <kenvandine> nothing for partner report, we need to work on getting our meetings rescheduled and getting back to a normal rhythm
[16:33]  * rodrigo_ waves
[16:33] <kenvandine> mterry has been rocking the gtk3 ports of the indicators
[16:33] <mterry> yay
[16:33] <kenvandine> i am about to upload appmenu-gtk with gtk3 support
[16:33]  * pitti yays to mterry
[16:33] <mterry> (I'm stuck on an issue with that -- pitti I'll ping you after this meeting maybe)
[16:33] <pitti> oh, btw
[16:34] <pitti> please avoid new transitions until Thursday
[16:34] <kenvandine> i'll also have an upload of telepathy-indicator today
[16:34] <pitti> i. e. breaking the desktop/CDs
[16:34] <pitti> Alpha-1 is on Thursday
[16:34] <pitti> we'll pretty much pick any daily that works, but as we haven't had one in three days, we need to get one again first
[16:34] <kenvandine> should i hold off appmenu-gtk3 then?
[16:34] <pitti> and the indicator transition will be fairly large, right?
[16:34] <kenvandine> actually it'll land in NEW anyway
[16:35] <kenvandine> pitti, yeah... but that won't happen before thursday
[16:35] <pitti> kenvandine: maybe stash it in bzr for now, and perhaps in the ubuntu-desktop PPA for people to try?
[16:35] <pitti> kenvandine: if it just adds a new binary, it's no problem
[16:35] <kenvandine> new binary, that won't hurt
[16:35] <pitti> right
[16:35] <kenvandine> all the indicators are still waiting for DX to review
[16:36] <kenvandine> that is all i have right now
[16:36] <pitti> thanks!
[16:37] <pitti> kenvandine: would you mind adding a summary to the wiki, for posterity?
[16:37] <pitti> (and people interested in the weekly progress)
[16:37] <pitti> didrocks: thanks for the unity report on the wiki; anything we need to discuss?
[16:38] <kenvandine> sure
[16:38] <didrocks> well, just to hilight if people on natty can confirm the bugs for unity in -proposed
[16:38] <didrocks> if you are on oneiric, you should already have the latest fixes goodness :)
[16:38] <didrocks> and unity-2d is there by default but seems to have issue on kvm as you discussed previously
[16:39] <didrocks> that's it for the unity side :)
[16:39] <Kaleo> pitti: I'm blocked by meetings but did you try other Qt apps?
[16:39] <pitti> Kaleo: no
[16:41] <pitti> tremolux: anythign to discuss for software-center?
[16:41] <tremolux> I think the wiki has it, oh, I should add that we released the 4.0.2 SRU for Natty also
[16:42] <tremolux> and, we have gotten word that there will be some additional UI changes coming in from UX
[16:42] <pitti> ok, thanks
[16:42] <tremolux> we only know general scope currently, details to come  ;)
[16:42] <tremolux> thanks
[16:42] <pitti> no Kubuntu representative, so let's skip that part
[16:43] <pitti> I'd like to go over http://people.canonical.com/~platform/workitems/oneiric/canonical-desktop-team-oneiric-alpha-1.html quickly to see what's left
[16:44] <fta> mterry, gasp, even encrypted, all the filenames are visible on the destination without entering the key, so it's possible to guess the content :P
[16:44] <pitti> desktop-o-default-email-client obviously wins here
[16:44] <mterry> fta, hold up, meeting going on
[16:45] <fta> oops
[16:45] <pitti> chrisccoulson: nothing there seems to be a real blocker right now, so sohuld we move it to a2 wholesale, or did some of the things already happen? (like "meet with"...)
[16:46] <chrisccoulson> pitti - not yet. i'm a bit concerned that i'm currently spending a lot of my time on non-WI stuff, which is eating a lot of my time atm
[16:46] <chrisccoulson> (eg, firefox 5 for lucid, maverick and natty)
[16:47] <pitti> ok, let's just move them over for now
[16:47] <pitti> https://launchpad.net/ubuntu/+spec/desktop-dx-o-bugs-triage-and-workflow is rather undrafted and unapproved, and not strictly our team, so let's ignore that one
[16:48] <pitti> kenvandine: gwibber changes can easily move, I think? I guess alpha-1 was more or less for your personal planning, not a strict deadline?
[16:48] <didrocks> well, just to keep you in touch, I'll finish my wi on it
[16:48] <didrocks> (this evening)
[16:48] <kenvandine> pitti, yeah
[16:48] <kenvandine> pitti, but i will likely have them finished by thursday
[16:49] <pitti> kenvandine: ah, great
[16:49] <pitti> kenvandine: so, want to keep them?
[16:50] <pitti> the remaining ones seem to be a lot of "determine...", "figure out...", "talk to..." stuff, so not really bound by a1 image building etc.
[16:50] <pitti> so let's see how much more we can squeeze out, and I'll move the rest wholesale on Thursday
[16:50] <pitti> anything we shoudl discuss here? blockers? transitions? testing?
[16:50] <kenvandine> pitti, i'll keep them and move what i don't get
[16:52] <pitti> AOB?
[16:52] <cyphermox> o/     ~ubuntu-desktop membership ;)
[16:53] <pitti> oh, still waiting for +1es?
[16:53] <cyphermox> not sure, there are two
[16:53] <cyphermox> ah, yes, missing one
[16:53] <Sweetshark> I could use some more too ...
[16:53] <pitti> anyone else sponsored stuff for cyphermox?
[16:56] <seb128> some but not a lot
[16:56] <pitti> Sweetshark: for PPU?
[16:56] <cyphermox> ok, let's just wait then
[16:56] <pitti> Sweetshark: isn't one +1 enough there?
[16:57] <seb128> cyphermox, some of the recent errors you did on versioning on not updating build-depends make me unsure about the +1 to behonest
[16:57] <cyphermox> seb128: understandable
[16:57] <seb128> but I'm happy if other who did enough sponsoring give their +1
[16:57] <Sweetshark> pitti: https://wiki.ubuntu.com/BjoernMichaelsen/DeveloperApplication AFAIK I need 3 sponsors. But IIRC only you sponsored my stuff anyway.
[16:57] <pitti> Sweetshark: maybe you should apply anyway, and point that out
[16:58] <pitti> Sweetshark: doko didn't sponsor stuff for you?
[16:58] <Sweetshark> pitti: nope
[17:00] <pitti> ok, I think we should adjourn the meeting
[17:00] <pitti> thanks everyone!
[17:00] <seb128> thanks
[17:00] <didrocks> thanks
[17:00] <pitti> (sorry for me being slow today, ping overflow)
[17:01] <pitti> seb128: I'd say try to apply anyway
[17:01] <seb128> (same here)
[17:01] <pitti> sorry, Sweetshark ^
[17:01] <seb128> cyphermox, keep doing a few updates and try to be careful not doing trivial overlooking errors and I will give you a +1 ;-)
[17:02] <seb128> pitti, thanks
[17:02] <rodrigo_> seb128, about the 'discuss creation of u1 addressbook' item you have assigned, any news from the tb guys? I haven't got any mail from them about that
[17:02] <seb128> chrisccoulson, ^
[17:02] <seb128> they were supposed to come discuss it there
[17:02] <rodrigo_> right, I should have asked chrisccoulson :)
[17:02] <seb128> dunno what happened
[17:02] <chrisccoulson> i think mike figured out how to create addressbooks already
[17:03] <rodrigo_> yes, right, it's very easy
[17:03] <Kaleo> pitti: when you have time, if you could run any qt apps in kvm that'd be awesome
[17:03] <chrisccoulson> rodrigo_, oh, that's good then :)
[17:03] <seb128> rodrigo_, the concern was on where it was tb's job to create the u1 adressbook
[17:03] <seb128> rodrigo_, if if some u1 service should do that
[17:03] <seb128> where->whether
[17:04] <rodrigo_> if he hasn't, tell him to look at http://git.gnome.org/browse/evolution-couchdb/tree/plugins/couchdb-contacts-source.c#n42 and the patch we have in evolution-couchdb
[17:04] <rodrigo_> seb128, it is evo-couchdb's job, so also tb's
[17:04] <rodrigo_> although I guess the u1-control-panel could do it indeed
[17:05] <seb128> right, I think they were arguing that tb has nothing to do with u1 and doesn't know what would be the condition to create that adressbook or not
[17:05] <seb128> so it would make sense if some u1 service was creating it when u1 is active
[17:05] <seb128> rather than relying on each email client to do the same thing on their side
[17:05] <rodrigo_> yes, it made sense to have it in evo-couchdb before, but now the u1-control-panel knows when the stuff is installed/activated
[17:06] <rodrigo_> nessita, ^^
[17:25] <pitti> kenvandine: can you please ping me when you released your lock on the meeting page?
[17:25] <rodrigo_> ok, giving up for now, the anesthesics are starting to low down, so pain is coming back, hopefully bbl
[17:25] <rodrigo_> later all
[17:25] <seb128> rodrigo_, take care
[17:26] <seb128> pedro_, hi, do you know any of the brasero guys? could you point them to https://bugzilla.gnome.org/show_bug.cgi?id=646069
[17:26] <kenvandine> pitti, done
[17:26] <pitti> kenvandine: thanks
[17:26]  * kenvandine goes to eat, bbl
[17:26] <seb128> pitti, ^ that bug is why the gir is not installed in debian
[17:26] <seb128> kenvandine, hey
[17:26] <seb128> kenvandine, hum ok, enjoy
[17:27] <pedro_> seb128, hey, yeah i'll ping them about it
[17:27] <seb128> kenvandine, I wanted to chat about getting the new empathy with the indicator patch dropped in oneiric maybe but no hurry
[17:27] <seb128> pedro_, thanks
[17:27] <pitti> seb128: ah, thanks
[17:45] <seb128> pitti, seems you forgot to push the tagged commit of your empathy upload, do you still have it or should I just fix the vcs?
[17:52] <pitti> seb128: sorry; pushed
[17:52] <seb128> pitti, no worry, thanks
[17:52] <seb128> pitti, it's depwait on the natty libnotify name
[17:52] <seb128> but it's not trivial to fix, I will talk to kenvandine about the GNOME3 update when he's back
[17:53] <seb128> well the build-depends is trivial to fix
[17:53] <seb128> but then it fails to build because it doesn't work with nautilus-sendto3
[17:53] <seb128> it's also still pulling libgnome-keyring2 libs in which are NBS
[17:54] <pitti> so, good night everyone!
[17:57] <didrocks> pitti: see you tomorrow!
[17:57] <seb128> 'night pitti
[18:33] <didrocks> seb128: in case you didn't see Julie's new ubuntu-fr mugs (5th edition?): http://latolo.didrocks.fr/post/2011/05/31/Ubuntu-party-mai-2011-%3A-nouveau-mug
[18:34] <seb128> didrocks, nice ;-)
[18:35] <didrocks> it's just in front of me, but without coffee :/
[18:35] <didrocks> that's the missing part ;)
[18:35] <seb128> didrocks, is that julie's blog?
[18:35] <didrocks> seb128: right
[18:35] <seb128> didrocks, so Julie is doing the drawing but not providing the coffee? ;-)
[18:35] <seb128> lazy girls!
[18:35] <didrocks> seb128: no, it's a shame, isn't it? :-)
[18:35] <seb128> indeed
[18:35] <didrocks> I'll tell her you agree :p
[18:36] <seb128> you can ;-)
[18:36] <didrocks> heh
[18:36] <seb128> I live far enough from you to not be scared :p
[18:38] <didrocks> that can motivate her to come to RMLL!
[18:38] <didrocks> of course, without you being warned so that the day you come :-)
[18:38] <seb128> :p
[18:41] <kenvandine> seb128, yeah, i want to get the new empathy in as well
[18:41] <seb128> kenvandine, but...? ;-)
[18:41] <kenvandine> i was going to try to land it right after tp-indicator is uploaded
[18:41] <seb128> ok
[18:42] <kenvandine> i know bcurtiswx was working on rebasing it too
[18:42] <seb128> check with bcurtiswx maybe, I think he's working on the merge
[18:42] <kenvandine> yeah
[18:42]  * bcurtiswx peeks head in
[18:42] <seb128> right, I was just suggesting to maybe move ahead and drop the indicator patch before getting tp-indicator in
[18:42] <kenvandine> but i guess with introducing a new package, we should aim for after A1 isos?
[18:42]  * kenvandine would hate to introduce that big of a regression... no status icon and no messaging menu
[18:43] <seb128> well if that was my call I would drop the indicator patch and get it in tomorrow
[18:43] <seb128> well right now it
[18:43] <seb128> - doesn't build
[18:43] <seb128> - conflict with nautilus3 (or the sendto binary at least)
[18:43] <seb128> - bring gnome-keyring2 in and libs which are nbs
[18:43] <kenvandine> so lots of hurdles :/
[18:44] <bcurtiswx> kenvandine, seb128: yes, when i am home (was on holiday this past weekend) I will work more on the  rebase/merge .  I can include/drop any patch for now.  I was waiting on Ken's help to get indicators working
[18:44] <seb128> kenvandine, it's not like oneiric was working great
[18:44] <seb128> we have no theme, no background, etc
[18:44] <kenvandine> bcurtiswx,can you push your branch somewhere so i can take a quick look?
[18:44] <kenvandine> i guess when you get home
[18:44] <kenvandine> seb128, yeah :/
[18:45] <seb128> kenvandine, well no hurry to get it today
[18:45] <seb128> but I don't want it to take another 2 weeks
[18:45] <seb128> so we should aim for next week at least
[18:45] <kenvandine> well i want to test tp-indicator with empathy3
[18:45] <kenvandine> it works with 2.34
[18:45] <seb128> ok
[18:45] <bcurtiswx> kenvandine, i can try to finish the rebase this afternoon, and i'll let you know.
[18:45] <seb128> so let's say you are on it but I'm just doing a gentle reminder that it needs to get in ;-)
[18:46] <kenvandine> seb128, understand :)
[18:46] <kenvandine> bcurtiswx, thx...
[18:46] <seb128> kenvandine, so maybe let bcurtiswx do his rebase today, review what he did tomorrow and see how to move on
[18:49] <micahg> is software center being ported to GTK3 this cycle?
[18:49]  * micahg saw a maybe on the blueprint
[18:51]  * didrocks waves goodnight (still having my script running in background, we'll check the result later)
[18:51] <bcurtiswx> nite didrocks :)
[18:51] <didrocks> good evening bcurtiswx!
[18:54] <bcurtiswx> empathy without any indicator patches makes it virtually impossible to see when you get a new message if you don't have the contact list open, FYI
[18:54] <bcurtiswx> would be my reasoning as why to wait until indicator stuff can get in before releasing
[18:55] <kenvandine> bcurtiswx, yeah
[18:55] <kenvandine> i am about to get started packaging tp-indicator
[20:52] <seb128> cyphermox, could you merge evolution-exchange on debian?
[20:52] <seb128> it seems like the delta should be small or almost null out of the version update
[20:53] <cyphermox> seb128: yeah, I could do it manually; but using bzr it doesn't seem to work (ubuntu branch is not in sync)
[20:53] <seb128> could you open an udd bug about the out of sync issue?
[20:53] <cyphermox> yeah
[20:54] <seb128> doing it manually work, that's how I do the merges on debian, I never used bzr for those ;-)
[20:55] <cyphermox> ah ;)
[20:55] <cyphermox> I always use bzr
[20:56] <cyphermox> hmm.. maybe it's not quite out of date either
[20:56] <cyphermox> ok, it is
[20:59] <cyphermox> seb128: bug 790876.
[20:59] <ubot2> Launchpad bug 790876 in udd "lp:ubuntu/evolution-exchange is out of date" [Undecided,New] https://launchpad.net/bugs/790876
[20:59] <seb128> cyphermox, thanks
[20:59] <seb128> it should be easy enough to merge by hand, I diffed the debian dirs the other day
[20:59] <seb128> the packaging from debian should just work
[21:00] <seb128> the only question was the patches to build on oneiric
[21:01] <cyphermox> yeah, starting now
[21:01] <cyphermox> (i went to fix temp on the oven ;)
[21:01] <seb128> great
[21:02] <seb128> time to call it a day, if you have an updated merge request just submit it and we will review tomorrow ;-)
[21:02] <cyphermox> sure
[21:02] <seb128> was there anything blocking evolution-mapi btw?
[21:02] <seb128> you mentioned some samba bug the other day?
[21:02] <seb128> was that sorted?
[21:02] <cyphermox> no, just about to upload it now, I was waiting for pbuilder
[21:02] <cyphermox> it's sorted
[21:03] <seb128> great work
[21:03] <seb128> ok, time to go now
[21:03] <seb128> bye everybody
[23:09] <bcurtiswx> kenvandine, empathy depends on "libdconf0 | gsettings-backend" previously they had gotten rid of libdconf0 since it was done at a higher level.  since this has the "or" gsettings-backend, do we still need to change this?
[23:10] <bcurtiswx> previously "we" had dropped libdconf0....
[23:26] <bcurtiswx> anyone know for the options in totem for example, where if you try to play a video and you need other decoders it will give you the option to install
[23:26] <bcurtiswx> if that was hacked by us or upstream?
[23:28] <TheMuso> I thought that was done by us...
[23:28] <TheMuso> Twas a few cycles ago though, so things may have changed in terms of where its maintained.
[23:33] <bcurtiswx> I'd be interested in the code maybe, just to see if i can do something similar with empathy.  I'm just playing around with ideas.
[23:33] <bcurtiswx> TheMuso, thx :)
[23:35] <TheMuso> np
[23:44] <Amaranth> bcurtiswx, TheMuso: We got gstreamer to implement the needed hooks and each distro connects it to their package manager
[23:45] <TheMuso> ah ok
[23:45] <bcurtiswx> Amaranth, ah cool. thx.
[23:52] <jasoncwarner> bryce robert_ancell TheMuso and RAOF, you guys almost ready for meeting?
[23:52] <jasoncwarner> https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-05-31
[23:53]  * bcurtiswx sits in
[23:53] <RAOF> Got a tea in my hand and a freshly minted, only slightly broken mesa package.  Ye haw!
[23:53] <TheMuso> Yup
[23:54] <TheMuso> Hrm a cup of tea sounds nice.
[23:54]  * TheMuso goes to put on kettle.
[23:56] <bcurtiswx> in apt-cache show the size is in KB or B ?
[23:58] <RAOF> KB I think.
[23:58] <bcurtiswx> thx
[23:59] <RAOF> No, I lie.  Bytes.
[23:59] <bcurtiswx> :( <trump> you're fired </trump>