[03:02] <smspilla1> 2
[03:03] <smspilla1> :(
[03:03] <smspilla1> new versions of tmux continue to be trolling me it seems
[03:58] <Mirv> mardy / kenvandine: yep, can be done, just prepare a clean patch (against 5.0.2 at this point, although I've started with 5.1 as well)
[04:01] <Mirv> mardy: also, file a bug against qtdeclarative-opensource-src
[05:38] <mardy> Mirv: OK, will do that today
[05:39] <didrocks> hey mardy! seems you are under pressure to get all webcreds building today :)
[05:39] <didrocks> mardy: good luck! as everything is stuck on it ;)
[06:21] <didrocks> veebers: thomi: hey, around?
[06:22] <veebers> didrocks: I am, just
[06:22] <didrocks> veebers: I'm running the apps tests here
[06:22] <didrocks> veebers: getting a lot of failure on http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-ati/18/console
[06:22] <didrocks> veebers: like that: http://paste.ubuntu.com/5734934/
[06:22] <didrocks> veebers: I'm sure it's a dep error or something not available, can you think of anything?
[06:23]  * veebers takes a look
[06:24] <veebers> didrocks: hmm, does http://10.97.0.1:8080/ work for you?
[06:24] <didrocks> veebers: yes, connected to the vpn?
[06:25] <veebers> didrocks: yeah I am :-P let me try something else
[06:25] <veebers> hmm, just had to reset vpn :-\
[06:25] <didrocks> interesting…
[06:29] <veebers> didrocks: hmm, can't seem to ssh into that machine, just checking something on the KVM
[06:29] <didrocks> veebers: do you need to ssh to it?
[06:29] <veebers> didrocks: I was hoping to check a couple of things quickly
[06:29] <didrocks> veebers: I thought that the stacktrace would just right a bell :)
[06:30] <didrocks> veebers: also, seems that now the tests are stuck
[06:30] <veebers> didrocks: sorry not off the top of my head, I think I have an idea what's happening but wanted to poke around
[06:30] <didrocks> but there is an autopilot process running
[06:30] <didrocks> ok :)
[06:30] <didrocks> /usr/bin/python /usr/bin/autopilot run webbrowser_app -v -r -rd /var/local/autopilot//videos/ -f xml -o /var/local/autopilot//junit//webbrowser_app.xml is running
[06:30] <didrocks> but not activity for 15 minutes
[06:32] <veebers> didrocks: oh, this isn't for the Unity or autopilot test (duh silly me)
[06:34] <didrocks> no
[06:34] <didrocks> it's apps autopilot tests
[06:39] <veebers> didrocks: My initial thoughts are it looks as though the launched application doesn't have the dbus object path: '/com/canonical/Autopilot/Introspection' (and/or the right  Interface to go with it)
[06:39] <didrocks> veebers: do you think it's because we don't run with latest sdk?
[06:40] <didrocks> if this is what expose the interface to it
[06:40] <veebers> didrocks: I couldn't say with certainty sorry. Do you mind if I much around in the KVM (I may need to install something)
[06:40] <didrocks> jibel: ^
[06:40] <didrocks> veebers: depends if you are in the container
[06:41] <veebers> I'm pretty sure launching the web-app with -testability should do what we need
[06:41] <veebers> didrocks: oh, ah because it's not the physical machine anymore right?
[06:41] <didrocks> veebers: we are in a lxc container
[06:41] <didrocks> which is a physical macine
[06:41] <didrocks> but not the host
[06:43] <veebers> didrocks: hmm, am I able to ssh in to poke around a little?
[06:44] <didrocks> veebers: do you know how to ssh inside the container?
[06:44] <jibel> veebers, you can use the KVM it's PS_radeon something on https://10.97.0.2
[06:44] <didrocks> yeah, better to use the KVM, you will stay inside the container :)
[06:44] <veebers> didrocks: no I don't think so. I'm not sure how much things have changed with the move to Otto
[06:45] <veebers> jibel: ah ok, thanks :-)
[06:45] <jibel> veebers, or ssh to dx-autopilot-ati then sudo lxc-attach -n saucy-i386-20130604-1531
[06:45] <veebers> jibel: is there a way to confirm that the KVM I have open is to the correct machine?
[06:46] <jibel> veebers, you're connected to PS-Radeon-HE-AP (HD5000) ?
[06:46] <jibel> if so, it is the correct machine
[06:48] <veebers> jibel: awesome, thanks
[06:51] <veebers> didrocks: hmm, I think the issue is that webbrowser-app is never actually launched. I tried: `/usr/bin/webbrowser-app -testability`
[06:52] <veebers> didrocks: and the error I get is the same as this extract from the logs: http://paste.ubuntu.com/5734971/
[06:52] <veebers> unless I need to do more than just that command at the command line
[06:52] <didrocks> veebers: so the wrong sdk can be a good road?
[06:52] <didrocks> veebers: anyway, autopilot shouldn't be stuck as it is now
[06:52] <veebers> didrocks: it appears so.
[06:52] <veebers> didrocks: agreed
[06:53] <didrocks> veebers: mind looking at why it's stuck while it is?
[06:53] <veebers> didrocks: any idea why the end of this log is the syslog (not autopilot.log)? http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot-ati/18/consoleFull
[06:53] <didrocks> veebers: or should we kill it
[06:53] <didrocks> veebers: because we are monitoring all logs
[06:53] <didrocks> (relevant ones)
[06:53] <didrocks> like syslog, .xsession-errors…
[06:57] <veebers> didrocks: makes sense
[06:57] <didrocks> veebers: do you know why autopilot is stuck (meaning, should we kill it to end the run?)
[06:58] <veebers> didrocks: I just had a look, sorry no idea why it's not returning/finishing. Perhaps related to the issues it was having during the run
[06:58] <didrocks> veebers: well, it should be protected against that, as otto as a timeout for it for instance :)
[06:59] <veebers> didrocks: I don't think there is anything else I can check, so you may have to kill it
[06:59] <didrocks> ok
[06:59] <veebers> didrocks: I'm supposed to be making dinner, my girlfriend is getting hungry :-) I'll be online later tonight though too.
[07:00] <didrocks> veebers: ok, enjoy your dinner
[07:00] <veebers> will do
[07:00] <veebers> didrocks: let me know if you have any other issues and I can look into them
[07:00] <didrocks> veebers: ok, will do :)
[07:00] <didrocks> the sdk is building
[07:00] <didrocks> so will rerun
[07:01] <veebers> didrocks: maybe tonight (or tomorrow) I will fire up a VM and try to duplicate what happened here
[07:01] <didrocks> great! :)
[07:56] <didrocks> dednick: hey, how are you?
[07:56] <dednick> didrocks: good morning. fine thanks and you?
[07:57] <didrocks> dednick: quite pressed by time for landing everything to saucy (touch & unity/100 scopes)
[07:57] <didrocks> sil2100: hey!
[07:57] <didrocks> dednick: not sure you are the right guy for it, but it seems that the testsuite is segfaulting, at least on amd64 for unity
[07:57] <didrocks> dednick: https://launchpadlibrarian.net/141697500/buildlog_ubuntu-saucy-amd64.unity_7.0.0daily13.06.05-0ubuntu1_FAILEDTOBUILD.txt.gz
[07:59] <dednick> didrocks: hm. ok, i'll try taking a look. havent got a set in ages, so it may take some time. Also, I'm still on raring, so may not be the same
[07:59] <didrocks> dednick: can be as well random, but maybe good to fix?
[07:59] <didrocks> dednick: let me try rebuild in case
[08:00]  * didrocks waits for i386 results before relauching
[08:00] <didrocks> launching*
[08:06] <sil2100> didrocks: hello!
[08:07] <sil2100> didrocks: saucy unity build issues?
[08:07] <sil2100> uuuuu, see a lot of red stacks on jenkins
[08:08] <sil2100> didrocks: QA stack is red as well, problems with xpathselect it seems
[08:09] <sil2100> veebers: ping
[08:09] <sil2100> veebers: are you still around?
[08:10] <didrocks> sil2100: you know that I finished at 11PM and started at 7AM for those? need to get the things moving to have saucy and not waiting :)
[08:10] <didrocks> sil2100: so xpathselect fixed by Mirv, waited for the fix to be merged
[08:11] <didrocks> and then relaunching QA stack
[08:11] <didrocks> sil2100: all stacks were red/yellow this morning
[08:11] <didrocks> dednick: sil2100: segfault confirmed on i386: https://launchpadlibrarian.net/141698375/buildlog_ubuntu-saucy-i386.unity_7.0.0daily13.06.05-0ubuntu1_FAILEDTOBUILD.txt.gz
[08:11] <didrocks> sil2100: this should be the priority now I guess
[08:12] <didrocks> mhr3: maybe you know about this testsuite ^
[08:12] <didrocks> (hey!)
[08:12] <didrocks> not sure who else can help
[08:12] <dednick> didrocks: just building unity now. hopefully i can confirm on my box.
[08:13] <dednick> *assuming it builds ok
[08:13] <didrocks> let's hope so :)
[08:13] <didrocks> sil2100: see also https://launchpadlibrarian.net/141698680/buildlog_ubuntu-saucy-i386.unity-scope-evolution_0.1daily13.06.05-0ubuntu1_FAILEDTOBUILD.txt.gz
[08:13] <didrocks> sil2100: as we have a new evolution, maybe that can be the cause
[08:14] <sil2100> OH SHIT
[08:14] <sil2100> ;)
[08:14] <sil2100> dednick: just be sure to have saucy running
[08:15] <davidcalle> didrocks, argh
[08:15] <didrocks> davidcalle: oh, you're around, can you do me a favor?
[08:15] <didrocks> davidcalle: installing latest dee
[08:15] <didrocks> davidcalle: and testing the scopes
[08:16] <davidcalle> didrocks, where can I find it?
[08:16] <didrocks> as we are under python3.3 and it's using site-packages
[08:16] <dednick> sil2100: i'm not on saucy
[08:16] <didrocks> not sure it works :)
[08:16]  * greyback_ rebooting, hopes his efi setup isn't broken
[08:16] <didrocks> davidcalle: https://launchpad.net/~ubuntu-unity/+archive/daily-build
[08:16] <sil2100> dednick: since the issue started appearing after we switched to saucy
[08:16] <sil2100> dednick: so I guess it's a saucy toolchain issue ;)
[08:17] <dednick> sil2100: upgrading now
[08:21] <davidcalle> didrocks, it works
[08:22] <didrocks> davidcalle: \o/ one less thing to handle :)
[08:22] <didrocks> so the override is read, great!
[08:22] <davidcalle> didrocks :)
[08:32] <davidcalle> didrocks, so, I can confirm the issue with gir1.2-ecalendar-1.2 in saucy. It only contains /usr/share/doc files...
[08:34] <didrocks> davidcalle: Laney did the evo update, maybe you can ping him?
[08:34] <davidcalle> didrocks, yup
[08:40]  * sil2100 is upgrading as well
[08:41] <sil2100> Mirv: thanks for the reviews! Will fix those issues in a minute
[08:42] <davidcalle> didrocks, can we drop/ignore unity-scope-evolution for now, to avoid blocking the stack?
[08:43] <didrocks> davidcalle: I think it's better if Laney can't get it
[08:45] <davidcalle> didrocks, ok (cf. discussion with Laney in #ubuntu-desktop)
[08:48] <Mirv> sil2100: you're welcome.
[08:51] <Mirv> didrocks: https://code.launchpad.net/~timo-jyrinki/indicator-datetime/mark_as_released/+merge/167482
[08:51] <didrocks> Mirv: interesting, ok, approving, thanks!
[08:52] <Saviq> tsdgeos, hum, question - I'm still seeing the  "content goes behind section header" issue on the phone - did we not distro-patch it?
[08:52] <tsdgeos> Saviq: think not
[08:53]  * tsdgeos checks for the bug
[08:53] <tsdgeos> Saviq: nope https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1183350
[08:53] <tsdgeos> or yes? which qt is in the device?
[08:54] <Saviq> tsdgeos, it only went into saucy Qt
[08:54] <Saviq> tsdgeos, that's fine, then, we'll get it soon enough
[08:54] <tsdgeos> oka
[08:54] <Saviq> tsdgeos, and then you're rewriting the thing anyway :)
[08:54] <tsdgeos> right
[08:54] <tsdgeos> still no section support
[08:54] <tsdgeos> getting there
[08:57] <Saviq> tsdgeos, cool
[09:05] <Saviq> didrocks, hey, can you please explain one thing about PPAs for me? (how) is it possible to have packages with the same version in the same PPA, for different series?
[09:05] <Saviq> didrocks, in https://launchpad.net/~phablet-team/+archive/ppa/+packages sergiusens somehow managed to just copy some sources from raring to saucy
[09:06] <Saviq> didrocks, but if I try that, I get a "same version already has published binaries..."
[09:07] <didrocks> Saviq: a binary copy works
[09:07] <didrocks> Saviq: not a source upload
[09:07] <didrocks> (or a rebuild)
[09:08] <Saviq> didrocks, ah, but that's not really safe is it?
[09:08] <Saviq> copying binaries between series
[09:08] <didrocks> Saviq: not really, because you can have difference due to toolchain
[09:08] <Saviq> didrocks, ok thanks
[09:08] <didrocks> and as we see, unity tests are failing on saucy for example (segfault)
[09:08] <didrocks> Saviq: yw :)
[09:16] <didrocks> davidcalle: so, conclusion is to remove the evolution scope?
[09:18] <mhr3_> didrocks, sorry was in a meeting, nick is looking at it
[09:20] <didrocks> mhr3_: pstolowski: mind remove the evolution scope? removing from the .json the evolution scope, we'll remove it from daily as well (also bumping libunity and unity build-deps to take it)
[09:20] <didrocks> mhr3_: pstolowski: evolution doesn't have anymore introspection data
[09:20] <davidcalle> didrocks, I guess, yes. That will also mean a quick modification to unity-scope-home, maybe : pstolowski does a master hide from filters if it doesn't have any scopes?
[09:22] <didrocks> sil2100: dednick: did you success in reproducing the issue?
[09:23] <dednick> didrocks: just finished upgrading. building unity now
[09:24] <didrocks> veebers: you asked me to ping you, seems the None.ogv is still an issue :/
[09:26] <pstolowski> davidcalle: yes, it won't show up
[09:26] <pstolowski> didrocks: ok, I'll do the change in libunity
[09:27] <didrocks> pstolowski: and unity, you need to bump the build-dep
[09:27] <didrocks> thanks!
[09:28] <didrocks> veebers: but before that, 3 tests failures on the QA stack
[09:29] <didrocks> which is below the threshold, but better to have them fixed one day :)
[09:30] <Saviq> mzanetti, ping
[09:30] <mzanetti> hey Saviq
[09:30] <Saviq> mzanetti, so how do we now make sure that there's multiple users in the tablet?
[09:31] <mzanetti> Saviq: do we need to?
[09:31] <mzanetti> Saviq: I mean... they don't do anything anyways
[09:31] <Saviq> mzanetti, but the greeter doesn't look good with all the empty space ;)
[09:31] <mzanetti> Saviq: and if someone wants to test the list any everything he can run it with ./run -f
[09:32] <mzanetti> Saviq: well, thing is, there is no such thing as a tablet or a phone ;)
[09:32] <mzanetti> Saviq: and as we now determine the amount of users through the LightDM api and not the screen size any more...
[09:32] <dednick> didrocks: which ppa is unity this building against?
[09:32] <dednick> *this unity
[09:32] <Saviq> mzanetti, yeah, that's fine
[09:33] <Saviq> mzanetti, so how do we then make sure that there's multiple users on a tablet? :P
[09:33] <didrocks> dednick: the daily-build one: https://launchpad.net/~ubuntu-unity/+archive/daily-build
[09:33] <Saviq> mzanetti, I'm just not sure people demoing are gonna be happy
[09:34] <mzanetti> Saviq: hmm... we would need to install another mock lightdm library
[09:34] <Saviq> mzanetti, but I do get the conflict - and thanks for raising the question with Katie
[09:34] <mzanetti> np :)
[09:35] <mzanetti> its kinda my job, isn't it
[09:35] <mzanetti> Saviq: anyways... so, we would need to replace the mock lib. would packaging them up and making them installable be an option?
[09:35] <Saviq> mzanetti, we already have the fake env package
[09:36] <mzanetti> Saviq: so if you want to have multiuser you do a apt-get install lightdm-mock-multiuser
[09:36] <Saviq> mzanetti, so making two of them could make sense
[09:36] <mzanetti> Saviq: yeah, but the default one is a single user one (which we decided to to because that's what we will focus on in the near future
[09:36] <Saviq> mzanetti, yeah, that's fine
[09:37] <mzanetti> Saviq: ok, I'll talk with mterry when he comes on. He's the lightdm-mock-master
[09:38] <Saviq> mzanetti, yeah, I think, though, that we should install both at the same time (actually I think that's the case already)
[09:38] <Saviq> mzanetti, and choose one or the other based on FORM_FACTOR for the time being
[09:38] <mzanetti> Saviq: you mean in /etc/phone-services? ... wait... :P
[09:39] <mzanetti> Saviq: just joking... yeah.. we'll figure something. lets have a chat later when mterry is here
[09:39] <didrocks> sil2100: do you have the build issue as well?
[09:39] <sil2100> didrocks: still upgrading ;/
[09:39] <Saviq> mzanetti, thanks
[09:39] <sil2100> didrocks: will know in some minutes
[09:39] <didrocks> sil2100: you were not on saucy? :/
[09:39] <didrocks> ok
[09:40] <Saviq> mzanetti, I also noticed one thing in CrossFadeImage after the recent changes
[09:40] <mzanetti> Saviq: that is?
[09:40] <Saviq> mzanetti, when you switch the images many times in a short period of time (just tap on different people in the greeter on the tablet)
[09:40] <Saviq> mzanetti, it fades to black for a second or so
[09:41] <Saviq> s/fades/drops/
[09:41] <mzanetti> Saviq: hmm, ok... I'll have a look
[09:43] <Saviq> mzanetti, I think what happens is it unloads the faded-out image before the new one was loaded / faded in
[09:43] <Saviq> mzanetti, but that's minor, don't focus on it now
[09:43] <duflu> That's interesting. I'm getting tearing on my 1920x1200 desktop since upgrading it to raring. Should be impossible if Intel is implementing buffer swapping by page flipping... right?
[09:45] <duflu> Oh, I see the problem. Intel changed their defaults. Grrr.... (**) intel(0): Wait on SwapBuffers? disabled
[09:46] <Saviq> duflu, raring!? ;)
[09:47] <duflu> Saviq: Yes, Intel has disabled it by default on raring. I wonder why... since this basically negates all the work to avoid tearing on Ubuntu
[09:48] <Saviq> duflu, buut, did you just upgrade to raring?
[09:48] <Saviq> duflu, we are all upgrading to saucy now ;)
[09:48] <duflu> Saviq: Yes. Raring came out as I left the country. And I just got home
[09:49] <pstolowski> sil2100, didrocks: https://code.launchpad.net/~stolowski/libunity/disable-some-scopes/+merge/167490 I'm a bit unsure about version bump, but it should be fine once I update unity to require libunity 7.0.1 instead of 7.0.0?
[09:49] <duflu> Raring/Saucy is not the point. I know you're being facetious. But I'm concerned about visible regressions on the desktop
[09:49] <Saviq> duflu, yeah I understand
[09:50] <didrocks> pstolowski: no, it need an upstream version bump, as we already had one build in the ppa
[09:50] <didrocks> pstolowski: otherwise, unity won't wait for the latest libunity to be there
[09:50] <pstolowski> didrocks: ok
[09:50] <didrocks> (we already have a 7.0.1daily… in the ppa from tonight daily build)
[09:50] <didrocks> pstolowski: making sense? ^
[09:50] <pstolowski> didrocks: yeah
[09:50] <duflu> Oh, wait. Maybe it's just a problem introduced by the Mir PPA :)
[09:51] <Saviq> mzanetti, hum, current trunk - I'm dragging the launcher from the edge past the middle of the screen, it shows fully
[09:52] <Saviq> mzanetti, I release my finger, it snaps back out?
[09:52]  * mzanetti tries
[09:53] <Saviq> mzanetti, also, the darkening of the background happened as-you-dragged-the-launcher-out before
[09:53] <mzanetti> Saviq: yeah... that with the darkening I noticed too. will fix soon
[09:53] <veebers> sil2100: I am in passing, what's the haps?
[09:54] <pstolowski> didrocks: does it need a new chanelog entry, or it's ok if I update existing one (it still says UNRELEASED)
[09:54] <veebers> didrocks: ack, I'll hit that tomorrow. Also there was some confusion earlier today in ps-qa regarding a potential autopilot issue that wasn't an issue?
[09:54] <mzanetti> Saviq: the other thing: not sure about that... because if you swipe it past the middle of the screen its not sure if you really want to reveal the launcher
[09:54] <mzanetti> Saviq: in that case the user rather tried to swipe away the content
[09:55] <mzanetti> Saviq: can ask katie what she things
[09:55] <mzanetti> thinks
[09:55] <didrocks> pstolowski: as long as it's UNRELEASED, you can update the existing one :)
[09:55] <Saviq> mzanetti, yes please, at least on the greeter it feels weird
[09:55] <sil2100> veebers: I think my issue is resolved now, but see didrocks ping ^
[09:55] <Saviq> mzanetti, and probably in dash, too, as nothing else happens
[09:55] <veebers> sil2100: aye, thanks.
[09:55] <didrocks> veebers: ah, not sure about that one ;)
[09:55] <didrocks> veebers: we fixed xpathselect FYI
[09:55] <didrocks> if that's what you are talking about
[09:55] <veebers> didrocks: oh, I wan't aware there was an issue :-P What was the problem?
[09:56] <mzanetti> Saviq: apart from that. I think it feels waaaay better now than before. what do you think?
[09:56] <Saviq> mzanetti, yeah, it's good
[09:56] <didrocks> veebers: new toolchain: https://code.launchpad.net/~timo-jyrinki/xpathselect/ftbfs_missing_include/+merge/167471
[09:57] <didrocks> veebers: it was failing to build
[09:57] <veebers> did ah I see
[09:57] <Saviq> mzanetti, there's many usability things that improved
[09:57] <Saviq> mzanetti, like the fact that it actually sticks to your finger, and that you can reverse the long-swipe
[09:57] <didrocks> veebers: I took the opportunity to approve as we are in a rush and want to deliver (also, it's a toolchain simple issue, didn't affect upstream code logic)
[09:57] <didrocks> as for a packaging change IMHO :)
[09:57] <mzanetti> Saviq: yeah... I hated that one with the old one :D
[09:57] <veebers> didrocks: yeah fair enough, simple enough fix :-)
[09:57]  * Saviq had to switch to GNOME until compiz stabilizes... the top-panel+title-bar+menu-bar{+tab-bar} combo is just atrocious
[09:57] <didrocks> yep ;)
[09:58] <mzanetti> oh right... should put some sauce on my notebook too...
[09:58] <Saviq> I thank sabdfl for forcing menus-in-panel on us
[09:58] <veebers> didrocks: right, off for the night. o/
[09:59] <didrocks> veebers: ttyl!
[10:00] <Saviq> mzanetti, btw, when you'll be touching the launcher, please increase the widening angle
[10:00] <mzanetti> Saviq: even more?
[10:00] <Saviq> mzanetti, it's still 10 isn't it?
[10:00] <mzanetti> Saviq: its 30 now
[10:01] <Saviq> mzanetti, hmm
[10:01]  * mzanetti check
[10:01] <mzanetti> s
[10:01] <Saviq> mzanetti, I'm getting a lot of false negatives on manta
[10:01] <mzanetti> Saviq: yeah, 30
[10:01] <Saviq> mzanetti, ok nvm, maybe that's just my finger
[10:01] <Saviq> ;)
[10:02] <mzanetti> Saviq: no... that's actually really important information... I think its crucial to find the best values
[10:02] <Saviq> mzanetti, yeah, but now that I use my thumb for it it's 10 for 10
[10:02] <Saviq> mzanetti, let's see how it goes
[10:03] <Saviq> mzanetti, on manta, when I drag the launcher so that the apps get dragged away, but then reverse the gesture
[10:04] <Saviq> mzanetti, the apps come back really slowly
[10:04] <mzanetti> Saviq: noted
[10:04] <Saviq> mzanetti, actually same on launcher
[10:04] <Saviq> s/launcher/maguro/
[10:04] <Saviq> but more visible on manta
[10:08] <Saviq> mzanetti, can you have a feel for the widening angle for lp:~dandrader/unity/phablet_edgeDragInStage ?
[10:08] <mzanetti> Saviq: sure
[10:08] <Saviq> mzanetti, I'm inclined to say that 10 is too low
[10:08] <dandrader> Saviq, btw, is it getting merged! :)
[10:08] <dandrader> ?
[10:08] <Saviq> dandrader, yeah, I'm just doing the last round of review
[10:08] <Saviq> dandrader, sorry it took so long
[10:09] <dandrader> Saviq, np, I'm aware that this is not the only merge proposal around
[10:09] <mzanetti> Saviq: btw: Pat's feedback was: everything less than 15 is totally unusable, 20 is what he really recommends as minimum. If it doesn't interfere too much with the rest, probably even 30 would be good
[10:09] <mzanetti> dandrader: ^
[10:11] <dandrader> Saviq, mzanetti ok, I'll change it to 20 now (for the Stage m.p.), no problem.
[10:12] <Saviq> dandrader, thanks
[10:13] <dandrader> done
[10:13] <mzanetti> yes... I'd say too... with 10 I fail to switch apps 3 out of 10 times - which is too much :D
[10:13] <Saviq> mzanetti, when talking to Katie, please also check whether the launcher-long-swipe doesn't begin too quickly
[10:14] <Saviq> mzanetti, I'd think it should maybe only start after you crossed 2*launcher.width?
[10:14] <Saviq> mzanetti, as now it kicks in when I just try and swipe the launcher in
[10:14] <mzanetti> Saviq: hmm.. was thinking about that too quite a while...
[10:15] <Saviq> mzanetti, aand, does the launcher have a behavior on its x? should be disabled when DDA is dragging
[10:15] <mzanetti> Saviq: I personally think panel.width * 2 is too much
[10:15] <mzanetti> Saviq: it is disabled while dragging
[10:15] <Saviq> mzanetti, ok, so it's just manta's tragic touch input
[10:15] <Saviq> mzanetti, sure, that could be too much
[10:16] <mzanetti> Saviq: actually had to add a hack I really hated because of that
[10:16] <Saviq> mzanetti, ;)
[10:16] <mzanetti> but seems to work perfectly fine and its small and documented, so I think we're ok
[10:16] <greyback> bloody hell saucy compiz is unstable
[10:16] <Saviq> greyback, +1
[10:16] <Saviq> greyback, I switched to GNOME
[10:16] <Saviq> greyback, and am missing Unity a _lot_
[10:16] <Saviq> like 1/5th of my screen is black at the top!
[10:16] <didrocks> pstolowski: ping me as well once you have the unity branch
[10:17] <greyback> Saviq: heh, I've not used gnome in a while now. gnome-classic?
[10:17] <Saviq> greyback, nah, -shell
[10:17] <Saviq> greyback, top-panel+title-bar+menu-bar{+tab-bar}
[10:17] <greyback> Saviq: yikes
[10:18] <mzanetti> hehe
[10:18] <Saviq> greyback, no kidding, like 1/6th of my screen with maximized Thunderbird is... black
[10:18] <greyback> Saviq: that can't be right
[10:19] <greyback> some configuration weirdness surely
[10:19] <dandrader> speaking of missing unity, have you guys noticed google docs have implemented a HUD?
[10:20] <mzanetti> dandrader: can't find it
[10:21] <dandrader> mzanetti, hide the menus (right corner icon)
[10:22] <dandrader> mzanetti, ctrl+shift+f
[10:22] <dandrader> mzanetti, then their HUD appears on the left corner of the top bar
[10:23] <Saviq> greyback, http://ubuntuone.com/3q763qrIyXlSS5Wc7isLnK
[10:23] <mzanetti> hehe, right
[10:24] <greyback> Saviq: yep, that's a lot of bars.
[10:25] <greyback> would look ok if at least the application titlebar hid while maximized
[10:25] <dandrader> mzanetti, have you found it? http://ubuntuone.com/02Ii27eRUIzeOSIrIdRJ5o
[10:25] <Saviq> greyback, yeah, but for maximized apps global menu bar is just awesome
[10:26] <greyback> Saviq: as long as you know it's there, yes
[10:26] <Saviq> greyback, OTOH I love the telepathy integration
[10:26] <pstolowski> didrocks, sil2100: https://code.launchpad.net/~stolowski/unity/bump-libunity/+merge/167497
[10:27] <Saviq> greyback, and I don't think I like "cross-workspace switcher"
[10:27] <didrocks> pstolowski: great, I'm waiting on libunity to be merged before because I think the upstream merger doesn't handle build-deps
[10:27] <sil2100> pstolowski: looking good, not sure if the ~ is required there
[10:27] <Saviq> although less than webapps who switch tabs in my browser
[10:27] <didrocks> sil2100: not really if we don't backport, not a biggie though
[10:27] <sil2100> didrocks: true true
[10:28] <mzanetti> dandrader: yeah. thanks
[10:30] <dednick> didrocks: sil2100: confirmed crash in TestGLibObject.AssignmentOperators
[10:31] <didrocks> dednick: ah, "nice" :)
[10:32] <sil2100> \o/
[10:32] <sil2100> dednick: I'm in the middle of building unity right now
[10:41] <dandrader> greyback, , when we have unity running with mir, what we have is a unity shell process with the whole mir loaded as a library, right?
[10:42] <Saviq> dandrader, yes
[10:42] <greyback> dandrader: yep.
[10:42] <Saviq> mzanetti, btw, it's impossible to do the long-swipe-to-dash on manta with just a thumb, please raise that with Katie, too
[10:42] <mzanetti> Saviq: ack
[10:43] <mzanetti> Saviq: actually I think vesar is now the Launcher designer
[10:43] <mzanetti> anyways, yes, I'll do
[10:43] <dandrader> greyback, I got it "working" (d-bus communications seems missing, so nothing coming from indicators or lenses/scopes). and rendering seems ok. but it looks like animation timers are just slower (as in slow motion, not slow rendering)
[10:44] <dandrader> greyback, do you get the same?
[10:44] <greyback> dandrader: yep, that's the same for me
[10:44] <greyback> dandrader: animations are slow due to apparantly slow buffer swaps, it's not Qt's fault
[10:45] <dandrader> greyback, but it's quite responsive though. if you open two apps (fake apps as the fake ubuntu.application component is the one that ends up loaded) and play with the right-edge animation
[10:46] <dandrader> it follows your finger quite nicely
[10:46] <sil2100> dednick, didrocks: same here, segfault in TestGLibObject.AssignmentOperators
[10:46] <greyback> dandrader: yeah, it's not bad at all. Once Mir gets a frame swapping algorithm that suits the Galaxy Nexus better, it'll be buttery smooth. I hear it's nice on the Nexus4
[10:47] <dednick> sil2100: didrocks: it's making the assumption that G_IS_OBJECT returns false for a deleted pointer.
[10:47] <dednick> but it's segfaulting because the mem is invalid i guess. don't know why it worked previously
[10:48] <didrocks> weird
[10:48] <sil2100> dednick: strange, maybe some quirk of the previous toolchain
[10:53] <dednick> sil2100: probably something like that. give me a few minutes. I'm fixing the test to use a weak ref to test for destruction of the gobject pointer
[11:10] <Saviq> Cimi, ping
[11:11] <Cimi> Saviq, pong
[11:11] <Saviq> Cimi, hey, what's the status of https://code.launchpad.net/~unity-team/unity/phablet.carousel-listview/+merge/165081 ?
[11:11] <Cimi> Saviq, I'm unsure on what to test actually
[11:12] <dednick> sil2100: didrocks: https://code.launchpad.net/~nick-dedekind/unity/TestGLibObject.use-weak-ref/+merge/167503
[11:12] <didrocks> sil2100: as you have the build env ready, mind reviewing and approving?
[11:12] <didrocks> you rock dednick :)
[11:13] <Saviq> Cimi, we have the functions in there tested
[11:13] <Cimi> yes
[11:14] <Saviq> Cimi, other than that it's really just a ListView, no?
[11:14] <Cimi> yep, more or elss
[11:14] <Cimi> *less
[11:14] <Saviq> Cimi, so there's no real point in testing the interaction
[11:14] <Saviq> Cimi, except maybe for trying to click on stuff and check that the right things happen
[11:14] <Saviq> Cimi, i.e. the correct clicked() signal is emitted
[11:15] <Cimi> which is not trivial :D you also need a model
[11:15] <sil2100> didrocks, dednick: reviewing!
[11:17] <Saviq> Cimi, well, a model isn't really an issue
[11:17] <Cimi> Saviq, I said 'trivial'
[11:18] <Saviq> Cimi, you said "not trivial" ;)
[11:18] <Cimi> yeah
[11:18] <Cimi> trivial = quck
[11:18] <Cimi> not easy
[11:18] <Cimi> unless my english is broken, and can be :D
[11:18] <Saviq> Cimi, trivial is easy
[11:18] <Cimi> takes a little bit of time but it's easy
[11:19] <Saviq> Cimi, ok, let's not do that :D
[11:19] <Saviq> Cimi, anyway, that's the only thing I can think of there
[11:19] <Saviq> Cimi, a purely functional test
[11:20] <Saviq> Cimi, i.e. tap, check; drag; tap; check; swipe; tap; check
[11:20] <Saviq> Cimi, but the drag and swipe would really be tests for the ListView
[11:20] <Cimi> currently getting mad with calendar tests though :D
[11:20] <mzanetti> Saviq: I'm writing tests for the LauncherModelInterface... I'm thinking, if the plugin implements the interface in unity-apis, does it make sense to write tests that check if all the methods are there?
[11:21] <Saviq> mzanetti, I say yes, as people might not use our headers for whatever reason
[11:21] <mzanetti> Saviq: oh...
[11:21] <Saviq> mzanetti, but if they expose the same API, that should still work
[11:21] <mzanetti> in that case, yes... but I wouldn't see any reason not to use that
[11:22] <Saviq> mzanetti, you wouldn't, I wouldn't ;)
[11:22] <mzanetti> lol
[11:22] <mzanetti> ok..
[11:22] <Saviq> mzanetti, but that's really just to verify  our headers are correct, too
[11:22] <mzanetti> ack
[11:23] <Saviq> Cimi, k, let's just not forget about the carousel :)
[11:24] <Cimi> :-)
[11:25] <Saviq> mzanetti, "Implement rotation unlock method" that shouldn't be in June milestone, should it?
[11:27] <mzanetti> Saviq: dunno... that was moved around by mterry and katie. Anyways, my prototype is implemented, if design comes to a conclusion if we really need that and how it should look like, it shouldn't be a problem to finish that in June still
[11:27] <Saviq> mzanetti, k
[11:27] <sil2100> dednick: approved
[11:27] <sil2100> oh, Trevinho_ also made a review
[11:28] <dednick> sil2100: \o/ thanks
[11:32] <ritz_> Hi, quick question. If I were to fix https://bugs.launchpad.net/unity/+bug/760785 , what is the way I would do this
[11:32] <ritz_> add dconf-key for this
[11:32] <ritz_> which unity-application-lens can read of , and add to filter
[11:33] <ritz_> or create a new lens, unity-application-domain , which addes a custom page
[11:33] <ritz_> or do I talk to design team about this ?
[11:34] <ritz_> didrocks ^^^
[11:36] <Saviq> mzanetti, is lp:~unity-team/unity/phablet-pinlock WIP?
[11:36] <mzanetti> Saviq: no... waiting for review
[11:37] <Saviq> mzanetti, there's tests failing and such
[11:37] <Saviq> mzanetti, as in whitespace tests at least
[11:37] <Saviq> mzanetti, and there's no commit message
[11:43] <mzanetti> multiple new lines at end of file... seriously?
[11:43] <mzanetti> :P
[11:44] <dandrader> greyback, do you mind if update lp:~unity-team/unity/phablet-integrate-mir to latest lp:unity/phablet?
[11:44] <mzanetti> but we allow comitting files without newline at end of file :D
[11:44] <mzanetti> Saviq: fixed both
[11:44] <greyback> dandrader: go ahead
[11:44] <Saviq> mzanetti, indeed, we should probably tweak the whitespace test to only allow a single newline at end of file :)
[11:45] <greyback> dandrader: and if you made any changes to the platform-api or qtubuntu branches, let's put them up somewhere.
[11:45] <mzanetti> Saviq: >0 imho
[11:45] <Saviq> mzanetti, ==1 :P
[11:45] <greyback> dandrader: lp:~unity-team/platform-api/mir-support for platform api anyway, no branch up yet for qtubuntu so feel free
[11:46] <Saviq> mzanetti, otherwise someone somewhen will just go through the files and check that and fix it, we don't need that if we just do the right way straight away
[11:46] <dandrader> greyback,  I didn't make any changes to platform-api or qtubuntu, just applied your patches on top of rcarr branches
[11:46] <greyback> dandrader: ok cool
[11:46] <dandrader> back in a bit
[11:46] <greyback> dandrader: I'll clean up those changes a bit later on today hopefully
[11:46] <Saviq> mzanetti, there's an issue with the keypad entry - looks like the star key has both the star and the arrow?
[11:46] <greyback> enjoy food!
[11:47] <mzanetti> Saviq: star key?
[11:47] <Saviq> mzanetti, or something, the lower left key has the back arrow
[11:47] <Saviq> mzanetti, but it looks wrong somehow
[11:47]  * mzanetti checks
[11:48] <mzanetti> Saviq: looks good here...
[11:48] <mzanetti> Saviq: http://wstaw.org/m/2013/06/05/plasma-desktopIo8216.png
[11:48] <Saviq> and the lower right button is supposed to be empty?
[11:49] <mzanetti> Saviq: ah... install "ubuntu-mobile-icons"
[11:49] <Saviq> mzanetti, right
[11:49] <sil2100> pstolowski: uh, the unity merge is failing now due to some unity errors (WTF?)
[11:49] <mzanetti> Saviq: there are 2 "ubuntu-mobile" and "ubuntu-mobile-icons"... for some reason we still pull the wrong one
[11:49] <sil2100> Ah
[11:49] <pstolowski> sil2100: grr
[11:49] <sil2100> I know now
[11:50] <sil2100> pstolowski: let's wait for dednick's fix to get in
[11:50] <sil2100> pstolowski: although I'm still worried about arm, since it's failing for a different readon
[11:50] <sil2100> *reason
[11:50] <Saviq> mzanetti, ah, needs fixin', then
[11:51] <mzanetti> Saviq: ?
[11:51] <Saviq> mzanetti, nvm, just meant "we need to fix that"
[11:51] <Saviq> mzanetti, also, do you think we could make some changes to ./run to allow for testing the different unlock methods?
[11:51] <mzanetti> Saviq: yeah... I think Kaleo has been talking to sergiusens already about it
[11:52] <Saviq> mzanetti, ah, so it's not really us that need to fix ;)
[11:52] <mzanetti> Saviq: that's there... ./run -p and ./run -k
[11:52] <Saviq> mzanetti, indeed!
[11:52] <mzanetti> Saviq: from what I understood the SDK should depend on the right icon theme
[11:52] <Saviq> mzanetti, sorry for the noise
[11:52] <mzanetti> Saviq: no prob
[11:52] <mzanetti> Kaleo: any news about that?
[11:52] <sil2100> dednick: I'm afraid there might be some complications with getting your fix into lp:unity
[11:53] <sil2100> dednick: armhf seems to have some issues with MockWindowManager.h
[11:53] <mzanetti> Kaleo: we are about to merge stuff that would require ubuntu-mobile-icons but seems we (as in you :P) still pull the wrong one
[11:53] <sil2100> dednick: http://s-jenkins:8080/job/unity-saucy-armhf-ci/5/console <- this is from the CI on your branch (and not only, I got the same thing on pstolowski's branch's CI)
[11:53] <Saviq> mzanetti, btw, I'd just go for "./run_on_device -- -p/-k"
[11:54] <Saviq> mzanetti, i.e. pass everything past -- to the ./run script
[11:54] <mzanetti> Saviq: no... everything after -- goes to the shell binary
[11:54] <Saviq> does it already?
[11:54] <mzanetti> Saviq: yes
[11:54] <Saviq> mzanetti, for ./run, yes, but not for ./run_on_device
[11:54] <Saviq> ?
[11:54] <mzanetti> Saviq: hmm.. .not entirely sure right now
[11:55] <mzanetti> Saviq: however, I would keep it consistent and make -- also for _on_device pass it on to the app itself
[11:55] <Saviq> mzanetti, regardless, please update the usage in ./run_on_device, too
[11:55] <Saviq> mzanetti, yeah, that's fine
[11:55] <Saviq> mzanetti, or we could go ./run_on_device --args -- --run_args -- --shell_args :D
[11:56] <mzanetti> Saviq: btw... exactly like this I think Pete and Nic should add their fully fledged infographics backend loading
[11:56] <Saviq> mzanetti, and sorry for distracting you, I'm gonna stop now :)
[11:57] <Saviq> mzanetti, other than --full?
[11:57] <mardy> Mirv: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1187746
[11:58] <mzanetti> Saviq: dunno... exactly... thats where I don't exactly know what mterry needs and what the others need
[11:58] <mzanetti> Saviq: done (and dont worry... I'm happy you reviewed it)
[11:59] <sil2100> dednick: it's an ARM-specific issue
[12:03] <sil2100> dednick: I can fix that in the CMakeFile (at least workaround it)
[12:05] <Saviq> mzanetti, getopt needs p and k in "sgh" in diff line 720
[12:05] <Saviq> mzanetti, and in 639, too
[12:06] <Mirv> mardy: thanks
[12:07] <Saviq> mzanetti, also, 473	+import QtGraphicalEffects 1.0 sounds unnecessary/
[12:07] <Saviq> ?
[12:08] <mzanetti> Saviq: ah right... there was the Blur effect before
[12:09] <Saviq> mzanetti, why you didn't use a Button for the PinPadButtons?
[12:09] <mzanetti> Saviq: because making a button look like a transparent ubuntushape is more work than using a transparent ubuntushape :D
[12:10] <Saviq> mzanetti, orly? :)
[12:10] <Saviq> mzanetti, feels like it should be reported to the UI toolkit
[12:11] <Saviq> mzanetti, also it's possible that this will be better when we start theming, can you please add a TODO somewhere there
[12:12] <Saviq> mzanetti, and it does feel like the wrongPasswordAnimation could be abstracted? it's used in three places already, right?
[12:13] <mzanetti> Saviq: yeah... true
[12:21] <kgunn> dednick: ping
[12:27] <Kaleo> mzanetti: hang on, meeting
[12:27] <mzanetti> Saviq: done, except the TODO. I really don't think it makes sense here to use a Button... As it should look like a ubuntu shape, and not like a button as per design
[12:27] <Saviq> mzanetti, IMO it is just a differently-themed button, but ok
[12:28] <Saviq> mzanetti, some more comments coming on the MR, IRC is too distracting for it (didn't plan a full review :P)
[12:28] <mzanetti> hehe
[12:30] <mzanetti> Saviq: as you've changed the community-created infographics research to INPROGRESS: I'd like to be able to integrate fitbit stats in there at some point ;)
[12:31] <Saviq> mzanetti, that task is really just about the visualization, not data sourcing
[12:31] <mzanetti> ah ok
[12:31] <Saviq> mzanetti, data sourcing will remain what we have now
[12:36] <didrocks> ritz_: I think you should first talk to pstolowski and mhr3_ :)
[12:36] <sil2100> dednick, didrocks: https://code.launchpad.net/~sil2100/unity/fix_ftbfs_arm_unused_typedefs/+merge/167525
[12:36] <sil2100> dednick, didrocks: this fix is also needed in lp:unity to unblock ARM builds (most probably)
[12:37] <sil2100> dednick, didrocks: the problem is... not sure if we can get it merged, as it probably needs dednick's fixes as well, since otherwise it will fail
[12:37] <ritz_> didrocks, thanks. will do
[12:37] <didrocks> sil2100: can you take it into your branch?
[12:37] <sil2100> dednick, didrocks: it might be that both fixes need to go in at the same time
[12:37] <didrocks> oupss dednick ^
[12:39] <ritz_> mhr3_ pstolowski wrt  https://bugs.launchpad.net/unity/+bug/760785 , How do I fix this ? add dconf-key for this which unity-application-lens can read of , and add to filter or create a new lens. Alternate, unity-application-domain , which addes a custom page based on dconf/settings. Or do I talk to design team about this ?
[12:39] <sil2100> dednick: I'm waiting for CI to spin on my branch to check all is ok, once it does that, would be good if you could for instance pull in this fix to your branch
[12:40] <didrocks> sil2100: your branch is based on his one?
[12:40] <didrocks> otherwise, we'll maybe have the segfault still, isn't it?
[12:40] <didrocks> or is it failing during build? (as public jenkins is failing…)
[12:42] <pstolowski> ritz_: hi
[12:42] <ritz_> pstolowski hi
[12:42] <pstolowski> ritz_: yeah, categories are hardcoded in applications lens
[12:43] <ritz_> they indeed are
[12:43] <pstolowski> ritz_: do you know if the "new" categories also exist in xapian index?
[12:44] <sil2100> didrocks: my branch is based on trunk
[12:44] <ritz_> pstolowski hmm, they would not
[12:44] <sil2100> didrocks: yes, it does have that, that's what I meant
[12:44] <ritz_> more along the lines of ubuntu-application-domain-lens
[12:44] <sil2100> didrocks: I can merge in dednick's fix in if needed, I hoped it to be done the other way around
[12:45] <sil2100> didrocks: but CI at least will tell me if ARM fails to compile or segfaults
[12:45] <didrocks> sil2100: I think we can't afford waiting for too long. If bregma agrees, we can as well bypass the merger as it's blocking everything for daily releasing
[12:45] <sil2100> If it's the second one, then I know the fix is correct
[12:45] <didrocks> (once we'll get the CI result for your branch)
[12:45] <sil2100> didrocks: we can do it like that - once we have CI results, I pull in dednick's branch and we merge
[12:46] <sil2100> Then pstolowski's branch will also go in
[12:46] <didrocks> yep :)
[12:46] <didrocks> I think we should definitively merge that manually
[12:46] <didrocks> as we're going to rebuild it in daily anyway
[12:46] <pstolowski> ritz_: in theory we could add missing categories in the app lens code. but this only makes sense if it fixes the problem completly, e.g. if the number of categories if not high and we can add them all.  also, we need to be able to turn selected category filter into xapian query
[12:47] <ritz_> pstolowski not sure about xapian index . but the issue I working on is more along the lines for custom deployment . To enabled kiosk/corporate users to see their apps easily
[12:48] <pstolowski> ritz_: ah, now I see where you're coming from with dconf
[12:49] <ritz_> okay, xapian is a search toolkit
[12:49] <pstolowski> ritz_: if it's not in xapian db, then app lens will not find an app unless it's installed already
[12:50] <ritz_> pstolowski yup, finding installed app is easy. but having it displayed on the dash makes it easier for the user
[12:51] <ritz_> especially, if they can see their "logo" along with other pages in dash
[12:52] <ritz_> using dconf key to add category would also be a solution
[12:52] <pstolowski> ritz_: so you're saying it's ok if this custom filter works for installed apps only?
[12:53] <ritz_> okay, http://www.enricozini.org/2007/debtags/apt-xapian-index/
[12:53] <ritz_> pstolowski this would seem fine to me
[12:54] <ritz_> would allow user to add custom filter such as "wine" or "mydomain"
[12:57] <pstolowski> ritz_: yes, it's doable, dconf or a flat file would do. but since it would work for installed apps only (and as such break existing UX), I think you would need an ack from design. but this shouldn't be a problem since it's for a limited use case
[12:58] <pstolowski> ritz_: that's my opinion at least ;)
[12:58] <sil2100> bregma: thanks for the review! Still waiting on CI
[13:01] <didrocks> sil2100: I've prepared the manual merge, just waiting on CI as well :)
[13:04] <sil2100> didrocks: with both branches ;) ?
[13:04] <sil2100> \o/
[13:04] <sil2100> I'm refreshing every moment
[13:04] <didrocks> sil2100: the 3 of them! :)
[13:04] <sil2100> Ah, Paweł's as well!
[13:04] <didrocks> yep :)
[13:04] <didrocks> then, relaunch a libunity + unity rebuild
[13:05] <didrocks> ah, let's do the libunity rebuild right now in the ppa, we'll buy some time then :)
[13:06] <sil2100> Indeed! How will you push the new libunity to the PPA? Just run the stack with just libunity ?
[13:12] <ritz_> pstolowski hmm, thanks . Do I go ahead and add design team to this ?
[13:18] <sil2100> grrrr, CO
[13:18] <sil2100> *CI
[13:19] <sil2100> Still waiting
[13:19] <mhr3_> ritz_, iirc people used to fork the apps lens to do this (in corporate environments), surely a generic solution where you could just change the config easily would be nice... but it might not be trivial
[13:27] <sil2100> didrocks: ok, it takes really long ;p I need to go for some lunch now
[13:28] <didrocks> sil2100: ok
[13:28] <didrocks> sil2100: I propose to run and moving on, wdyt?
[13:28] <didrocks> merging that
[13:32] <sil2100> didrocks: ok, let's do that then
[13:32] <sil2100> It shouldn't break anything anyway
[13:32] <sil2100> didrocks: thanks!
[13:33] <didrocks> yw :)
[13:34] <rsalveti> didrocks: hey!
[13:34] <rsalveti> didrocks: where do we stand with the saucy transition?
[13:35] <rsalveti> I'll be working on the telepathy components now, so let me know if there is anything blocking you
[13:35] <rsalveti> also regarding any possible ftbfs, as that might be related with the new hybris as well
[13:37] <Saviq> dednick, can you not hear us/
[13:37] <greyback> Saviq: better skip me
[13:37] <greyback> Saviq: I can hear you
[13:37] <dednick> Saviq: can now
[13:38] <didrocks> rsalveti: we got a lot of FTBFS, they are almost all fixed now
[13:38] <didrocks> rsalveti: the remaining points is webcreds tests that are failing
[13:38] <didrocks> mardy is on it AFAIK
[13:38] <didrocks> rsalveti: the whole media stack, sil2100 already has a branch for qt-video-node
[13:38] <didrocks> rsalveti: libcolumbus as well, Mirv has a patch, we are waiting for upstream to answer
[13:38] <didrocks> meanwhile, I'm rebuilding libunity and unity
[13:39] <didrocks> it's fixing some FTBFS, disabling some scopes that don't work on saucy
[13:39] <didrocks> then, we'll finally get some tests results for unity
[13:39] <didrocks> rsalveti: so maybe on your side, the media stack is what you can work on?
[13:40] <rsalveti> didrocks: yup
[13:40] <didrocks> I disabled some indicators as well that doesn't have all the components in
[13:40] <rsalveti> it's basically what I expected to be broken somehow
[13:40] <didrocks> (from indicator-clients)
[13:40] <didrocks> ok
[13:40] <rsalveti> hm, right
[13:40] <didrocks> rsalveti: http://10.97.0.1:8080/view/cu2d/view/Head/view/Media/job/cu2d-media-head-2.1build/43/console
[13:40] <didrocks> you have a summary at the last line :)
[13:41] <didrocks> sil2100 proposed https://code.launchpad.net/~sil2100/qtvideo-node/fix_ftbfs_with_new_libhybris/+merge/167509
[13:41] <rsalveti> cool
[13:41] <rsalveti> I'll create a few pkg-config files for the new hybris as well
[13:41] <rsalveti> hardcoded library sucks
[13:42] <didrocks> agreed :)
[13:42] <didrocks> mardy: can you refresh on on where you are on the webcreds tests issues on saucy?
[13:42] <didrocks> (as the apps and hud are dep on it, I'm more afraid on that)
[13:43] <mardy> didrocks: I *think* I fixed them today
[13:44] <didrocks> mardy: are they merged in trunk?
[13:44] <didrocks> mardy: I can relaunch the stack
[13:45] <mardy> didrocks: not yet
[13:45] <didrocks> fginther: hey! can you speed up mardy's branch landing in trunk? this is blocking landing into saucy everything :)
[13:45] <didrocks> mmrazik: ^
[13:47] <mmrazik> didrocks: which branch?
[13:47]  * mmrazik is trying to find it in the logs
[13:48] <didrocks> mardy: ? ^
[13:48] <pstolowski> ritz_: sorry, I was otp. yeah, checking with design won't hurt
[13:50] <mardy> mmrazik: https://code.launchpad.net/~mardy/libaccounts-glib/packaging/+merge/166800
[13:50] <mardy> mmrazik: actually it's still failing, but I always get 404 when i try to see the logs
[13:50] <mmrazik> mardy: publishing is broken
[13:50] <mmrazik> let me give you direct link
[13:51] <mmrazik> mardy: configure.ac:14: option `serial-tests' not recognized
[13:51] <rsalveti> didrocks: did we land anything already? saw we don't yet have platform-api in the archive
[13:52] <mardy> mmrazik: weird, works fine here. Ok, I'll do things differently
[13:53] <didrocks> rsalveti: no, I blocked everything to manual publishing
[13:53] <rsalveti> didrocks: got it, cool
[13:53] <didrocks> rsalveti: as I think we won't have all tests results before end of day, and time for NEWing and so on, I see that by the end of the day, we fix everything we have to fix
[13:54] <mardy> mmrazik, kenvandine: in raring it won't work, automake is not new enough
[13:54] <didrocks> rsalveti: and just push the publish button + NEWing + promoting to main for what we have to promote tomorrow morning
[13:54] <didrocks> (freezing the state menawhile)
[13:54] <mzanetti> mterry: did you see my email regarding the single-user, multi-user etc?
[13:54] <mardy> mmrazik, kenvandine: I'll bump the dependency, can we run the jobs in saucy, though?
[13:54] <rsalveti> didrocks: sounds fine
[13:54] <mmrazik> mardy: I don't see a reason why not. kenvandine?
[13:55] <mterry> mzanetti, ah yes.  Let me reply.  I was waiting for design to comment, but I can too
[13:55] <mmrazik> mardy: wasn't vrruiz mentioning that there were some failures in saucy?
[13:55] <kenvandine> sure
[13:55] <mardy> mmrazik: yes, this branch fixes them :-)
[13:55] <Saviq> paulliu, I just MR'd a branch that does the libbost fix...
[13:56] <Saviq> paulliu, and then some - feel free to review https://code.launchpad.net/~saviq/unity/phablet.saucy-build-scripts/+merge/167528
[13:56] <mmrazik> kenvandine, mardy: so we can move the full stack to saucy? or just this project?
[13:56] <kenvandine> we dropped the CI stuff to raring temporarily to get stuff
[13:56] <didrocks> rsalveti: if you need anything in a stack that is yellow or green to be rebuilt, tell me (as I disabled the cron job + manual publish): http://10.97.0.1:8080/view/cu2d/view/Head/
[13:56] <mardy> kenvandine: OK, then I'll bump the dependency, and you'll update the jobs?
[13:56] <kenvandine> mmrazik, i'll propose a branch
[13:56] <kenvandine> yeah
[13:56] <mmrazik> ok
[13:56] <rsalveti> didrocks: sure, thanks
[13:56] <didrocks> yw
[13:58] <mzanetti> mterry: and the -f seems to be broken. can you fix that? I think its blocking nic and pete
[13:59] <kenvandine> fginther, can you review this and then update the jenkins jobs again? https://code.launchpad.net/~ken-vandine/cupstream2distro-config/webcred_saucy/+merge/167544
[14:00] <paulliu> Saviq: ok
[14:00] <fginther> kenvandine,  looking
[14:00] <mterry> mzanetti, broken how?
[14:01] <mzanetti> mzanetti: doesn't load any users
[14:01] <kenvandine> fginther, thx... mardy has fixes for the saucy builds, but they won't work on raring now :)
[14:01] <greyback> Saviq: I can hear you
[14:01] <greyback> Saviq: oops, up arrow on wrong window
[14:01] <Saviq> greyback, I can, too
[14:01] <Saviq> greyback, you're doing "plonk"
[14:02] <mardy> kenvandine: I could make them working on raring as well, but that would require me making another upstream release, and I'd rather avoid making it today (I already made two :-) )
[14:02] <kenvandine> plonk is a fun game :)
[14:02] <Saviq> kenvandine, right!
[14:02] <kenvandine> hehe
[14:02] <Saviq> kenvandine, I was there when it was born :D
[14:02] <greyback> never heard of it :(
[14:02] <kenvandine> Saviq, cool!
[14:02] <kenvandine> it was fun to port it :)
[14:03] <kenvandine> it's now my kid's favorite game on ubuntu touch :)
[14:03] <Saviq> kenvandine, it's the first game on ubuntu touch, too :D
[14:03] <Saviq> greyback, http://thp.io/2011/plonk/
[14:03] <kenvandine> greyback, i ported it for ubuntu, it's in the collections PPA
[14:03] <mterry> mzanetti, not loading users is by design.  I wanted to keep the default fake as a single user experience
[14:04] <mterry> mzanetti, since that's what our focus is for 13.10 and that's what -f gave you by default before (until you maximized)
[14:04] <mzanetti> mterry: yeah... but -f should load all the test users, no?
[14:04] <mterry> mzanetti, why?
[14:04] <Saviq> greyback, and https://twitter.com/kenvandine/status/337656152777191424
[14:04] <mterry> mzanetti, -f means "fake" not "full"
[14:05] <mzanetti> mterry: ok... somehow you should be able to load all of them. because people developing the infographics. I don't care if its -f
[14:05] <mzanetti> mterry: also, Saviq said we need to have the demo users on the tablet somehow
[14:05] <mterry> mzanetti, infographics exist for single users too
[14:05] <didrocks> kenvandine: please relaunch the webcreds stack once it's merged
[14:05] <kenvandine> didrocks, i will... :)
[14:05] <Saviq> mterry, unfortunately we need to remember the things are getting demoed all the time (tablet, too)
[14:06] <didrocks> and hey! :)
[14:06] <didrocks> kenvandine: we are almost there, crossing fingers!
[14:06] <didrocks> (very hard)
[14:06] <kenvandine> didrocks, once i think it'll work :)
[14:06] <Saviq> mterry, so we should strive not to break that experience
[14:06] <didrocks> heh
[14:06] <mterry> Saviq, I did know we are demoing, but I was under the impression tablet was not one of them
[14:06] <Saviq> mterry, all the time
[14:06] <mterry> Saviq, yah yah I understand not breaking experiences, just thought tablet was not a demo
[14:07] <Saviq> mterry, it's not our focus for 13.10 indeed, but the demos include tablet, too
[14:07] <Saviq> mterry, it's awesome to demo, why wouldn't we! :D
[14:08] <mterry> mzanetti, so I still don't get your complaint about infographic.  Is it just that the current -f doesn't show one?  You tied infographics to multiple users in a previous comment
[14:08] <Kaleo> my IRC client highlighted "breaking"
[14:08] <Kaleo> anybody who breaks anything will die. :)
[14:09] <mterry> Saviq, also, note that tablet demo isn't broken.  It just shows a giant single-user swipe unlock
[14:09] <mzanetti> mterry: I'm fine... nic-doffay and pete-woods had troubles yesterday from what I understood..
[14:10] <mterry> mzanetti, I don't like the idea of switching to a login list based solely on width.  I want a platform API that tells us if we are in tablet mode.  But until then, we can hack a width consideration too
[14:11] <greyback> Saviq: kenvandine: well now I need to play it :)
[14:11] <mzanetti> mterry: I'm not saying it should be related to the width
[14:11] <mterry> mzanetti, I'm also confused about the demo problem.  Tablet demo still works, right?  We just show a phone greeter for the moment.  If we want multiple users for the tablet demo, we need a different demo setup
[14:12] <Saviq> mterry, depends on the definition of broken ;)
[14:12] <Saviq> mterry, feel free to ask sabdfl on his opinion :D
[14:12] <mzanetti> mterry: yes, that would have been my thoughts too...like a second set of demo data that enables the mulituser mock backend
[14:12] <mterry> Saviq, when we switch to lightdm (any day now), we're not going to have any demo users
[14:13] <mterry> Saviq, so whoever is running these demos needs to actually set up the device if they want to show tablet mode anyway
[14:13] <mzanetti> oh... we're already there? that's cool
[14:13] <Saviq> mterry, yeah I wasn't aware we're that close
[14:14] <Saviq> mterry, if that's the case then yeah, we need the phonedations team to create the users, is all
[14:14] <mterry> Saviq, no, not like tomorrow close, but close enough that I don't want to spend time creating a special demo mode that's just going to go away
[14:14] <Saviq> mterry, ok, what about the guys doing infographics? are they set to support multi-user changes, too?
[14:15] <MacSlow> Saviq, is the way plugins are loaded described somewhere?
[14:16] <mterry> Saviq, I don't follow?  We have infographics in multi-user mode, we have tests that expose a multi-user setup, I'm not sure what they're missing.  nic-doffay or pete-woods ?  Is there anything blocking your infographic work?
[14:16] <pete-woods> Saviq, mterry: I'd say it's broken, the clock doesn't show or anything like that
[14:16] <mterry> pete-woods, you mean with ./run -f?
[14:16] <pete-woods> it's like somewhere halfway between the old tablet style greeter and the phone one
[14:16] <pete-woods> no
[14:16] <kenvandine> fginther, thx for the merge, please let me know when jenkins is ready
[14:16] <pete-woods> ./run -- -fullscreen
[14:16] <pete-woods> mterry: ^
[14:17] <pete-woods> is what I'm doing
[14:17] <pete-woods> if we don't care about tablet mode for the time being, that's fine
[14:17] <pete-woods> I just thought it worth pointing out yesterday
[14:17] <Saviq> MacSlow, not sure what you mean, the order? or?
[14:18] <mterry> pete-woods, this is because the infographic code doesn't do anything smart when there's no infographic data
[14:18] <Saviq> MacSlow, here's some info http://qt-project.org/doc/qt-5.0/qtqml/qtqml-modules-qmldir.html
[14:18] <mterry> pete-woods, there should be a big (empty) infographic in center
[14:18] <pete-woods> mterry: the infographic has nothing to do with this
[14:19] <mterry> pete-woods, what you're seeing there is a non-narrowMode non-multiUser login screen
[14:19] <pete-woods> yes
[14:19] <mterry> pete-woods, in non-narrowMode, we don't show the clock.  Perhaps that should swich to non-multiUser
[14:19] <pete-woods> the infographic is correctly displaying
[14:19] <pete-woods> but there is no clock or login list
[14:19] <fginther> kenvandine, all done
[14:19] <pete-woods> so it looks really weird
[14:19] <mterry> pete-woods, it is?  I don't see the infographic here
[14:19] <MacSlow> Saviq, I just want to see if/where the backend is actually loaded
[14:19] <pete-woods> I think design need to decide what should happen here
[14:20] <pete-woods> mterry: I'm not using -f and this is on the phablet branch
[14:20] <mterry> pete-woods, there is no login list because this is just a very big phone screen (we stopped using size to determine if we are in phone or tablet mode)
[14:20] <mterry> pete-woods, yup, the default demo has just one user now (i.e. is in phone mode)
[14:20] <Saviq> MacSlow, I usually try a simple qml file with "import Something; Item { }" to check
[14:21] <pete-woods> mterry: I understand this - I'm only mentioning it because I think that it "appears" like it's broken to a user and I think that someone needs to figure out what it should look like
[14:21] <mterry> pete-woods, so you see an infographic?  It only looks broken to me because I don't see anything in the middle.  It felt like an infographic bug to me
[14:22] <pete-woods> mterry: yes, the infographic is there for the single "guest" user in "demo" mode
[14:22] <mterry> pete-woods, oh right, you're using demo, I was using -f
[14:22] <pete-woods> I totally agree that there needs to be some "no data" handling for the infographic too
[14:23] <kenvandine> fginther, thx
[14:24] <mterry> pete-woods, mzanetti: I'll test a branch that uses narrowMode to determine if we see LoginList instead of multiUser.  That might conform to your expectations more
[14:24] <Saviq> MacSlow, you can also go "qmlplugindump Something 1.0"
[14:25] <mzanetti> Saviq: found a bug in Verifier.qml ... It expects CONSTANT properties to have a changed signal
[14:25] <mzanetti> would you know right now how to fix it? otherwise I'd investigate myself
[14:25] <Saviq> mzanetti, yeah, simples, but do look into it, it's really simple
[14:26] <Saviq> mzanetti, and it's good that there's someone else to know that
[14:26] <mzanetti> ok
[14:27] <Saviq> mzanetti, but
[14:27] <Saviq> mzanetti, are you saying 'property: "something"' or 'constant: "something"' ?
[14:27] <Saviq> mzanetti, 'property: "something"' is assuming one with NOTIFY
[14:28] <mzanetti> oh
[14:28] <mzanetti> missed that
[14:28] <rsalveti> didrocks: sil2100: https://code.launchpad.net/~sil2100/qtvideo-node/fix_ftbfs_with_new_libhybris/+merge/167509 failed to land but I can't see the logs
[14:28] <mzanetti> Saviq: oh, that looks better, cheers
[14:28] <Saviq> mzanetti, introspecting wouldn't make sense, you need to declare in the test you want it to be that or something else
[14:29] <didrocks> rsalveti: I think it's a question for mmrazik ^
[14:29]  * Saviq still needs to document Verifier.qml
[14:29] <mmrazik> rsalveti: publishing to the public jenkins is broken :-/ IS is working on it
[14:29] <mmrazik> let me give you another url
[14:31] <rsalveti> alright, failure due the libhybris available in daily-build-next ppa
[14:32] <mterry> rsalveti, my libhybris is broken?
[14:32] <rsalveti> mterry: it's incompatible with the upstream one (in the archive)
[14:33] <mterry> rsalveti, because of my change or just in general?
[14:33] <rsalveti> and that mr is to fix the new lib names, but can't get it approved as the ci job is pulling the older hybris
[14:33]  * mterry was going to port that patch to the one in distro...
[14:33] <rsalveti> mterry: which patch?
[14:33] <rsalveti> mterry: not sure if this issue is related with anything you changed
[14:33] <mterry> rsalveti, oh I just patched libhybris yesterday for a shm issue with nexus7 devices
[14:34] <mterry> it was an upstream patch though...
[14:34] <rsalveti> I pushed the new hybris to the archive, based on upstream, and the media lib changed from mediaplayer to media
[14:34] <rsalveti> mterry: hm, mind pointing me the patch?
[14:34] <mterry> rsalveti, https://github.com/libhybris/libhybris/pull/49/files
[14:34] <rsalveti> mterry: right, that's not yet merged upstream
[14:35] <mterry> rsalveti, right
[14:35] <rsalveti> I can check why
[14:35] <rsalveti> mterry: but meanwhile can you remove libhybris from daily-build-next?
[14:36] <mterry> rsalveti, will that break our phablet builds, if the two are incompatible?
[14:36] <rsalveti> mterry: it'll break the media player related stack, which I'm trying to fix
[14:36] <rsalveti> mterry: it's just for saucy anyway
[14:36] <rsalveti> as we're trying to get them in the archive
[14:37] <mterry> rsalveti, ok...  I want to see if we need to carry any patches over to archive first
[14:37] <rsalveti> mterry: we don't, unless you added another extra patch there
[14:37] <rsalveti> mterry: I did the sync between both versions
[14:37] <rsalveti> and pushed most upstream already
[14:37] <rsalveti> I'm doing the clean up
[14:38] <mterry> rsalveti, so you have the no-gles2 patch already?
[14:38] <rsalveti> but I only did the sync from whatever was in the bzr branch
[14:38] <rsalveti> no-gles2?
[14:38] <rsalveti> why didn't such patches land in the bzr branch we were maintaining?
[14:38]  * rsalveti looks
[14:38] <mterry> rsalveti, ah, that landed in bzr trunk
[14:39] <mterry> rsalveti, the only thing missing is that pull-49 above, which I uploaded yesterday to the daily-build-next ppa
[14:39]  * Cimi is getting mental with timezones...
[14:39] <rsalveti> mterry: cool, then we're good
[14:39] <mterry> rsalveti, do you have any objection to that pull-49 being applied to the saucy package?
[14:40] <rsalveti> mterry: well, would like to test that with the other devices I have first, do code review and check with upstream what it wasn't yet merged
[14:41] <rsalveti> *why
[14:42] <mterry> rsalveti, it's blocking testing on nexus7, so I'll hold off applying to saucy, but would appreciate your attention on it
[14:43] <rsalveti> mterry: sure, I'm reviewing it already
[14:43] <mterry> rsalveti, libhybris on saucy deleted from daily-build-next
[14:44] <rsalveti> mterry: and what is the behavior that this patch fixes?
[14:44] <rsalveti> thought the pthread issues were happening just when testing mir
[14:44] <mterry> rsalveti, on nexus7, mir wouldn't work after a few seconds
[14:44] <rsalveti> as we have the nvidia hack in place
[14:44] <rsalveti> right, that is it then
[14:44] <mterry> rsalveti, kdub_ knows more
[14:45] <rsalveti> cool, thanks
[14:45] <mterry> rsalveti, right, should have said are blocking testing mir on nexus7.  left out "mir"  :)
[14:45] <rsalveti> :-)
[15:12] <Saviq> greyback, do you need me at the mir-unity sync today?
[15:13] <greyback> Saviq: no, I'll be fine. It won't be a long one
[15:18] <sil2100> davidcalle: hi
[15:18] <davidcalle> sil2100, hey
[15:19] <sil2100> davidcalle: how does that gdrive scope segfault look to you?
[15:19] <sil2100> Fixable? ;)
[15:21] <davidcalle> sil2100, I think it's the new gir gdata. But I can't reproduce yet, no Saucy install around (downloading). If, by any chance, you have a Saucy install running Unity <7 and the previous gdocs scope fails, then that's it.
[15:26] <sil2100> davidcalle: sadly, I have 7.0.0 unity installed here
[15:27] <davidcalle> sil2100, will give it a try as soon as I can, but I'm not sure it will be before tomorrow.
[15:31] <sil2100> davidcalle: what's the exact test-case in this case? Saucy running old unity with the old scope, yes?
[15:32] <davidcalle> sil2100, yes, since they both use gir1.2-gdata, and that's what could cause a segfault in the test.
[15:59] <davidcalle> sil2100, running a VM now. It does work.
[16:00] <sil2100> davidcalle: oh, so it wasn't the problem?
[16:00] <davidcalle> sil2100, nope :(
[16:02] <mzanetti> Saviq: I'm away next 2 days so no urgency at all: https://code.launchpad.net/~mzanetti/unity-api/launcher/+merge/167560
[16:02] <davidcalle> sil2100, I need to go, but I will try to reproduce the segfault. On Saucy, what is the PPA with the segfault?
[16:02] <Saviq> mzanetti, yup, saw that
[16:03] <Saviq> mzanetti, have a nice time off
[16:03] <sil2100> davidcalle: it's in daily-build, so ppa:ubuntu-unity/daily-build
[16:03] <sil2100> Saucy
[16:03] <mzanetti> Saviq: however, when I come back I will start implementing the appropriate mock in the shell... so it'd be ubercool if we would have the apis packaged up and ready to depend on from the shell (if that's not already happened)
[16:03] <sil2100> davidcalle: I'll also try to take a look at that, the only problem is that I do not know nosetests ;)
[16:03] <mzanetti> Saviq: thanks
[16:04] <Saviq> mzanetti, you know, if it goes in without review comments, it'll be there ;D
[16:04] <Saviq> mzanetti, while you're at it, can you push it to ~unity-team
[16:04] <mzanetti> Saviq: hehe... I rather meant the whole packaging stuff
[16:04] <mzanetti> Saviq: ack
[16:04] <Saviq> mzanetti, it's being packaged already
[16:05] <mzanetti> Saviq: so all it takes is to add it as a build-dep in unity8?
[16:05] <Saviq> mzanetti, yeah
[16:05] <mzanetti> awesome
[16:06] <mzanetti> Saviq: moved it over to ~unity-team
[16:07] <Saviq> mzanetti, cheers
[16:19] <Cimi> Saviq, I added tests, can I have a mid review?
[16:24] <Saviq> Cimi, not today ;)
[16:24] <davidcalle> sil2100, so. There is a segfault issue in the test_get_filters method. Specifically at filter_set.get_filters()
[16:24] <mzanetti> Cimi: I can give it a quick look if you want
[16:26] <davidcalle> sil2100, and I do need to go this time. You should ask jamesh if he has an idea why. (Really need to go now :) )
[16:27] <sil2100> ;)
[16:27] <sil2100> didrocks: along with rsalveti, we have resolved all the issues in the media stack builds (probably)
[16:27] <sil2100> Once all the merges go in, we'll re-run the stack maybe?
[16:28] <Cimi> mzanetti, good
[16:28] <sil2100> didrocks: I'll try to takle the gdrive issue in a moment after David's pointers
[16:28] <Cimi> mzanetti, https://code.launchpad.net/~cimi/indicators-client/system-components
[16:29] <Cimi> still some work has to be done but there's a TODO for that
[16:31] <mzanetti> Cimi: I think you should move __compressedHeight etc inside the "intern" object. you can still access it from there in the tests, no?
[16:34] <Cimi> mzanetti, don't think so
[16:34] <Cimi> mzanetti, how?
[16:34] <Cimi> findChild didn't work
[16:35] <mzanetti> Cimi: oh... hmm... probably because its a QtObject and not an Item. I would still vote for making it an item instead of pollution the API with __ stuff
[16:35] <mzanetti> Cimi: not sure we all agree on that... just my 2 cents
[16:36] <Cimi> decide guys :)
[16:37] <mzanetti> Cimi: hehe... that means you decide, its your code :P
[16:37] <Cimi> B-)
[16:48] <Kaleo> mzanetti: don't use Ã__
[16:48] <Kaleo> mzanetti: __
[16:48] <Kaleo> mzanetti: that's the "new" policy in the sdk
[16:48] <mzanetti> Kaleo: +1
[16:49] <Kaleo> lunch time
[16:57] <mzanetti> Cimi: http://paste.ubuntu.com/5736303/
[16:57] <mzanetti> Cimi: I added comments on the tests
[17:01] <didrocks> sil2100: great! ;)
[17:02] <mzanetti> Cimi: I'm also not sure if the copy/paste of the Calendar tests to the CalendarMenu tests is good. As CalendarMenu just add a label on top I'd say that testing everything through CalendarMenu makes more sense
[17:11] <sil2100> didrocks: still debugging ;/
[17:31] <sil2100> didrocks: what other scopes are python3 based?
[17:31] <sil2100> I just need at least one other
[17:32] <didrocks> sil2100: all the others apart from launchpad and sshsearch are python3 based
[17:32] <sil2100> ACK
[17:33] <sil2100> Ok, thought some are also vala, not sure I had the assumption we had vala scopes somewhere
[17:33]  * sil2100 stupid
[17:47] <sil2100> didrocks: so, I debugged and found where it's segfaulting, but it seems to segfault in this particular place for all scopes (jsut othes scopes don't use this)
[17:48] <sil2100> didrocks: so, it might be even something with the new toolchain?
[17:49] <sil2100> didrocks: the thing is, it seems that we get a segfault when iterating through a vala List in python that's returned by libunity
[17:49] <sil2100> didrocks: it seems as if something is invalid in the list, making it iterate over the end of the list
[17:50] <didrocks> sil2100: urgh
[17:50] <didrocks> urgh urgh urgh
[17:51] <didrocks> sil2100: we need mhr3 and pawel?
[17:51] <sil2100> didrocks: I tried pinging jamesh, but he's not around
[17:51] <sil2100> Same for Paweł and Michal
[17:51] <sil2100> ;/
[17:52] <sil2100> I'm trying to check what's wrong, as the length is being returned correctly
[17:53] <didrocks> sil2100: ok, maybe try barry?
[17:53] <didrocks> sil2100: or doko?
[17:53] <didrocks> sil2100: there is a Dee gir override
[17:53] <didrocks> sil2100: it's in dist-packages
[17:53] <didrocks> ooopsss
[17:53] <didrocks> site-packages
[17:53] <didrocks> maybe it needs to be moved in dist-packages?
[17:53] <didrocks> you can maybe try that locally?
[17:53] <sil2100> didrocks: I see that len() also segfaults ;p But after returning the length
[17:55] <didrocks> sil2100: so maybe that override?
[17:55] <sil2100> didrocks: let me check that
[17:55] <didrocks> sil2100: pitti can also help debugging (but he should be afk)
[17:59] <sil2100> didrocks: that override, what package installs it?
[18:00] <didrocks> sil2100: gir1.2-dee-1.0
[18:00] <didrocks> IIRC, you have a /usr/lib/python3/site-packages/gi/overrides/Dee.py
[18:00] <didrocks> oops
[18:00] <didrocks> IIRC, you have a /usr/lib/python3.3/site-packages/gi/overrides/Dee.py
[18:00] <didrocks> maybe try in dist-packages?
[18:00] <didrocks> (cp it)
[18:00] <sil2100> It's in dist-packages for python3
[18:00] <sil2100> dpkg -L gir1.2-dee-1.0
[18:00] <sil2100> /usr/lib/python3/dist-packages/gi/overrides/Dee.py
[18:01] <sil2100> But maybe my dee is outdated?
[18:01] <sil2100> hm, it seems to be rather up-to-date, from 2 days ago
[18:03] <sil2100> didrocks: I'll fill in a bug and e-mail some relevant python folks about it
[18:03] <didrocks> sil2100: hum
[18:04] <didrocks> sil2100: you should have one in the ppa from today
[18:04]  * didrocks looks
[18:04] <sil2100> Yes, but I didn't upgrade to that one
[18:04] <didrocks> sil2100: I'm interested into that one TBH ;)
[18:04] <sil2100> Still, I doubt it changed in like one day?
[18:05] <tedg_> bregma, Do you know of someone I can harass to review this merge?  https://code.launchpad.net/~ted/unity/upstart-job/+merge/164270
[18:05] <sil2100> didrocks: I don't know how the python<->vala bindings are done, so I'm a bit puzzled here
[18:06] <didrocks> sil2100: maybe olli would know who can help?
[18:12] <sil2100> olli: ^
[18:15] <sil2100> olli: ping!
[18:16] <sil2100> Great, and thunderbird segfaults all the time
[18:17] <sil2100> Thank you saucy
[18:19] <ChrisTownsend1> tedg_: I'll review that MP
[18:19] <tedg_> ChrisTownsend1, Great, thanks!
[18:19] <ChrisTownsend> tedg_: Sure thing!
[18:29] <sil2100> hm, currently I have no more ideas
[18:29] <sil2100> didrocks: but I sent an e-mail to people
[18:29] <sil2100> pstolowski or mhr3 might know how to deal with this, they know interaction with vala well
[18:30] <didrocks> sil2100: ok, thanks!
[18:30] <didrocks> sil2100: this is the latest blocker I guess
[18:30] <didrocks> then, we'll be done
[18:30] <didrocks> unity tests pass
[18:31] <sil2100> \o/
[18:31] <sil2100> :)
[18:32] <ChrisTownsend> tedg_: Approved!  Sorry that it sat so long.
[18:33] <didrocks> let's hope it will get fix tomorrow ;)
[18:33] <didrocks> sil2100: nice email, thanks!
[18:35] <tedg_> ChrisTownsend, Cool, while you've got things setup, do you mind going down the chain?  https://code.launchpad.net/~ted/unity/upstart-panel-service/+merge/165739
[18:35] <sil2100> ;/
[18:35] <tedg_> ChrisTownsend, It's basically the next step from getting Unity in, then the panel service.
[18:35] <sil2100> didrocks: np! Still trying to figure out what's wrong ;p
[18:35] <tedg_> ChrisTownsend, Broke it up to make it easier to review.
[18:35] <ChrisTownsend> tedg_: Ok, yeah, will do.
[18:35] <didrocks> sil2100: heh, good hunt!
[19:32] <ChrisTownsend> tedg_: Hey, when trying to merge in lp:~ted/unity/upstart-panel-service into unity on my machine, I get a bzr warning telling me I got a criss-cross merge.  Is this expected?
[19:32] <tedg_> ChrisTownsend, Eh, could be.  Probably I merged a branch that has already landed in trunk.
[19:32] <tedg_> ChrisTownsend, Guessing probably the upstart-event branch.
[19:33] <ChrisTownsend> tedg_: Ok.  I get a debian/control conflict.
[19:33] <tedg_> Hmm, that's more serious.
[19:33] <tedg_> Let me fix it.
[19:34] <ChrisTownsend> tedg_: Alright
[19:35] <tedg_> ChrisTownsend, No clue how that was a conflict...
[19:35] <tedg_> ChrisTownsend, r3339
[19:35] <ChrisTownsend> tedg_: Yeah, looked strange to me...
[20:26] <ChrisTownsend> tedg: I may prematurely approved the first MP.  For some reason, it was not running trunk when I tried it out and I thought everything was working fine.  When I try trunk on it's own, I keep getting a crash, so I can't test your MP's against trunk at the moment.
[20:34] <tedg> ChrisTownsend, Ah, okay.  Bummer.
[20:34] <ChrisTownsend> tedg: Well, I already approved that first MP based on false results.  It's probably too late to stop it.