[00:12] <veebers> elopio: is there anything I can do to help out with the touch events? I find myself idle while waiting for tests etc.
[03:34] <elopio> veebers: sorry, I went to the gym.
[03:34] <elopio> maybe you can help me figuring out how to get an old version of all the packages that are installed with autopilot.
[03:34] <elopio> or maybe, it would be easier to replicate everything autopilot does with python-evdev, and then we reduce the problem to that package and the libs it calls.
[03:39] <veebers> elopio: that was going to be my suggestion, remove autopilot and replicate using the bare libraries.
[03:40] <veebers> That way we remove any question that it's autopilot specific, also might help outline if we're doing something incorrect
[03:41] <elopio> yes, that sounds better. I will give it a try.
[03:45] <veebers> sounds good, let me know how it goes. Sorry I can't follow along at home, I don't have the right hardware
[03:50] <elopio> veebers: no worry. You are keeping me from doing stupid things, which is help enough.
[03:50] <veebers> ^_^
[04:37] <veebers> elopio: if you're still around can I get your opinion on this: https://code.launchpad.net/~canonical-platform-qa/address-book-app/remove-teardown-ap-tests/+merge/258829
[04:37] <veebers> (even if you're not around, can you comment on it ;-))
[04:47] <elopio> veebers: looking...
[04:48] <elopio> veebers: nice! would it make sense to make it a fixture?
[04:48] <veebers> elopio: excellent idea
[05:07] <veebers> hmm, dumb appending to CalledProcessError.args doesn't work as I expected it
[05:14] <veebers> elopio: have pushed a new fixture version
[05:16] <elopio> veebers: why not raising the exception when the initctl call fails?
[05:17] <veebers> elopio: oh rats, I think I screwed that , one sec
[05:18] <veebers> elopio: good catch, I removed the raise line by accident
[05:18] <elopio> veebers: ok, other than that, +1.
[05:19] <veebers> pushed
[05:24] <veebers> elopio: who else would I need to ping? Or can I be confident that it'll get picked up by the team
[05:24] <elopio> veebers: the team is right. If you don't get a review soon, ping renato.
[05:25] <veebers> coolio, thanks again el
[05:25] <veebers> :-P tab completion fail
[10:12] <jibel> pitti, is there any way to know to what ${misc:Depends} will expand to? I've problems to autodiscover some dkms packages that only have this line in the Depends field
[10:13] <pitti> jibel: not precisely, but it shouldn't be related -- it's usually stuff like versioned dpkg
[10:13] <pitti> jibel: we might need to hardcode some packages?
[10:14] <jibel> pitti, OK, I'll do that.
[10:19] <jibel> actually almost all the dkms package names end with -dkms excepted proprietary drivers which have dkms in their Depends field. It should be relatively accurate to rely on Depends and fallback to the name.
[14:11] <brendand_> elopio, sure we can pair
[14:11] <brendand_> elopio, the test seems pretty simple though
[14:11] <elopio> :) brendand_: tell me when you are writting the code, and I will just look over your shoulder.
[14:15] <elopio> sjcazzol: you need an account in https://trello.com. Make sure to sign with your canonical email.
[14:16] <sjcazzol> elopio: ok, I'll do, thanks
[14:23] <elopio> sjcazzol: want to start writting some code now?
[14:23] <sjcazzol> yes, just a minute please
[14:23] <sjcazzol> elopio: just a minute pleas
[14:23] <elopio> ok, let me know when you are ready.
[14:25] <sjcazzol> elopio: I am ready
[14:25] <elopio> sjcazzol: lets join the same hangout.
[14:25] <elopio> the stand up one I mean.
[15:10] <elopio> ping oSoMoN_: do you remember the version # of an arale with working autopilot tests?
[16:00] <elopio> fgimenez: have you been using tmate?
[16:02] <fgimenez> elopio, not lately, when i did it worked just fine
[16:02] <elopio> fgimenez: I will give it a try with sjcazzol
[16:04] <fgimenez> elopio, ok, it's great for pairing
[16:05] <fgimenez> elopio, sjcazzol we can try https://github.com/fgimenez/fenced-tmate tomorrow, hopefully it still works ;)
[16:05] <elopio> fgimenez: it's downloading stuff. I'll let you know how it goes.
[16:08] <sjcazzol> elopio: fgimenez: I can't download dependencies until the system update is not completed
[16:09] <elopio> sjcazzol: I'll just have to give you an ip to ssh. Nothing to install in there.
[16:10] <sjcazzol> great
[16:12] <elopio> fgimenez: the problem is that it's a 14.04 container. That's hard to set up for trunk development.
[16:14] <elopio> we can do tmate read only, which anyway it's better than screen sharing.
[16:14] <fgimenez> elopio, yes, we could try setting up a container with the 'devel' distribution, and update from there
[16:15] <elopio> sjcazzol: try this: ssh ro-34vtwOqtNVoVJ2lwweNsI7CBY@ny.tmate.io
[16:15] <fgimenez> I'm leaving, good evening everyone o/
[16:16] <elopio> bye fgimenez.
[16:17] <sjcazzol> elopio: done
[16:17] <elopio> sjcazzol: can you see the ping?
[16:17] <sjcazzol> elopio: yes
[16:18] <elopio> sjcazzol: ok, lets try one last time the hangout.
[16:18] <elopio> we'll talk over google and code over tmate.
[16:46] <elopio> sjcazzol: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/fixture_unset_env/
[17:21] <elopio> sjcazzol: ready for review: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ui-toolkit/fixture_unset_env/+merge/258906
[17:21] <elopio> you can comment and leave your vote: approve or needs fixing.
[17:47] <balloons> elopio, what's the status on those unity helpers ? http://people.ubuntu.com/~elopio/unity8/unity8.html
[17:47] <balloons> can we import them now?
[17:47] <elopio> balloons: waiting for one prerequisite branch. I can propose now the sphinx branch for you to start reviewing it.
[17:47] <elopio> well, tomorrow more likely.
[17:48] <balloons> elopio, ok.. and what package will this go into?
[17:48] <balloons> no rush, plenty of reviews for me to do atm :p
[17:48] <elopio> balloons: unity8.