[01:01] <kenvandine_wk> eeejay: see my merge request?
[02:14] <vorian> oh brother
[02:15] <Hobbsee> hm?
[02:15] <vorian> this channel is not registered 
[02:17] <tedg> vorian: How do we register it?
[02:17] <vorian> that's gonna be tricky :)
[02:17]  * tedg is relatively new to this stuff.
[02:18] <vorian> tedg: first things is this, a group contact needs to be established
[02:18]  * vorian gets another linky
[02:18] <vorian> http://freenode.net/group_registration.shtml
[02:20] <tedg> vorian: Okay, that makes sense.  We're closely related to the Ubuntu folks.  Does it make sense to put us under their contact, or to create another?
[02:20] <tedg> vorian: Or does that imply a namespace?
[02:20] <vorian> i would create another, but it is up to you all, and the #ubuntu IRC council
[02:21] <vorian> yeah, that would imply a namespace
[02:21]  * vorian would stick with this one
[02:23] <tedg> vorian: Thanks for the information, I think that davidbarth would probably be a good contact, but he's asleep right now.
[02:23] <vorian> no problem
[02:23] <tedg> vorian: I'll send him a mail, and hopefully get this started tomorrow.
[02:23] <vorian> excellent
[02:24] <tedg> vorian: What should we do about #dx?  Wait until this is registered?
[02:24] <vorian> there's not much that can be done about it
[02:24] <tedg> Can you set the topic to "everyone's moved to #ayatana" ?
[02:24] <tedg> So atleast people know we're not leaving them behind :)
[02:25] <vorian> what if a nintendo fan comes in, and thinks "cool, we moved!"
[02:25] <tedg> Then we'll work on making them a Ubuntu fan ;)
[02:25] <vorian> :)
[02:26] <tedg> Perhaps text like "If you're looking for the Ubuntu DX channel it is now #ayatana"
[09:19] <mpt> bratsche, notification-daemon treats title text verbatim too
[09:20] <mpt> Try it: notify-send "Joe's phone is online" "fish &amp; chips"
[09:21] <mpt> Compare with notify-send "Joe&apos;s phone is online" "fish &amp; chips"
[09:21] <mpt> notification-daemon renders the "&apos;" as "&apos;"
[09:21] <mpt> so, so should notify-osd.
[11:59] <davidbarth> eeejay: hi eitan
[12:01] <davidbarth> do you have the latest pidgin package (pidgin + indicator stuff)?
[12:24]  * MacSlow -> lunch
[14:20] <eeejay> hey tedg!
[14:20] <tedg> Good morning eeejay
[14:21] <eeejay> tedg: kenvandine_wk: we need some quick decisions about the python bindings, eh?
[14:21] <tedg> eeejay: Yes.
[14:22] <tedg> kenvandine_wk: Did you get an initial upload sponsored?
[14:22] <kenvandine_wk> yes
[14:22] <kenvandine_wk> with the patch
[14:22] <eeejay> kenvandine_wk: patch that lets it build against 0.1.5?
[14:23] <kenvandine_wk> yes
[14:23] <eeejay> ah, cool
[14:23] <kenvandine_wk> eeejay: tedg has a branch that fixes some stuff that broke with 0.1.5
[14:23] <kenvandine_wk> eeejay: and i have a merge request too
[14:23] <kenvandine_wk> think you can bring all that together and make a 0.0.3?
[14:23] <eeejay> kenvandine_wk: you bet..
[14:24] <kenvandine_wk> eeejay: rock!
[14:24] <kenvandine_wk> thx
[14:25] <eeejay> kenvandine_wk: so this branch add some important dist files, bumps the version..
[14:25]  * eeejay looks
[14:25] <kenvandine_wk> yeah
[14:25] <kenvandine_wk> the last tarball had 0.0.1 in configure.ac
[14:25] <kenvandine_wk> but was a 0.0.2 tarball
[14:25] <eeejay> hehe
[14:26] <kenvandine_wk> also the COPYING files... we had some complaints in getting it reviewed about that
[14:26] <kenvandine_wk> since it is dual licensed
[14:26] <kenvandine_wk> so i did that
[14:26] <kenvandine_wk> as well as the files in tests
[14:26] <eeejay> kenvandine_wk: where does the build patch you made live?
[14:26] <kenvandine_wk> tedg's branch
[14:26] <kenvandine_wk> one sec
[14:26]  * eeejay didn't know it is dual licensed
[14:27] <kenvandine_wk> it is in the source files :)
[14:27] <kenvandine_wk> i assumed you did that
[14:27] <kenvandine_wk> lp:~ted-gould/indicator-applet/python-bindings-dont-know-what-im-doing
[14:27] <eeejay> kenvandine_wk: doh!
[14:27] <tedg> eeejay: We had to do LGPL v2/3 because some apps can't link against one or the other.
[14:28] <eeejay> kenvandine_wk: tedg: ah.. phew, i thought i was just being sloppy
[14:28] <kenvandine_wk> hehe
[14:28] <kenvandine_wk> eeejay: i think merging my branch and tedgs into your's... then create a tarball
[14:28] <eeejay> tedg: i couldn't get your branch to work with listen-and-print.py, is it supposed to?
[14:28] <kenvandine_wk> eeejay: it would also be great if the tests files got installed as docs
[14:29] <tedg> eeejay: I didn't try that.  I asked kenvandine_wk to check out Gwibber and Gajim.
[14:29] <tedg> eeejay: Probably I broke the listener interface.
[14:29] <eeejay> tedg: but they don't use the listener iface
[14:29] <tedg> I said in the branch name that I didn't know what I was doing ;)
[14:30] <eeejay> tedg: true, i guess you aren't liable then
[14:30] <kenvandine_wk> i tested the im example, gwibber and gajim
[14:30] <eeejay> kenvandine_wk: i updated trunk to work with 0.1.5
[14:30] <eeejay> kenvandine_wk: without tedg's branch
[14:30] <kenvandine_wk> gajim actually only half works... but i think that is because the gajim guys changed my patch :)
[14:30] <tedg> eeejay: Do you see an easy thing that I broke?
[14:31] <kenvandine_wk> eeejay: ok... i tested it with tedg's changes
[14:31] <eeejay> tedg: you didn't break anything that was not broken already
[14:31] <tedg> eeejay: I was just trying to change to O instead of s and i for the various indicator struct pointers.
[14:31] <eeejay> tedg: but you failed to fix the listener iface :)
[14:32] <tedg> Does it make sense to mark it as broken for 0.0.3 then?
[14:32] <eeejay> tedg: yeah, that won't work. you obviously didn't know what you were doing ;)
[14:32] <eeejay> tedg: yes, it does
[14:32]  * eeejay wrote about it extensively in the merge request
[14:33] <eeejay> https://code.launchpad.net/~ted-gould/indicator-applet/python-bindings-dont-know-what-im-doing/+merge/5366
[14:34] <tedg> eeejay: Heh, hadn't gotten to that mail yet.
[14:34] <tedg> eeejay: Yes, everything you say there :)
[14:36] <kenvandine_wk> eeejay: hummm... it did work though :)
[14:36] <eeejay> kenvandine_wk: what worked?
[14:37] <tedg> eeejay: So without the boxing, could we have something reasonable that would link against 0.1.5?  It seems so if we drop listener, right?
[14:37] <kenvandine_wk> tedg's code
[14:37] <eeejay> tedg: exactly
[14:37] <tedg> And the fact that you manually undid the enum, that would be "unpythonic" but work.
[14:37] <eeejay> kenvandine_wk: with gwibber and gajim? yeah, it should work with those
[14:37] <eeejay> kenvandine_wk: the listener interface is broken
[14:38] <kenvandine_wk> eeejay: ok... so it works fine for everything we know about now
[14:38] <eeejay> kenvandine_wk: which only matters if you are implementing a new indicator-applet-like app
[14:38] <kenvandine_wk> so not "awefule"
[14:38] <kenvandine_wk> aweful even
[14:38] <kenvandine_wk> but we should fix it
[14:38] <hyperair> does anybody know if Bug #345837 is reallly a duplicate of Bug #345296?
[14:38] <eeejay> tedg: the enum actually is not relevant, since the listener iface is broken
[14:38] <hyperair> their descriptions seem to show that the bugs really are different.
[14:39] <kenvandine_wk> eeejay: ok... so you already have these issues fixed?
[14:39] <eeejay> kenvandine_wk: yeah, we should keep the gwibber and gajim folks happy
[14:39] <tedg> eeejay: Except for the signal coming from the server to say that someone is interested, right?
[14:39] <tedg> eeejay: I think, interested_added and interest_removed both use the enum.
[14:40] <eeejay> tedg: which symbol does that?
[14:40] <tedg> I doubt that Gwibber or Gajim are using that though.
[14:40]  * eeejay looks at server.h
[14:40] <kenvandine_wk> eeejay: today is freeze... so if we are getting a fix in, lets do it real soon :)
[14:40] <eeejay> kenvandine_wk: okie dokes
[14:41] <tedg> hyperair: Seems odd to me too.  MacSlow do you know if those bugs are dups ^^
[14:41] <hyperair> tedg: it would be nice if that oen could get fixed before jaunty, because it's really annoying if you use media keys with banshee.
[14:42] <tedg> So, to summarize.  If we go with my "don't know what I'm doing branch" and make a 0.0.3 we'll link against 0.1.5 but the listener interface will be broken.  And we've got a plan to make that better for 0.0.4.  Is that a good summary eeejay kenvandine_wk?
[14:42]  * eeejay moves swiftly
[14:43] <eeejay> tedg: the relevant changes from your branch have been in trunk for a while
[14:43]  * eeejay acts swiftly
[14:43] <kenvandine_wk> eeejay: well how hard is fixing the listener interface?
[14:43] <tedg> eeejay: Heh, okay.  Are you going to spin a 0.0.3 then or should I?
[14:43] <kenvandine_wk> it would be nice to make a 0.0.3 with that
[14:44] <kenvandine_wk> tedg: cause what we have now is as good as that... no need to spin a release :)
[14:44] <eeejay> tedg: let me get the branch in shape, we could all agree, and i will cut a release
[14:44] <kenvandine_wk> tedg: 0.0.2 was uploaded with the patch from your branch
[14:45] <tedg> kenvandine_wk: Yeah, I'd like to get something cleaner than what I did if possible.
[14:45] <kenvandine_wk> tedg: yeah... but i am hoping we can fix the other issue at the same time :)
[14:45] <tedg> kenvandine_wk: I'm not a python fan, and I think it shows :)
[14:45] <kenvandine_wk> hehe
[14:45]  * kenvandine_wk would chose python over C any day... but lets not have that debate
[14:49]  * tedg is going to make a T-shirt: "You can take my semicolon from my cold dead hands."  :)
[14:52]  * eeejay rejects tedg's branch because of his hateful comments
[14:53]  * hyperair kills tedg and takes his semicolon
[14:53] <eeejay> kenvandine_wk: would you mind testing trunk one last time before i upload the tarball?
[14:53] <hyperair> tedg: i believe it's s/take/pry/
[14:54] <kenvandine_wk> eeejay: certainly
[14:54] <tedg> hyperair: Heh, need to spend more time at NRA rallies... research...
[14:54] <kenvandine_wk> eeejay: is it ready now?
[14:54] <eeejay> kenvandine_wk: yup!
[14:55] <eeejay> kenvandine_wk: lp:~indicator-applet-developers/indicator-applet/indicate-python <- to avoid confusion
[14:56] <hyperair> tedg: ?
[14:57] <tedg> hyperair: I believe that the guns phrase that is taken from is an NRA one.
[14:57] <kenvandine_wk> testing nwo
[14:58] <eeejay> i think charlton heston would say that at NRA rallies
[14:58] <hyperair> tedg: no idea. i see it everywhere
[14:58] <eeejay> or michael moore lead me to believe that
[15:04] <eeejay> kenvandine_wk: not so smooth?
[15:06] <Hobbsee> gah.  Did this latest version of pidgin stuff get tested?
[15:06] <Hobbsee> i'm now getting pidgin segfaulting.
[15:06] <kenvandine_wk> eeejay: sorry... phone rang
[15:06] <kenvandine_wk> testing now
[15:06] <eeejay> kenvandine_wk: phew, thought you were in debugging craze
[15:10] <tedg> Hobbsee: pidgin-libnotify?  There is a big pidgin bug with Jabber right now.
[15:10] <kenvandine_wk> eeejay: not good
[15:10] <eeejay> kenvandine_wk: crasher?
[15:10] <Hobbsee> tedg: oh, there was another change there.  I assumed it was notify killing it.
[15:11] <kenvandine_wk> File "/usr/lib/python2.6/dist-packages/indicate/__init__.py", line 26, in <module>
[15:11] <kenvandine_wk>     from _indicate import *
[15:11] <kenvandine_wk> ImportError: /usr/lib/python2.6/dist-packages/indicate/_indicate.so: undefined symbol: indicate_server_show_indicator_to_user
[15:11] <tedg> Hobbsee: It seems to be related to gstreamer -- I don't really get how though.
[15:11] <kenvandine_wk> eeejay: ^^
[15:12] <Hobbsee> tedg: oh, fun.  
[15:12] <eeejay> kenvandine_wk: checking now..
[15:13] <Hobbsee> tedg: thanks.  Wish I knew how to disable the jabber bit!
[15:13] <tedg> Hobbsee: I don't think there's a way, but if you uninstall one of the gstreamer plugin packs, I think bad, it gets better.
[15:14] <Hobbsee> tedg: thanks
[15:16] <eeejay> kenvandine_wk: i don't have that symbol in my version, are you certain you installed it in  /usr/lib/python2.6/dist-packages/indicate?
[15:16] <kenvandine_wk> yes
[15:16] <kenvandine_wk> i did a make dist
[15:16] <kenvandine_wk> then build the package from that tarball
[15:16] <kenvandine_wk> let me compare files
[15:17] <eeejay> kenvandine_wk: if you didn't give it /usr as the prefix, it should be in /usr/local
[15:17] <kenvandine_wk> oh
[15:17] <kenvandine_wk> humm
[15:17] <kenvandine_wk> eeejay: i installed it from a package
[15:17] <kenvandine_wk> it didn't use my tarball
[15:17] <kenvandine_wk> hang on
[15:18] <eeejay> you scared me for a moment
[15:18] <eeejay> i usually give it some arbitrary prefix, and set PYTHONPATH to that
[15:18] <kenvandine_wk> i like testing with packages
[15:18] <kenvandine_wk> i am a nut that way
[15:19] <eeejay> heh
[15:20] <hyperair> davidbarth: you marked bug #345837 as a dupicate of #345296 right? are you sure it's really a duplicate?
[15:20] <hyperair> davidbarth: the descriptions seem rather different.
[15:22] <davidbarth> hyperair: hi, let me check again
[15:23] <hyperair> davidbarth: alright 
[15:24] <davidbarth> hyperair: you're right this one is not a duplicate
[15:25] <davidbarth> it is the issue with the close_notification_handler
[15:25] <hyperair> hmm
[15:25] <hyperair> haven't looked at notify-osd's code yet
[15:25] <Hobbsee> tedg: speaking of pidgin, has anyone tested the notifications on dist-upgraded machines?  I found some strangeness, before i wiped my ~/.purple directory, and started again
[15:25] <hyperair> but it would be good if the priority for this bug could be raised a little
[15:25] <davidbarth> but there was anohter bug I thought with banshee/rhythmbox bubbles crashing into synchronous ones
[15:25] <hyperair> it's very annoying, and very visible when you use banshee with media keys
[15:26] <davidbarth> hyperair: the problem has been fixed (sort of) by not sending confirmation bubbles from gnome-settings-daemon
[15:26] <hyperair> davidbarth: rhythmbox doesnt have this issue, because it updates the existing bubble rather than deleting the old and spawning a new
[15:26] <davidbarth> hyperair: from an architecture point of view, that was not great
[15:26] <hyperair> hmm. why not?
[15:26] <davidbarth> so the bug should not occur anymore
[15:26] <davidbarth> even if the corner-case still exists in the layout code of n-osd
[15:26] <hyperair> davidbarth: it won't occur as often, but it'll still occur.
[15:26] <tedg> Hobbsee: I haven't tried that specifically.  Though I haven't noticed any bugs related to something like that.  What was the weirdness?
[15:27] <hyperair> davidbarth: e.g. when i adjust my volume when pidgin fires up a notification
[15:27] <hyperair> davidbarth: and there are multiple
[15:27] <davidbarth> hyperair: ah, and pidgin /force/ closes the bubbles?
[15:27] <kenvandine_wk> eeejay: ok... it works
[15:27] <kenvandine_wk> the listener still shouldn't work right?
[15:27] <Hobbsee> tedg: new messages in pidgin not showing up in the envelope at all (although it would show up most of the time with the little black notification)
[15:27] <eeejay> kenvandine_wk: sweet!
[15:28] <hyperair> davidbarth: you don't need to force close the bubbles for it to happen i think
[15:28] <eeejay> kenvandine_wk: right
[15:28] <eeejay> kenvandine_wk: pushing a tarball now
[15:28] <kenvandine_wk> thx
[15:28] <hyperair> davidbarth: but okay, supposing you change your volume while banshee's switching songs, you'd get that.
[15:28] <Hobbsee> tedg: ie, if you missed the black notification, there was absolutely no indication of a new message
[15:28] <davidbarth> hyperair: the bug with update was fixed, as well as other potential visual collisions between sync and async bubbles
[15:29] <tedg> Hobbsee: That might have been related to a couple of bugs that we just fixed in indicator-messages, they had the possibility of getting lost.
[15:29] <davidbarth> it's in the lates tarball of today (not yesterday)
[15:29] <davidbarth> brb
[15:29] <tedg> Hobbsee: Hopefully those are fixed, I'm curious why removing .purple would solve that.
[15:29] <tedg> Hobbsee: Honestly, I'm hoping they were unrelated :)
[15:30] <Hobbsee> tedg: I'm not sure.  I tested it a few days ago, removed ~/.purple, set up the user accounts again, and it worked fine.
[15:30] <hyperair> davidbarth: i see, then it should be considered fixed then =\
[15:30] <Hobbsee> tedg: might be worth trying to find some people to test that
[15:33] <eeejay> tedg: i don't think i have perms to register a new release in the 0.1 indicator-applet series
[15:34] <bratsche> Oh nice, I think this new text filter works well.
[15:35] <tedg> eeejay: Okay, made it: https://edge.launchpad.net/indicator-applet/0.1/python0.0.3
[15:35] <tedg> eeejay: Can you add files?
[15:35] <eeejay> tedg: yep, thanks
[15:38] <eeejay> tedg: kenvandine_wk: released
[15:38] <tedg> eeejay: Yeah!  Great!
[15:39] <kenvandine_wk> great
[15:39] <kenvandine_wk> i already subscribed motu-release :)
[15:39] <kenvandine_wk> bug 358483
[15:40] <eeejay> sweet
[15:41] <kenvandine_wk> asac and james_w are looking at it
[15:43] <kenvandine_wk> eeejay: mind filing a bug about the listener so we can track it?
[15:43] <eeejay> kenvandine_wk: yup, will do
[15:43] <kenvandine_wk> thx
[15:43] <kenvandine_wk> please subscribe me too :)
[19:16] <maco> away
[19:17] <maco> whoops