[04:31] <bschaefer> thomi, you were right about that gdb crash
[04:31] <bschaefer> http://pastebin.ubuntu.com/1062024/
[04:31] <bschaefer> causes it
[04:32] <thomi> hah!
[04:32] <bschaefer> I somehow ended up pinging you in this channel haha
[04:32] <thomi> meh
[04:32] <bschaefer> thomi, I was trying to figure out to prove that it was the problem...
[04:32] <bschaefer> soo it's sigc++ fault
[04:32] <bschaefer> haha
[04:33] <thomi> bschaefer: more likely it's the dodgy template code we grabbed off the Internet
[04:33] <bschaefer> thomi, o yeah
[04:33] <thomi> bschaefer: can you update the bug report please?
[04:33] <bschaefer> thomi, but you can't compile code with a lambda with sigc::slot<bool>  if it has a return
[04:33] <bschaefer> thomi, yup!
[04:34] <thomi> cheers
[04:35] <thomi> maybe we'll get a template guru to tell us what we're doing wrong
[04:36] <bschaefer> thomi, yeah, templates are ... odd, my professor has always said java did generics better haha
[04:36] <bschaefer> thomi, before I go, can you review this haha? https://code.launchpad.net/~brandontschaefer/unity/opening-dash-in-scale-mode-SRU
[04:36] <bschaefer> thomi, it was already accpetd in trunk
[04:37] <thomi> sure
[04:37] <bschaefer> awesome thanks. I can go to bed happy I got that gdb problem down to 1 file haha
[04:38] <thomi> bschaefer: approved
[04:38] <bschaefer> thomi, awesome thanks!
[04:38] <bschaefer> im off now, have a good night
[07:51] <sil2100> hm
[07:52] <sil2100> didrocks: since I will be essentially trying to release unity for quantal today, is there a possibility of 'freezing' trunk for today? By 'freezing' I mean disabling merging of new fixes
[07:52] <didrocks> sil2100: well, that's the discussion I tried to had with popey last week
[07:52] <didrocks> as you will define the process release, I understood that mmrazik and popey designed something without trunk freeze
[07:52] <didrocks> so see with them
[07:56] <didrocks> sil2100: also, what about the dee fix?
[08:49] <seb128> didrocks, I guess sil2100 falled asleep ;-)
[08:49] <didrocks> seb128: I'm under the same impression, asking and then sleeping :)
[09:04] <sil2100> ! ;)
[09:04] <sil2100> didrocks: almost done
[09:04] <sil2100> (I have a broken compiz/unity now so I don't see all chat windows)
[09:06] <didrocks> sil2100: sorry, what is almost done? dee or unity? :)
[09:37] <sil2100> didrocks: I had dee in my mind, but actually I've been thinking - do we need to add python3 to the build deps now?
[09:37] <didrocks> sil2100: not really, we just need to ship the additional gir file and we'll be fine
[09:38] <didrocks> as automagic dep doesn't work anyway and not in the gir area itself
[09:42] <sil2100> ACK
[09:52] <sil2100> didrocks: hm, to make this work, I need to modify the original commit I cherry-picked and, so to say, 'hack it' a bit (in dee)
[09:53] <sil2100> didrocks: should I do a quilt patch for that?
[09:53] <sil2100> didrocks: since I'll be modifying a Makefile
[09:54] <didrocks> sil2100: no, just fix it and propose it upstream
[09:54] <didrocks> as par of upstream branch
[09:54] <didrocks> then, cherry-pick your upstream commit into your packaging branch
[11:14] <sil2100> didrocks: did you try running a built unity with the new compiz/nux from -proposed?
[11:16] <didrocks> sil2100: well, as you can see in -proposed, there is a new unity rebuilt against those there :)
[11:16] <sil2100> didrocks: and it works for you?
[11:16] <didrocks> as it was compulsory because of the compiz ABI breaks
[11:16] <didrocks> sil2100: define "works" :)
[11:16] <sil2100> didrocks: does it run and look correctly ;)?
[11:17] <didrocks> sil2100: yep
[11:17] <sil2100> hm hm
[11:17] <sil2100> I'll try installing that then too
[11:18] <didrocks> what's your issue?
[11:19] <sil2100> I built a new packages on my system basing on the -proposed nux etc. and even though unity works, everything (panel, dash, launcher) are completely transparent
[11:19] <sil2100> This happens both on trunk of unity and the current version, after re-building
[11:19] <sil2100> But maybe something's broken on my side when I'm building those locally
[11:20] <sil2100> Yep, the packages from -proposed work normally
[11:20] <sil2100> Shit
[11:26] <didrocks> sil2100: I just tried another build, works wonderfully here :)
[11:26] <sil2100> So I need to find out why it's broken on my system
[11:26] <sil2100> didrocks: thanks
[11:39] <sil2100> Yup, something's wrong with my system, uh
[11:40] <didrocks> what was it?
[11:41] <sil2100> Don't know yet, but even building the very same sources gathered from apt-get source results in a binary with all unity transparent - where the packages from -proposed work fine (very same sources)
[11:41] <sil2100> So maybe I've got broken dependencies or something...
[11:43] <sil2100> didrocks: btw. is there a way to enable -proposed for my local sil2100 PPA? For build-dependencies?
[11:50] <didrocks> sil2100: you can have a ppa build-dep on another ppa
[11:50] <didrocks> sil2100: not sure if it works on real archives. I think it won't
[12:02] <sil2100> hm, dee is failing to build on quantal
[12:05] <didrocks> sil2100: the dee fix seems to have made the test failing, can you look at it, please? https://jenkins.qa.ubuntu.com/job/automerge-dee/68/console
[12:05] <sil2100> didrocks: it's not because of the fix
[12:05] <sil2100> didrocks: it was failing before as well - it's a quantal problem
[12:05] <sil2100> didrocks: I asked someone from my team to look into that
[12:06] <didrocks> sil2100: nice, keep me in touch then :)
[12:06] <didrocks> sil2100: the merge of the dee fix is blocked on that
[12:07] <sil2100> didrocks: I know...
[12:07] <sil2100> didrocks: I just want to prepare first everything related to unity, since A2 is tomorrow
[12:07] <didrocks> sil2100: well, it won't be in alpha2 :) but yeah, we should have releases of all the stack
[12:07] <didrocks> lenses, nux, unity
[12:08] <sil2100> didrocks: unity won't?
[12:08] <sil2100> Oh
[12:08] <sil2100> Ok
[12:08] <sil2100> ...;)
[12:08] <didrocks> well, alpha2 is tomorrow
[12:08] <didrocks> meaning that we are testing the iso already
[12:08] <didrocks> since Monday
[12:09] <didrocks> we don't push the crack on tomorrow and declare the image alpha
[12:09] <didrocks> it got certifications and tests
[12:09] <sil2100> Ah, since we had like INTENSE testing plans for today - hehe, ok, thanks for clarification
[12:09] <sil2100> ;)
[12:09] <sil2100> We'll do those anyway!
[12:18] <sil2100> didrocks: https://bugs.launchpad.net/dee/+bug/1017277
[12:19] <didrocks> mhr3: ^
[12:19] <sil2100> mhr3: could you look into that?
[12:22] <mhr3> y u break gobject-introspection gnome?
[12:24] <sil2100> mhr3: ;)
[12:50] <mhr3> sil2100, https://code.launchpad.net/~mhr3/libunity/more-api-changes/+merge/112340
[12:50] <mhr3> eeh
[12:50] <mhr3> not that
[12:50] <mhr3> sil2100, http://paste.ubuntu.com/1062498/
[12:54] <sil2100> mhr3: checking that now
[12:58] <sil2100> mhr3: it seems to work! Could you request a merge..?
[13:13] <sil2100> mhr3: pretty please with cherries on top... :)
[13:37] <sil2100> mhr3: if you're particulary busy, I can push the MRQ for you instead - if you don't mind ;)
[13:37] <mhr3> sil2100, sorry, just got back from lunch
[13:37] <mhr3> i'm on it
[13:38] <sil2100> mhr3: thanks! Since this bit is blocking another merge that is needed for the dee SRU
[13:45] <mhr3> sil2100, https://code.launchpad.net/~mhr3/dee/quantal-compability/+merge/112358
[13:45] <sil2100> mhr3: thank you!
[13:45] <mhr3> you get the pleasure of approving it
[13:45] <mhr3> fwiw i checked that it doesn't break precise
[14:12] <sil2100> What the...
[14:13] <sil2100> mhr3: you saw https://jenkins.qa.ubuntu.com/job/automerge-dee/69/console ?
[14:13] <sil2100> mhr3: I was actually building the dee package on my quantal machine and nothing like that popped up
[14:15] <mhr3> weird, i was also running both make and make check and it passed
[14:16] <mhr3> sil2100, i guess we use different flags in tests/
[14:17] <mhr3> not sure why the build has yet different ones
[14:17]  * sil2100 sighs
[14:20] <sil2100> mhr3: do you have a neat idea on how to fix this?
[14:24] <mhr3> sil2100, https://code.launchpad.net/~mhr3/dee/remove-thread-init/+merge/112368
[14:25] <mhr3> oh, should have pushed it to the old branch
[14:25] <mhr3> a sec
[14:25] <sil2100> mhr3: does this deprecate the old one?
[14:26] <mhr3> sil2100, pushed to the old one, nevermind this one
[14:28] <sil2100> mhr3: thanks!
[14:28] <sil2100> btw.
[14:28] <sil2100> mhr3: about this one: https://code.launchpad.net/~sil2100/dee/hack_python3_overrides/+merge/112308
[14:28] <sil2100> mhr3: didrocks asked me to push this upstream, since without it python3 overrides are not working at all
[14:28] <sil2100> They won't be installed
[14:29] <mhr3> sil2100, it's breaking build and not respecting prefix, we can't accept that
[14:29] <sil2100> And the merged in previous commit that added python3 overrides in fact overwrites the 2.7, thus breaking everything ;/
[14:29] <didrocks> mhr3: can you get it fix the right way then?
[14:30] <mhr3> let me ask gnome people
[14:30] <sil2100> mhr3: we need to get this at least fixed somehow, since right now it just breaks python2.7 overrides
[14:30] <mhr3> sil2100, if you want fast fix, revert the addition of the python3 branch
[14:31] <sil2100> mhr3: well, we could do that, but the whole point of the dee SRU was to fix python3 - so hm, we'd just have to wait with the SRU until a proper fix is done
[14:31] <sil2100> Or add the whole thing as a distro patch
[14:32] <sil2100> didrocks: maybe just quilt the whole thing..?
[14:33] <didrocks> sil2100: well, let's see what mhr3 can come with :)
[14:34] <didrocks> sil2100: as it's an upstream issue in the end
[14:34] <mhr3> didrocks, that's what we get after you push to our branch? :P
[14:34] <sil2100> didrocks: ok, then we'll wait with the SRU
[14:37] <didrocks> mhr3: completely, you ignored the MR for a month :p
[14:38] <didrocks> mhr3: it's just that my local install of the dee override tricked me in my test I guess
[15:06] <mhr3> didrocks, sil2100, it's it just me? doing "from gi.repository import ..." with python3 on P just gives me "No module gi.repository"
[15:06] <mhr3> so why are we even trying to sru that thing?
[15:06] <didrocks> mhr3: it's just you
[15:07] <didrocks> ah on precise
[15:07]  * didrocks doesn't have a precise box handy
[15:07] <didrocks> waow, we shipped some python3 Quickly template, so I was expecting that gobject-introspection to be here at least
[15:07] <didrocks> I never tested it myself
[15:07] <didrocks> so I have we have the packages :)
[15:08] <mhr3> also, all the other override files from upstream pygobject are only in python2.7 dir, so it wouldn't work either
[15:08] <didrocks> mhr3: yep, I'll try to look at precise later on. Speaking about quantal/trunk now :)
[15:09] <mhr3> didrocks, so try to import Gio on Q
[15:09] <didrocks> mhr3: it works, i can totally tell you that
[15:09] <didrocks> mhr3: this is what my lens is using :)
[15:09] <didrocks> (on Q)
[15:09] <mhr3> the question is if the overrides work
[15:09] <didrocks> I didn't run into any issue for what I'm using
[15:10] <mhr3> try DBusProxy
[15:10] <didrocks> if there are other parts having issue, we ship the override for python3 as well
[15:10] <didrocks> mhr3: what do you try to demonstrate here?
[15:10] <mhr3>       proxy = Gio.DBusProxy.new_sync(...)
[15:10] <mhr3>       result = proxy.MyMethod('(is)', 42, 'hello')
[15:11] <mhr3> use some real service and see if this works
[15:11] <didrocks> mhr3: well, I have enough to make the lens working and answering in python 3
[15:11] <didrocks> apart from this lens
[15:11] <mhr3> (taken from /usr/share/pyshared/gi/overrides/Gio.py)
[15:11] <didrocks> for the rest, we should as well shipping the overriding files for them
[15:11] <didrocks> but that doesn't mean that Dee hasn't a bug in not shipping python3 override file
[15:12] <mhr3> didrocks, nonetheless upstream pygobject will surely need to solve this as well :)
[15:12] <didrocks> mhr3: indeed
[15:12] <mhr3> and clearly they're the experts for this
[15:12] <didrocks> but still I don't see what's your point here and how it prevents solving it for Dee
[18:42] <davidcalle> seb128, thanks for reminding me about errors.ubuntu.com : both top bugs are fixed in trunk, ready for a SRU.
[18:51] <seb128> davidcalle, thanks! popey said they would SRU the fixes
[18:52] <davidcalle> Great :)
[18:52] <popey> nice one davidcalle