[08:38] <didrocks> sil2100: unity-scope-video-remote uploaded, ensure that the trunk and tarballs are published please :)
[08:38] <sil2100> didrocks: so the scope branches were fine?
[08:39] <didrocks> sil2100: yeah, I bumped the standards-version and Vcs-Bzr as for the other one though
[08:39] <didrocks> so please look at the lintian warnings when building the package :)
[08:39] <sil2100> didrocks: thanks! ;)
[08:39] <didrocks> yw, thanks to you
[08:39] <sil2100> Ooops
[08:40] <sil2100> I think I was in a hurry again, need to burn that down in my head...
[09:05] <sil2100> didrocks: what about the dee update? Is pygi on 12.04 insufficient for the release to make sense?
[09:05] <didrocks> sil2100: I didn't had a hand over a precise machine yet, did you?
[09:07] <sil2100> didrocks: not yet
[09:46] <sil2100> didrocks: hm, would you mind if we'd release nux 3.0 along with unity 6.0..?
[09:46] <didrocks> sil2100: nope, but you need to update the packaging for nux 3.0
[09:46] <didrocks> and merge the ABI branches that jay wants
[09:46] <sil2100> didrocks: since Jay poked me yesterday about that, the ABI change is not big
[09:46] <sil2100> didrocks: will do
[09:48] <sil2100> didrocks: for safety I would target this release for next week though
[09:51] <didrocks> sil2100: well, as quick as possible, doing a release shouldn't take long :)
[10:19] <sil2100> didrocks: just out of curiosity (you probably told us that, but I forgot) - what's the difference between lp:~ubuntu-desktop/unity/ubuntu and lp:ubuntu/unity ?
[10:19] <sil2100> Since I see that those two are different
[10:19] <didrocks> sil2100: now, all the ref are lp:ubuntu/<package>
[10:19] <didrocks> for things that I've moved
[10:19] <didrocks> looks at Vcs-Bzr to ensure you have the right target :)
[10:20] <sil2100> So lp:ubuntu/unity is the 'right' one?
[10:20] <sil2100> Ah, I see
[10:20] <sil2100> But the way those are created is the same, right? They're done through merge-upstream and such?
[10:22] <didrocks> yeah
[10:22] <didrocks> it's the same branch, just the newer location
[11:00] <and471> hi I have an issue which is releated to indicators
[11:01] <and471> basically I want to make an indicator which has a button within one of the menuitems
[11:01] <and471> at the moment I am just using a Gtk.MenuBar, so I can test it out
[11:01] <and471> the issue is that whilst I can see the button after packing it into the Gtk.MenuItem
[11:01] <and471> I can't interact with it
[11:01] <and471> (i.e. press it)
[11:01] <and471> I have tried to link up the button-press-events but it isn't working
[11:02] <and471> here is the code http://pastebin.com/Rbe6B3Wv
[11:02] <and471> any help ?
[11:05] <and471> I should say that by connecting to the button_press_event of the button, I can see that the event is passed along, but the button shows no sign of being pressed
[11:05] <and471> (i.e. looking pressed in)
[11:35] <didrocks> mhr3: hey, do you know when the branch for the music lens I did would be reviewed?
[11:38] <sil2100> didrocks, seb128: even though the video lens/scope for quantal is not yet released (since I'm waiting for David to show up and publish the new tarballs), what about the SRU version of those?
[11:39] <sil2100> Is everything ready and ok for that?
[11:40] <didrocks> for me, it's in quantal, so ok for the SRU :)
[11:47] <didrocks> mhr3: is it on purpose that the gir files are not shipped by libunity?
[11:47] <didrocks> mhr3: we usually ship them in the -dev package, but it's installed on make install
[11:47] <didrocks> like for dee
[11:48] <seb128> didrocks, sil2100, sru got uploaded yesterday and is waiting for review: https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=video
[11:48] <mhr3> didrocks, as in not shipped in the tarball?
[11:48] <didrocks> mhr3: no, I mean, not installed on make install
[11:48] <didrocks> seb128: sweet!
[11:49] <mhr3> didrocks, the gir is not installed? no way
[11:49] <mhr3> lenses wouldn't work then :P
[11:49] <didrocks> mhr3: it's not or I am dreaming :)
[11:49] <sil2100> seb128: \o/ Thank you!
[11:49] <didrocks> mhr3: well, the typelibs are
[11:49] <mhr3> hmmm
[11:49] <didrocks> mhr3: and vapi, this is what they are using, isn't it?
[11:49] <didrocks> the gir is just to generate them
[11:49] <mhr3> the vala ones are using vapi yea, python ones are using typelibs
[11:50] <didrocks> yeah
[11:50] <didrocks> so no need for the .gir files :)
[11:50] <mhr3> well...
[11:50] <mhr3> i'd say it should be there
[11:50] <seb128> sil2100, thank *you* for the work, I just tested and uploaded ;-)
[11:50] <didrocks> but normally, we ship them in -dev, so that bindings depending on bindings can impotr them
[11:50] <didrocks> mhr3: yeah, it should, see ^
[11:50] <mhr3> didrocks, exactly
[11:50] <mhr3> didrocks, could you file a bug?
[11:50] <didrocks> mhr3: I would even do better!
[11:50] <didrocks> file a bug
[11:50] <didrocks> and fix it :)
[11:50] <mhr3> omg!
[11:50] <mhr3> you're awesome!
[11:50] <didrocks> crazy, isn't it? ;)
[11:51] <mhr3> indeed
[12:03] <tjaalton> hey, I've re-added compiz to bug 966744, I've had the same symptoms on two different laptops, and the same "recovery" method
[13:22] <didrocks> sil2100: so, I tried on precise
[13:22] <didrocks> sil2100: yeah, there are overrides python3 support in it
[13:22] <didrocks> mhr3: FYI ^
[13:22] <didrocks> sil2100: so, the dee SRU is needed
[13:23] <didrocks> can you do it now?
[13:24] <mhr3> didrocks, hmmm
[13:24] <mhr3> didrocks, aaaaah, there's an actual python3-gi package
[13:24] <didrocks> mhr3: yep
[13:24] <mhr3> i guess installing that would help :)
[13:25] <didrocks> it can ;)
[13:28] <sil2100> didrocks: ok, but hm, how should I do the package now exactly? Do we need to build it twice again? If so, how do we force that?
[13:28] <didrocks> sil2100: oh right, you didn't look into that?
[13:28] <didrocks> sil2100: ok, I'll do it for quantal
[13:28] <didrocks> then, I'll backport it
[13:30] <sil2100> didrocks: I looked into normal ways of doing it - I never did tricks like 'building package twice' in debian/rules ;)
[13:31] <didrocks> sil2100: can you look if there is a bug about that in dee and if not, opening one?
[13:32] <sil2100> didrocks: you mean, bug for the missing overrides?
[13:33] <didrocks> yep
[13:33] <sil2100> didrocks: there is one:
[13:33] <sil2100> https://bugs.launchpad.net/dee/+bug/905085
[13:33] <didrocks> sil2100: excellent, thanks
[13:35] <sil2100> didrocks: the test case is missing since we didn't manage to start testing the SRU package even
[13:36] <didrocks> sil2100: well, the test case is quite easy
[13:36] <didrocks> sil2100:  but for quantal, it seems that dee needs a new release
[13:38] <didrocks> sil2100: you are taking care of that?
[13:38] <didrocks> also, it seems that wrapping this into a package is failing on make install
[13:40] <sil2100> hm, so, we need a new dee release for quantal as well?
[13:42] <sil2100> Ok, hm, just tell me how to perform the double build for it to work for both python2 and python3 and I'll do the release ;)
[13:45] <didrocks> sil2100: sure, when we talk about an unity release, it's the whole stack
[13:45] <didrocks> lenses, dee, bamf, libunity, compiz, unity, nux…
[13:45] <didrocks> sil2100: yeah, I'm adding an upstream fix as well so that it works
[13:50] <sil2100> didrocks: thanks!
[13:51] <sil2100> didrocks: I'm testing the new nux (3.0) and unity on my PPA right now
[13:51] <didrocks> good
[13:51] <sil2100> didrocks: so... when we'll be releasing unity 6.0, along with it we have to release bamf, dee, libunity, nux and compiz?
[13:52] <sil2100> But actually compiz for quantal was released this week right..?
[13:52] <didrocks> sil2100: the lenses as well
[13:52] <didrocks> yeah, compiz can wait
[13:52] <sil2100> Ok, so just everything besides compiz
[13:52]  * sil2100 notes it down
[13:52] <mhr3> lenses didn't change yet
[13:52] <sil2100> mhr3: so only video lens, righ?
[13:52] <sil2100> We'll have to rebuild them anyway
[13:52] <mhr3> no you wont
[13:53] <mhr3> libunity is abi stable
[13:53] <sil2100> Because of the major version bump in unity, the assets changed place
[13:53] <sil2100> They're in 6 now
[13:53] <mhr3> oh, that needs fixing in the lenses then iirc
[13:53] <didrocks> mhr3: well, the music lens is my branch is merged :p
[13:53] <sil2100> So this needs a bump anyways :(
[13:53] <mhr3> it's not read out from anywhere
[13:54] <sil2100> mhr3: it's hard-coded?
[13:54] <mhr3> didrocks, oh, is it?
[13:54] <mhr3> sil2100, let me check but i think it is
[13:54] <didrocks> mhr3: "if" ;)
[13:54] <didrocks> sil2100: FYI: http://bazaar.launchpad.net/~ubuntu-desktop/dee/ubuntu/revision/245
[13:54] <didrocks> sil2100: so, that in quantal and the precise SRU
[13:55] <sil2100> mhr3: since I know when I used the unity 6.0.0 test package I built, the lenses were missing graphics
[13:55] <sil2100> Since I didn't rebuild them
[13:56] <mhr3> sil2100, yea, the .lens files have the version hardcoded
[13:56] <mhr3> but other than that a rebuild wouldn't be needed
[13:57] <sil2100> mhr3: true
[14:02] <sil2100> didrocks: ah, hacky!
[14:02] <sil2100> didrocks: thanks
[14:02] <didrocks> sil2100: only way to not move to cdbs and anyway, we don't want to build anything else for nothing :)
[14:10] <sil2100> davidcalle: hi!
[14:10] <sil2100> didrocks: I've been waiting for you... ;)
[14:10] <davidcalle> hi sil2100
[14:10] <sil2100> (that's never a good thing!)
[14:10] <didrocks> you meant davidcalle
[14:10] <sil2100> Ah, ouch, yes!
[14:10] <sil2100> davidcalle: that was to you actually ^
[14:11] <davidcalle> sil2100, :)
[14:11] <sil2100> davidcalle: anyway, didrocks switched the video lens and scope branches to the new, 'cool' architecture - which means I had to release new tarballs for quantal
[14:11] <sil2100> davidcalle: sould you upload those on the main project page?
[14:12] <davidcalle> didrocks, thank you!
[14:12] <sil2100> And, probably also, merge in the changes I made to lens and scope trunks? Since we're getting rid of the debian/ directory there
[14:12] <didrocks> davidcalle: yw ;)
[14:12] <sil2100> davidcalle: I'll post the links in a moment
[14:13] <sil2100> davidcalle: http://ubuntuone.com/6uJF8oLJzKmLIXHWNjBzsU <- lens new tarball
[14:13] <sil2100> davidcalle: http://ubuntuone.com/37ldvMpNknG1bTaUINn3km <- scope new tarball
[14:13] <davidcalle> sil2100, so the idea is to have a trunk and distro branches containing the packaging?
[14:14] <sil2100> davidcalle: yes, trunk should have only sources, while a packaging branch has actually packaging + sources, created in a neat way
[14:14] <sil2100> So, actually I would like you to merge in the changes from these branches:
[14:14] <sil2100> https://code.launchpad.net/~sil2100/unity-lens-videos/scope_trunk_PRE <- for the scope branch you have
[14:14] <sil2100> And
[14:14] <sil2100> https://code.launchpad.net/~sil2100/unity-lens-videos/trunk_PRE <- for the lens branch you have
[14:15] <sil2100> Sorry for all the chaos in your project, but it's for unifications and future simplifications sake
[14:16] <sil2100> So, what I would need:
[14:16] <davidcalle> Good chaos actually.
[14:16] <sil2100> 1) uploading new tarballs, I made them out of the debian-less trunks
[14:16] <sil2100> 2) pulling those few changes from the *trunk* branches I made
[14:17] <sil2100> This way will be safe, as didrocks already checked all these things I prepared yesterday
[14:18] <davidcalle> Ok. What about the packaging branches, is there a naming convention, "unity-lens-videos/ubuntu" ?
[14:19] <sil2100> davidcalle: I think they're available through lp:ubuntu/unity-lens-video etc.
[14:19] <sil2100> didrocks: could you confirm that ^ ?
[14:21] <davidcalle> sil2100, oh right. I'm asking in case I need to do a daily ppa for some tests. To know which packaging branch I should merge in the recipe.
[14:21] <sil2100> didrocks: btw. for dee, should I use lp:ubuntu/dee or lp:~ubuntu-desktop/dee/ubuntu ?
[14:27] <sil2100> didrocks: when should I use the first one and when the other? Since I see sometimes lp:ubuntu/* is not up-to-date
[14:28] <sil2100> So confusing
[14:29] <didrocks> sil2100: I'm pushing for every new project thoses to lp:ubuntu/</package>
[14:29] <didrocks> for every new release
[14:30] <didrocks> that's why I explained last week :)
[14:30] <didrocks> so we are in the transition period
[14:30] <didrocks> for now, use the branch I pointed
[14:30] <didrocks> davidcalle: btw, it would be cool to have one project per source
[14:31] <sil2100> didrocks: what about lenses? Since I'll need to mod them up a bit - should I use lp:ubuntu* or the old one?
[14:31] <didrocks> so a unity-scope-remote
[14:31] <didrocks> sil2100: start always from the old one
[14:31] <didrocks> until it's transitionned
[14:31] <didrocks> as told, Vcs-Bzr is the ref :)
[14:32] <davidcalle> didrocks, ok. I'm creating it. I suppose I will need to change the watch file in the packaging branch too.
[14:32] <sil2100> ACK
[14:32] <didrocks> davidcalle: yep :)
[14:32] <sil2100> didrocks: will you help davidcalle with all the transitioning now? ;)
[14:32] <davidcalle> sil2100, trunks are now trunk only.
[14:33] <sil2100> davidcalle: yay \o/
[14:33] <sil2100> davidcalle: did you also upload the tarballs?
[14:33] <davidcalle> Yes
[14:33] <davidcalle> 3.6 release for both
[14:33] <sil2100> \o/
[14:33] <sil2100> Awesome
[14:46] <davidcalle> didrocks, sil2100: https://launchpad.net/unity-scope-video-remote (trunk and latest tarball are in) Now, do I just need to change the upstream in https://launchpad.net/+ubuntu/+source/unity-scope-video-remote ?
[14:47] <didrocks> davidcalle: well, we can do it for next release, do not worry :)
[14:47] <davidcalle> didrocks, ok then, thank you both for all the sanity :)
[14:48] <didrocks> yw ;)
[14:49] <sil2100> davidcalle: np ;)
[14:53] <sil2100> didrocks: so, regarding lens/scopes we're all done, yes?
[14:53] <sil2100> didrocks: I mean the video lens and scopes
[14:53] <didrocks> sil2100: yeah, for this one, we are all done :)
[14:54] <sil2100> didrocks: ok... now regarding dee - is everything done here as well? I mean, the precise branch is precisely the same as the one you did, right?
[14:54] <didrocks> sil2100: hum no?
[14:54] <didrocks> you need two things
[14:54] <didrocks> making the new dee release for quantal
[14:54] <didrocks> with all the fixes for build and such
[14:54] <didrocks> (new vala)
[14:55] <didrocks> and just cherry-pick the override fix + packaging for precise
[14:55] <sil2100> didrocks: ah, ok ok, hm, ok