[09:28]  * thorwil waves to djsiegel 
[09:28] <djsiegel> hey dude
[09:28] <djsiegel> how are you, thorwil?
[09:28] <thorwil> djsiegel: fine, thanks. and you?
[09:28] <djsiegel> thorwil: so much work before UDS!
=== MacSlow is now known as MacSlow|lunch
=== MacSlow|lunch is now known as MacSlow
=== njpatel_ is now known as njpatel
[17:37] <hyperair> tedg: what happens to an appindicator using application if indicator-{application,applet} isn't installed?
[17:38] <hyperair> i'd like to know because of banshee-extension-appindicator depending on indicator-{application,applet}.
[17:38] <tedg> hyperair: It should fall back to using the notification area
[17:38] <hyperair> tedg: okay, so i should remove the dependency?
[17:38] <tedg> hyperair: Uhm, yeah, I don't think there should be.
[17:38] <hyperair> okay
[17:39] <tedg> hyperair: Thanks for the cli packaging patch
[17:39] <hyperair> tedg: no problem.
[17:39] <tedg> hyperair: I have no clue what it did, but I assume that you do :)
[17:39] <hyperair> tedg: yes, i do :)
[17:40] <hyperair> tedg: the policy violations aside, you had binary/libappindicator0-cil:: binary-arch, where binary-arch is an internal CDBS rule that depends upon binary/libappindicator0-cil somehow or other.
[17:41] <hyperair> tedg: and in the redefined binary-arch rule, you did the dh_*cli* things.
[17:41] <hyperair> tedg: so the ordering was off
[17:41] <hyperair> this is why..... don't use CDBS ;-)
[17:41] <tedg> hyperair: Hmm.  Okay.  And so what did that create on the backend, just the messed up dependency?
[17:42] <hyperair> tedg: in the end it was missing clilibs, which is the cli equivalent of shlibs.
[17:42] <hyperair> tedg: so similarly, ${cli:Depends} was missing things, just as a missing shlibs would leave missing things from ${shlibs:Depends}
[17:42] <tedg> hyperair: There's another Mono patch that I just merged, not sure how important it is: https://code.launchpad.net/~bratsche/indicator-application/assemblyinfo/+merge/23407
[17:42] <tedg> hyperair: Ah, okay.  I see now.
[17:43] <hyperair> pardon my english, it seems a little off today.
[17:44] <tedg> hyperair: Do you need that patch in the package before the Banshee extensions rebuild?
[17:44] <hyperair> tedg: ideally.
[17:44] <tedg> k
[17:45] <hyperair> er make that a definite yes.
[17:45] <hyperair> will that be ubuntu3?
[17:45] <hyperair> i'll tighten the dep further
[17:46] <tedg> Sure, yeah.  I'll get that one together.
[17:46] <tedg> We'll make it 3
[17:48] <hyperair> okay
=== mpt_ is now known as mpt
[22:03] <Nafai> tedg: Around? :)
[22:06] <tedg> Nafai: Yes.
[22:07] <Nafai> So I've done as much as I can do to figure out the bluetooth bug and could use a little direction
[22:07] <Nafai> here's a summary of what I've found:
[22:07] <Nafai> https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/558841/comments/5
[22:07] <ubot4`> Launchpad bug 558841 in gnome-bluetooth (Ubuntu) "bluetooth "devices" menu item not working in bluetooth indicator (affects: 1) (heat: 6)" [High,In progress]
[22:11] <tedg> Hmm, that's definitely odd.  bratsche, do you have any ideas? ^
[22:18] <Nafai> would it be helpful if I pastebined the bluetooth-applet code or such and pointed you to the appropriate functions to see what it is doing?
[22:19]  * bratsche clicks
[22:32] <Nafai> Here's some links to code: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/558841/comments/6
[22:32] <ubot4`> Launchpad bug 558841 in gnome-bluetooth (Ubuntu) "bluetooth "devices" menu item not working in bluetooth indicator (affects: 1) (heat: 6)" [High,In progress]
[22:55] <Nafai> any ideas? :)
[23:14] <tedg> Nafai: I'm sorry I don't.  I'm guessing unless he got distracted, bratsche doesn't as well.
[23:14] <tedg> I'm trying to chase down a dbusmenu bug that is sucking.
[23:14] <tedg> :(
[23:14] <Nafai> :(
[23:14] <tedg> Nafai: I'd look at the GtkAction stuff.  It's probably doing something different.
[23:15] <tedg> Nafai: See if you can look at that tree and see what it's up to.
[23:15] <Nafai> I know there was some changes in the last little while in the way libappindicator handled that, so I'll look
[23:15] <Nafai> because there haven't been any changes to this part of the bt indicator code
[23:17] <tedg> Nafai: You can try building old versions of libappindicator -- see which version it broke in.
[23:17] <tedg> Nafai: That might narrow it down.
[23:18]  * Nafai nods
[23:18] <Nafai> yeah, I might do that
[23:19] <Nafai> Is there an easy way of finding out which version was shipped with alpha3?
[23:19] <Nafai> that's when the bug reporter reports it working and then he upgraded to beta2 and it broke
[23:19] <tedg> Nafai: I'd just look at the dates
[23:19] <Nafai> ok
[23:19] <tedg> Nafai: It should be pretty close
[23:58] <Nafai> okay, I narrowed it down to the version where the problem arises
[23:58] <Nafai> http://bazaar.launchpad.net/~ubuntu-desktop/indicator-application/ubuntu/revision/98
[23:59] <Nafai> uh, so confused
[23:59] <Nafai> I don't see anything there that I imagine could cause this regression :(